Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle JDeveloper updated3 12.2.1.3.0

Product Description:

This VPAT covers the user environment of Oracle JDeveloper 12.2.1.3.0 ; the Installer and Upgrade Assistant are also covered. The Oracle Application Development Framework (ADF) 12.2.1.3.0 output is not covered here, it is covered separately in the ADF 12.2.1.3.0 VPAT listed in the Dependencies Section.

Date:

16-Mar-2018

Archive Note:

This VPAT applies to only version 12.2.1.3.0. It does not apply to any versions of Oracle JDeveloper after this. This VPAT has been superseded by Oracle JDeveloper 12.2.1.4.0.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:
  • Product Tutorials

Steps to enable Access Bridge

  1. Launch the Windows Control Panel and click on Ease of Access Center
  2. Click on 'Use the computer without a display'
  3. Under the 'Other programs installed' section, select the screen reader being used and 'Enable Java Access Bridge'
  4. Restart screen reader before starting up JDeveloper

Please see About JDeveloper Accessibility for information on the accessibility features of Oracle JDeveloper.

Dependent Products


This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/index.html

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/Level A - Yes
Level AA - Yes
Level AAA - No
Section 508 as published in 2017, at https://www.Section508.govYes

Terms

The terms used in the Conformance Level information are defined as follows:

Supports
The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Supports with Exceptions
Some functionality of the product does not meet the criteria.
Does Not Support
Majority of functionality of the product does not meet the criteria.
Not Applicable
The criteria are not relevant to the product.

WCAG 2.0 Report

Table 1 also documents conformance with:

  • Section 508: Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria
Conformance Level
Remarks and Explanations
1.1.1 Non-text Content (Level A)Supports with Exceptions

The product was tested for:

  • Images that convey information are embedded within standard user interface components and have a meaningful AccessibleName and/or AccessibleDescription
  • Images that are decorative are embedded within standard user interface components and have neither an AccessibleName nor an AccessibleDescription
  • Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table), or the containers of the complex images are filled with simple image children whose information is exposed via AccessibleName and/or AccessibleDescription
  • Data tables include a summary or caption, programmatically connected with the table as the AccessibleTable's AccessibleSummary
  • Controls have an AccessibleName, or a label control with an AccessibleName has been programmatically associated with it
  • Text summary or alternative is provided for time-based media
  • Non-text characters are not used or have meaningful alternative text
  • CAPTCHAs are not used

Exceptions:

  1. Bug 19970115: While debugging a test program, opening the Threads window and using the arrow keys to navigate through the table does not read out selected item. The key pressed is read out instead.
  2. Bug 21217867: On the first page of the Create Application Server wizard there are radio buttons to specify whether the server is an integrated or standalone web server. The screen reader does not read the selected button's value but just says “Web server radio button selected”.
  3. Bug 23041623: Screen reader does not read text "This version of JDeveloper requires that all projects with JavaServer Faces and JSTL be migrated..." in 'Java Web Projects' page but just reads "Migrate Application, Step 2 of 3".
  4. Bug 23033596: Every tree node in the Hooks tab of extension.xml is read multiple times when navigating using the keyboard.
  5. Bug 23033573: Screen reader does not read out the contents of the Insert Hook Handler dialog when extension.xml is opened and the Hook Handlers tab is selected.
  6. Bug 23033555: Screen reader incorrectly reads out "read only field followed by HTML tags" instead of the actual field's content when focus is on the read only fields having description about the rule in Audit's Manage Profile preferences dialog.
  7. Bug 23031692: Screen reader incorrectly reads out column headers when editing a table after online database connection is created.
  8. Bug 23031673: Screen reader incorrectly reads out username field first instead of the default highlighted database link name when editing a database link in an online database connection.
  9. Bug 23031663: Screen reader incorrectly reads out the title and fields when a tablespace in an online database is edited.
  10. Bug 23031653: Screen reader incorrectly reads out the title and fields when a sequence in an online database is edited.
  11. Bug 23031639: Navigating to ‘Quick DDL’ for any table or view created against an online database, and using arrow keys to open the sub menu, the “Save to File” option is read out twice.
  12. Bug 23031021: Opening a file list and choosing the 'Date Modified' option, displays current system date. But attempting to navigate using arrow keys to the next date, month or year causes the screen reader to incorrectly read out the previous date shown instead of the current selection.
  13. Bug 22956738:  When multiple windows like Message, Debugging, Breakpoint, Running are opened, screen reader does not read out the window list drop down when Alt+0 is invoked.
  14. Bug 22938142: When a conflicting shortcut is wired to a command in the shortcut keys page, the screen reader incorrectly reads out the conflicting commands twice.
  15. Bug 22937441: Navigating through the road map options using arrow keys in the 'Run Ant Target -> Advanced...' dialog, results in the screen reader incorrectly reading out the step number.
  16. Bug 22929995: When adding a repository to pom.xml using 'Add from Preferences' option, the check box selection is not read out by the screen reader when space bar is pressed to select a repository.
  17. Bug 22917634: The window title for all the windows within JDeveloper are not read by the screen reader. If a window is already open, then the screen reader reads "Edit". If the window is opened for the first time, then the screen reader does not say anything at all.
  18. Bug 22392977: Screen reader does not read out items when using Ctrl+Tab to move between views in JDeveloper. In addition, the keyboard actions (up/down) closes this dialog when the screen reader is running.
  19. Bug 22392964: When tabs are added to Messages view when debugging a Java program, none of the tab names like Debugging, Messages, Smart Data and Breakpoints are read out by the screen reader.
  20. Bug 22392955: When audit rules are run for a workspace and 'Show Audit Rule...' is selected by invoking the context menu on any audit warning, dialog contents are not read out by the screen reader.
  21. Bug 22392945: Screen reader does not read any of the items in the combo box when 'Break only for Threads named' is selected while editing the condition breakpoints.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not Applicable

Audio/video content is not included in the product.

1.2.2 Captions (Prerecorded) (Level A)Not Applicable

Audio/video content is not included in the product.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not Applicable

Audio/video content is not included in the product.

1.2.4 Captions (Live) (Level AA)Not Applicable

Audio/video content is not included in the product.

1.2.5 Audio Description (Prerecorded) (Level AA)Not Applicable

Audio/video content is not included in the product.

1.3.1 Info and Relationships (Level A)Supports

The product was tested for:

  • User interface component labels are associated with the fields they are labeling via the LabelFor and LabeledBy relations
  • Headings are marked as such with a Group relation from the header to the items beneath the header
  • Groups of components are marked as such, with a Group relation from the header of the group to the members of the group
  • Style sheets are used only to change the layout and presentation on the screen
  • Lists are contained within a List component
  • Tables are contained within a Table component, implement the AccessibleTable interface, provide an AccessibleSummary, and contain include row and column headers where appropriate
1.3.2 Meaningful Sequence(Level A)Supports

The product was tested for:

  • The accessibility hierarchy is logical
1.3.3 Sensory Characteristics(Level A)Supports

The product was tested for:

  • Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound
  • Instructions provided which refer to graphics included a reference to the text alternative of the graphic
1.4.1 Use of Color(Level A)Supports

The product was tested for:

  • Information conveyed by color is available in alternative formats, such as shape, text, font weight
  • Information conveyed by color has a contrast ratio of at least 3:1
1.4.2 Audio Control(Level A)Not Applicable

Audio/video content is not included in the product.

1.4.3 Contrast (Minimum) (Level AA)Supports with Exceptions

The product was tested for:

  • Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
  • All other text and images of text have a contrast ratio of at least 4.5:1

Exceptions:

  1. Bug 23039096: The list of projects is not visible in the search tab of the Resource Bundle node in High Contrast Black theme.
  2. Bug 23040591: Configuration dialogs (Create Remote Region, Create Catalog) launched from Application Resources and Resource Catalog views have user interface elements that are cutoff or unreadable in the High Contrast Black theme on Windows Look & Feel.
  3. Bug 23040410: In High Contrast themes with Windows Look & Feel, text in the 'Properties' and 'Version' tab in 'About Oracle JDeveloper' dialog, 'Application Overview' dialog, 'Preference' window and 'Shortcut Keys' page becomes unreadable.
  4. Bug 23040237: In High Contrast themes with Windows Look & Feel, window headers are unreadable in the ‘Resources’, ‘Create File System Connection’, ‘Create JMX Connection’ and ‘Create Remote Region Connection’ dialogs.
  5. Bug 23038985: The mnemonics key underlines in the context menu for an online database connection are not visible in High Contrast Black theme with Windows Look & Feel.
  6. Bug 23038970: Section headers are not properly visible in the editor UI for database files in High Contrast themes with Windows Look & Feel.
  7. Bug 23038949: The Show/Hide controls to access column properties for online database tables are not visible in High Contrast themes with Windows Look & Feel.
  8. Bug 23038318: The text for a command button placed on a page is unreadable on the 'Design' tab in High Contrast themes with Windows Look & Feel.
  9. Bug 22386343: When audit rules are run for any project and 'About Rule' dialog is invoked, the contents are unreadable in High Contrast themes with Windows Look & Feel.
  10. Bug 22386224: Data in the ‘Issues’ window is not readable in High Contrast themes.
  11. Bug 22198426: Some of the UI in the ‘Find in Application Files’ dialog including button titles is not visible in High Contrast themes with Windows Look & Feel.
  12. Bug 21932303: The text in the Application Overview page becomes unreadable in High Contrast themes with Windows Look & Feel.
  13. Bug 21932429: Table header is cut off and not readable in High Contrast themes with Windows Look & Feel, when extension editor is opened and Hook Handlers is selected.
  14. Bug 21932405: None of the issues listed in the live issues tab when Java code containing issues is opened, are visible in High Contrast themes with Windows Look & Feel.
  15. Bug 21932335: When a file is opened in the editor, the file name on the selected tab becomes black and unreadable in High Contrast themes with Windows Look & Feel.
1.4.4 Resize text(Level AA)Supports

The product was tested for:

  • Text can be resized up to 200% without loss of content or functionality
1.4.5 Images of Text(Level AA)Supports

The product was tested for:

  • Images of text are not used
2.1.1 Keyboard(Level A)Supports with Exceptions

The product was tested for:

  • ability to perform functions from the keyboard only
  • logical movement of focus through the controls
  • proper operation of unique keystrokes, including those listed in the product documentation

Usability information: There are a few non-standard workarounds for issues that occur when we try to debug any test program:

  • The first is that, the 'Monitors' window that is opened while debugging a given test program cannot be closed using the standard keyboard operations. Similarly, when a variable is chosen and the Inspectors window is opened while debugging a test program, this window cannot be closed using the standard keyboard operations. The workaround for both these issues is to use 'Ctrl+Space' to open the context menu for the child window and select close.
  • Another issue that occurs while debugging, only when a screen reader and Java Access Bridge are enabled is that:  When we open the debugger logging window, we are not able to access the search field or the terminate button using the standard keyboard operations in this window. One workaround is to use ‘Shift+Tab’. Using ‘Shift+Tab’ twice gets us to the terminate button and ‘Space’ activates it. Using it thrice puts us in the search field. Another workaround is to use ‘Ctrl+Tab’ to set the focus in the Debugging log window, and the focus is initially on the search field. The next ‘Tab’ takes us to the Terminate button and hitting ‘Space’ terminates the debugging session. When the screen reader is not enabled, the standard keyboard operations work fine.

Exceptions:

  1. Bug 13734304: The gutter and many of its icons/indicators are presently not accessible using just the keyboard.
  2. Bug 8915761: The dialogs, arrow/toggle buttons inside JDeveloper need to be made more discoverable by adding some extra text to the accessible description.
  3. Bug 23042609: Unable to navigate to all the Heap Dump buttons in the Heap Dump console of the profiler.
  4. Bug 23042482: Unable to invoke the context menu using keyboard from the Thread Dump console of the profiler.
  5. Bug 23040062: Screen reader does not read toolbar buttons when navigating using the keyboard.
  6. Bug 22956783: Keyboard navigation using up and down arrow keys does not work for the property menu list in the Property Inspector.
  7. Bug 22929508: When creating maven archetype projects using 'Generate from Archetype' option, the tree node in the table for matching archetypes cannot be expanded using keyboard.
  8. Bug 22392583: Unable to switch from the default tab in the Log view using the keyboard.
  9. Bug 21629682: From the Log window, the system menus do not come up when using the keyboard shortcuts.
  10. Bug 25645330: Unable to navigate to all components in the test viewer dashboard and find tasks views.
  11. Bug 22937652: Both 'Change...' & 'Finish' buttons are wired to the same mnemonic key (n) in the 'Process' page of the 'Run Ant Target -> Advanced' dialog.
  12. Bug 22937567: Both 'Property Files' and 'Finish' buttons are wired to the same mnemonic key (F) in the 'Properties' page of 'Run Ant Target -> Advanced' dialog.
  13. Bug 22930397: When a profile activation rule for 'JDK Version' is added to the Project Object Model (POM) file, the 'Version Range Specification' hyperlink although focusable, cannot be opened using the keyboard.
  14. Bug 23631297: Help content is not automatically read by the screen reader until the focus is set to the area that contains the actual text.
  15. Bug 25558990: The drop down menu in the Team Servers window cannot be opened using the keyboard.
2.1.2 No Keyboard Trap (Level A)Supports

The product was tested for:

  • Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control.
2.2.1 Timing Adjustable(Level A)Not Applicable

There is no time sensitive content included in the product.

2.2.2 Pause, Stop, Hide (Level A)Not Applicable

There is no flashing or moving content included in the product.

2.3.1 Three Flashes or Below Threshold(Level A)Not Applicable

No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

2.4.1 Bypass Blocks(Level A)Supports

Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.

2.4.2 Page Titled(Level A)Supports

The product was tested for:

  • The name of the software application is meaningful.
2.4.3 Focus Order(Level A)Supports with Exceptions

The product was tested for:

Exceptions:

  1. Bug 22937769: Pressing the 'Remove' button to remove a classpath entry from 'Run Ant Target -> Advanced -> Classpath' dialog, incorrectly shifts focus to the next checkbox component - 'Include Jar Files from User Home'.
  2. Bug 22930661: In the Import Maven Projects dialog, pressing the spacebar to activate the Refresh button shifts the focus to the 'Also import source files into application' checkbox.
  3. Bug 23631297: Help content is not automatically read by the screen reader until the focus is set to the area that contains the actual text.
2.4.4 Link Purpose (In Context)(Level A)Supports

The product was tested for:

  • The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose
2.4.5 Multiple Ways(Level AA)Supports

The product was tested for :

  • Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.
2.4.6 Headings and Labels(Level AA)Supports

The product was tested for:

  • Headers describe the topic or purpose of the content below them
  • Labels describe the purpose of the associated field
2.4.7 Focus Visible(Level AA)Supports with Exceptions

The product was tested for:

  • Visual indication of the location of the focus

Exceptions:

  1. Bug 21206316: The focus indicator is not shown on the sections separator labels of the Component Palette.
3.1.1 Language of Page(Level A)Supports

The product was tested for:

  • Properly set locale/language
3.1.2 Language of Parts(Level AA)Supports

The product was tested for:

  • Properly set locale/language for text passages that are in a different language than that of the software
3.2.1 On Focus(Level A)Supports with Exceptions

The product was tested for:

  • When an element receives focus, it does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window

Exceptions:

  1. Bug 23031038: Opening a file list and choosing 'Date Modified' as the first dropdown option and 'is in the last' as the second dropdown option causes the page to not refresh properly and display letter 'a' in between the first and second field when screen reader is running
3.2.2 On Input(Level A)Supports

The product was tested for:

  • Changes in the value of user interface components does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window
3.2.3 Consistent Navigation(Level AA)Supports

Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.

 

3.2.4 Consistent Identification(Level AA)Supports

The product was tested for:

  • Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)Supports

The product was tested for:

  • When input errors are detected, they are described to the user in text, including identifying the item where the error occurred
3.3.2 Labels or Instructions (Level A)Supports

The product was tested for:

  • Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion (Level AA)Supports

The product was tested for:

  • Where suggestions for fixing an input error are known, they are provided to the user
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

The product was tested for:

  • Submissions can be reversed by the user.
4.1.1 Parsing(Level A)Supports

The product was tested for

  • Markup languages aren't used to generate the user interface.
4.1.2 Name, Role, Value (Level A)Supports with Exceptions

The product was tested for:

  • User interface components have a programmatically associated AccessibleName and AccessibleRole as defined by the Java Accessibility API
  • State information, properties, and values are programmatically exposed for user interface components

Exceptions:

  1. Bug 8219340: The screen reader does not recognize elements in the Component Gallery dialog for the Gauge component.
  2. Bug 19970115: While debugging a test program, opening the Threads window and using the arrow keys to navigate through the table does not read out selected item. The key pressed is read out instead.
  3. Bug 22930397: When a profile activation rule for 'JDK Version' is added to the Project Object Model (POM) file, the 'Version Range Specification' hyperlink although focusable, cannot be opened using the keyboard.
  4. Bug 21206316: The sections separator labels in the Component Palette are not focusable.
  5. Bug 21217867: On the first page of the create application server wizard there are radio buttons to specify whether the server is an integrated or standalone web server. Screen reader does not read the selected button's value but just says web server radio button selected.

back to top

2017 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria
Conformance Level
Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.2.2 No Disruption of Accessibility FeaturesSupports

Product was tested for:

  • Software does not disrupt platform features that are defined in the platform documentation as accessibility features.
 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.2 Modification of Object InformationNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.3 Row, Column, and HeadersNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.4 ValuesNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.5 Modification of ValuesNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.6 Label RelationshipsNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.7 Hierarchical RelationshipsNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.8 TextNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.9 Modification of TextNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.10 List of ActionsNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.11 Actions on ObjectsNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.12 Focus CursorNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.13 Modification of Focus CursorNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.3.14 Event NotificationNot Applicable

The product is not a platform or does not have access to platform accessibility features

502.4 Platform Accessibility FeaturesNot Applicable

The product is not a platform or does not have access to platform accessibility features

 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesNot Supported

Bug 26184220 - Product does not permit user preferences

503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingSupports

See the responses in the WCAG 2.0 section of this report.

504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot Applicable

Oracle JDeveloper does not perform format conversion

504.2.2 PDF ExportNot Applicable

Product does not export PDF

504.3 PromptsSupports

Oracle JDeveloper provides Audit Rules functionality that allows provides users feedback on content to conform to Accessibility requirements.

504.4 TemplatesNot Applicable

Product does not provide templates

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

Please see About JDeveloper Accessibility for information on the accessibility features of Oracle JDeveloper.

602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Product documentation is in electronic format.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory. International hearing-impaired customers should use the TRS at +1.605.224.1837. An Oracle Support engineer will respond to technical issues according to the standard service request process.

back to top

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicableStandards/Guidelines, subject to Oracle's interpretation of those standards(available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.

This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.