Name of Product: Oracle JDeveloper 12.2.1.2.0

Last Updated:05-Oct-2016

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

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

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
This document describes the extent to which the product conforms to the Web Content Accessibility Guidelines (WCAG) 2.0 'A' and 'AA' levels as described at http://www.w3.org/TR/WCAG20/, and the applicable U.S. Section 508 standards, subject to Oracle's interpretation of those standards and the remarks in this document. If this product has dependencies on other products, they are stated at the end of this VPAT and they may or may not meet the WCAG 2.0 criteria. Please see the individual VPATs for details. We are using a format similar to the Voluntary Product Accessibility Template, or VPAT®. There are three columns in the tables. The first column contains each of the WCAG 2.0 A and AA Success Criteria or Section 508 criteria; the second column indicates whether the product meets the criterion, and the third column contains remarks about the product with regard to the criterion, including known defects, if any.

For more information regarding the accessibility status of this product or other Oracle products, see https://www.oracle.com/accessibility/ or contact:accessible_ww@oracle.com.


Note: This document is provided for information purposes only and the contentshereof are subject to change without notice. Oracle Corporationdoes not warrant that this document is error free, nordoes it provide any other warranties or conditions, whether expressedorally or implied in law, including implied warranties and conditionsof merchantability or fitness for a particular purpose. Oracle Corporationspecifically disclaims any liability with respect to this documentand no contractual obligations are formed either directly or indirectlyby this document. Oracle further makes no representation concerning the ability ofassistive technologies or other products to interoperate with Oracle products.This document addresses the named product(s) only and not prerequisite products for whichOracle supplies restricted use licenses.

Section WCAG Web Content Accessibility Guidelines

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1.1.1 Non-text Content: All non-text content thatis presented to the user has a text alternative that serves theequivalent purpose, except for the situations listed below. (Level A)
  • Controls, Input: Ifnon-text content is a control or accepts user input, then it has a namethat describes its purpose. (Refer to Guideline 4.1 for additionalrequirements for controls and content that accepts user input.)
  • Time-Based Media: Ifnon-text content is time-based media, then text alternatives at leastprovide descriptive identification of the non-text content. (Refer toGuideline 1.2 for additional requirements for media.)
  • Test: Ifnon-text content is a test or exercise that would be invalid ifpresented in text, then text alternatives at least provide descriptiveidentification of the non-text content.
  • Sensory: Ifnon-text content is primarily intended to create a specific sensoryexperience, then text alternatives at least provide descriptiveidentification of the non-text content.
  • CAPTCHA: If the purpose of non-textcontent is to confirm that content is being accessed by a person ratherthan a computer, then text alternatives that identify and describe thepurpose of the non-text content are provided, and alternative forms ofCAPTCHA using output modes for different types of sensory perceptionare provided to accommodate different disabilities.
  • Decoration, Formatting, Invisible: Ifnon-text content is pure decoration, is used only for visualformatting, or is not presented to users, then it is implemented in away that it can be ignored by assistive technology.
Product has been developed to conform to this standard subject to the remarks on the right.

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 23025919: The Uniform Resource Locator (URL) drop down text in the Sources accordion of a team server is not read by the screen reader.
  14. Bug 23025669: The text in the Find Tasks option of the Tasks accordion is unreadable for High Contrast themes with Windows Look and Feel.
  15. 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.
  16. 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.
  17. 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.
  18. 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.
  19. 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.
  20. 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.
  21. 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.
  22. 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.
  23. 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): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: (Level A)
  • Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.

  • Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.

Product has been developed to conform to this standard subject to the remarks on the right.

Audio/video content is not included in the product.

1.2.2 Captions (Prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearlylabeled as such. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

Audio/video content is not included in the product.

1.2.3 Audio Description or Media Alternative (Prerecorded): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

Audio/video content is not included in the product.

1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

Audio/video content is not included in the product.

1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

Audio/video content is not included in the product.

1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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:When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • The accessibility hierarchy is logical
1.3.3 Sensory Characteristics:Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A)
Note:For requirements related to color, refer to Guideline 1.4.
Product has been developed to conform to this standard subject to the remarks on the right.

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:Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A)
Note:This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.
Product has been developed to conform to this standard subject to the remarks on the right.

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:If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A)
Note:Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
Product has been developed to conform to this standard subject to the remarks on the right.

Audio/video content is not included in the product.

1.4.3 Contrast (Minimum):The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA)
  • Large Text:Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
  • Incidental:Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
  • Logotypes:Text that is part of a logo or brand name has no minimum contrast requirement.
Product has been developed to conform to this standard subject to the remarks on the right.

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 21922246: The bottom borders of the Overview editor for the faces configuration file (faces-config.xml) are not visible in High Contrast White theme.
  2. Bug 23039096: The list of projects is not visible in the search tab of the Resource Bundle node in High Contrast Black theme.
  3. 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.
  4. 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.
  5. 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.
  6. Bug 23039029: The advanced menu options in the property inspector are not fully visible in High Contrast themes with Windows Look & Feel.
  7. 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.
  8. Bug 23038970: Section headers are not properly visible in the editor UI for database files in High Contrast themes with Windows Look & Feel.
  9. 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.
  10. Bug 23038365: When a file list is opened for an application and ‘Date modified’ is chosen as the first dropdown value, the UI and the date values are not clearly visible in High Contrast themes with Windows Look & Feel.
  11. 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.
  12. Bug 23038292: The application description on the Create New Application dialog is not clearly visible in High Contrast themes with Windows Look & Feel.
  13. Bug 22981133: When using Oracle Look & Feel, all radio buttons have a contrast ratio (when selected) smaller than 3:1.
  14. 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.
  15. Bug 22386224: Data in the ‘Issues’ window is not readable in High Contrast themes.
  16. 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.
  17. Bug 21932303: The text in the Application Overview page becomes unreadable in High Contrast themes with Windows Look & Feel.
  18. Bug 21932168: Upon configuring a team server, finding and selecting a project from the search list makes the text unreadable in High Contrast themes with Windows Look & Feel.
  19. Bug 21932151: In the team server interface, formatting issues seen in the activity stream that is displayed upon clicking the Dashboard link in High Contrast themes with Windows Look & Feel.
  20. Bug 21932137: When a team server is configured, the confirmation dialog that comes up upon clicking 'Finish' is unreadable in High Contrast themes with Windows Look & Feel.
  21. Bug 21932112: Most of the headers in the Task editor are not readable using High Contrast themes with Windows Look & Feel.
  22. 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.
  23. 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.
  24. 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:Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Text can be resized up to 200% without loss of content or functionality
1.4.5 Images of Text:If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA)
  • Customizable:The image of text can be visually customized to the user's requirements;
  • Essential:A particular presentation of text is essential to the information being conveyed.
Note:Logotypes (text that is part of a logo or brand name) are considered essential.
Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Images of text are not used
2.1.1 Keyboard:All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)
Note 1:This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.
Note 2:This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.
Product has been developed to conform to this standard subject to the remarks on the right.

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 23042447: From the snapshot window of the profiler, unable to navigate to the different snapshot buttons using the keyboard.
  6. Bug 23040062: Screen reader does not read toolbar buttons when navigating using the keyboard.
  7. Bug 23033571: Using just the keyboard, unable to navigate to any toolbar button. The workaround is to use the equivalent menu options.
  8. Bug 22956783: Keyboard navigation using up and down arrow keys does not work for the property menu list in the Property Inspector.
  9. 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.
  10. Bug 22392583: Unable to switch from the default tab in the Log view using the keyboard.
  11. Bug 22392547: Using the keyboard, unable to navigate between all the items in the Team view.
  12. Bug 21629682: From the Log window, the system menus do not come up when using the keyboard shortcuts.
  13. Bug 21453491: It is not possible to access the project dropdown or tasks under the Task accordion in the Team view using the keyboard.
  14. 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.
  15. 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.
  16. Bug 22956467: When a shortcut key (Alt + r) is pressed on the Global Search page, the run menu is invoked instead of selecting the Results Filter.
  17. 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.
  18. 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.1.2 No Keyboard Trap:If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)
Note:Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
Product has been developed to conform to this standard subject to the remarks on the right.

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:For each time limit that is set by the content, at least one of the following is true: (Level A)
  • Turn off:The user is allowed to turn off the time limit before encountering it; or
  • Adjust:The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend:The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception:The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception:The time limit is essential and extending it would invalidate the activity; or
  • 20 Hour Exception:The time limit is longer than 20 hours.
Note:This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.
Product has been developed to conform to this standard subject to the remarks on the right.

There is no time sensitive content included in the product.

2.2.2 Pause, Stop, Hide:For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)
  • Moving, blinking, scrolling:For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
  • Auto-updating:For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Note 1:For requirements related to flickering or flashing content, refer to Guideline 2.3.
Note 2:Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
Note 3:Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.
Note 4:An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.
Product has been developed to conform to this standard subject to the remarks on the right.

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

2.3.1 Three Flashes or Below Threshold:Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A)
Note:Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
Product has been developed to conform to this standard subject to the remarks on the right.

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

2.4.1 Bypass Blocks:A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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:Web pages have titles that describe topic or purpose. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • The name of the software application is meaningful.
2.4.3 Focus Order:If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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):The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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:More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

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:Headings and labels describe topic or purpose. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

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:Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

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:The default human language of each Web page can be programmatically determined. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Properly set locale/language
3.1.2 Language of Parts:The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

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:When any component receives focus, it does not initiate a change of context. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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:Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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:Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

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:Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification:If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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:Labels or instructions are provided when content requires user input. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion:If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

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):For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA)
  1. Reversible:Submissions are reversible.
  2. Checked:Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
  3. Confirmed:A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Submissions can be reversed by the user.
4.1.1 Parsing:In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A)
Note:Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.
Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for

  • Markup languages aren't used to generate the user interface.
4.1.2 Name, Role, Value:For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
Note:This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.
Product has been developed to conform to this standard subject to the remarks on the right.

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 22956467: When a shortcut key (Alt + r) is pressed on the Global Search page, the run menu is invoked instead of selecting the Results Filter.
  4. 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.
  5. Bug 21206316: The sections separator labels in the Component Palette are not focusable.
  6. 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

Section 1194.21 Software Applications and Operating Systems

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.21(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

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 23042447: From the snapshot window of the profiler, unable to navigate to the different snapshot buttons using the keyboard.
  6. Bug 23040062: Screen reader does not read toolbar buttons when navigating using the keyboard.
  7. Bug 23033571: Using just the keyboard, unable to navigate to any toolbar button. The workaround is to use the equivalent menu options.
  8. Bug 22956783: Keyboard navigation using up and down arrow keys does not work for the property menu list in the Property Inspector.
  9. 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.
  10. Bug 22392583: Unable to switch from the default tab in the Log view using the keyboard.
  11. Bug 22392547: Using the keyboard, unable to navigate between all the items in the Team view.
  12. Bug 21629682: From the Log window, the system menus do not come up when using the keyboard shortcuts.
  13. Bug 21453491: It is not possible to access the project dropdown or tasks under the Task accordion in the Team view using the keyboard.
  14. 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.
  15. 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.
  16. Bug 22956467: When a shortcut key (Alt + r) is pressed on the Global Search page, the run menu is invoked instead of selecting the Results Filter.
  17. 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.
  18. 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'.
  19. Bug 22930661: In the Import Maven Projects dialog, pressing 'Space' to activate the Refresh button shifts the focus to checkbox 'Also import source files into application'.
  20. 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.
1194.21(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. Product has been developed to conform to this standard subject to the remarks on the right.

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 23042447: From the snapshot window of the profiler, unable to navigate to the different snapshot buttons using the keyboard.
  6. Bug 23040062: Screen reader does not read toolbar buttons when navigating using the keyboard.
  7. Bug 23033571: Using just the keyboard, unable to navigate to any toolbar button. The workaround is to use the equivalent menu options.
  8. Bug 22956783: Keyboard navigation using up and down arrow keys does not work for the property menu list in the Property Inspector.
  9. 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.
  10. Bug 22392583: Unable to switch from the default tab in the Log view using the keyboard.
  11. Bug 22392547: Using the keyboard, unable to navigate between all the items in the Team view.
  12. Bug 21629682: From the Log window, the system menus do not come up when using the keyboard shortcuts.
  13. Bug 21453491: It is not possible to access the project dropdown or tasks under the Task accordion in the Team view using the keyboard.
  14. 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.
  15. 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.
  16. Bug 22956467: When a shortcut key (Alt + r) is pressed on the Global Search page, the run menu is invoked instead of selecting the Results Filter.
  17. 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.
  18. 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.
1194.21(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Visual indication of the location of the focus
  • 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 21206316: The focus indicator is not shown on the sections separator labels of the Component Palette.
  2. Bug 8219340: The screen reader does not recognize elements in the Component Gallery dialog for the Gauge component.
  3. 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.
  4. Bug 22956467: When a shortcut key (Alt + r) is pressed on the Global Search page, the run menu is invoked instead of selecting the Results Filter.
  5. 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.
  6. Bug 21206316: The sections separator labels in the Component Palette are not focusable.
  7. 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.
1194.21(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology. When an image represents a program element, the information conveyed by the image must also be available in text. Product has been developed to conform to this standard subject to the remarks on the right.

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
  • 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

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 22956467: When a shortcut key (Alt + r) is pressed on the Global Search page, the run menu is invoked instead of selecting the Results Filter.
  4. 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.
  5. Bug 21206316: The sections separator labels in the Component Palette are not focusable.
  6. 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.
  7. 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.
  8. 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”.
  9. 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".
  10. Bug 23033596: Every tree node in the Hooks tab of extension.xml is read multiple times when navigating using the keyboard.
  11. 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.
  12. 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.
  13. Bug 23031692: Screen reader incorrectly reads out column headers when editing a table after online database connection is created.
  14. 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.
  15. Bug 23031663: Screen reader incorrectly reads out the title and fields when a tablespace in an online database is edited.
  16. Bug 23031653: Screen reader incorrectly reads out the title and fields when a sequence in an online database is edited.
  17. 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.
  18. 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.
  19. Bug 23025919: The Uniform Resource Locator (URL) drop down text in the Sources accordion of a team server is not read by the screen reader.
  20. Bug 23025669: The text in the Find Tasks option of the Tasks accordion is unreadable for High Contrast themes with Windows Look and Feel.
  21. 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.
  22. 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.
  23. 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.
  24. 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.
  25. 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.
  26. 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.
  27. 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.
  28. 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.
  29. 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.
1194.21(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Images and controls are used and identified consistently throughout the product
  • 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
1194.21(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Text is rendered through the platform controls which are responsible for exposing content in a way that is programmatically available to assistive technology on the platform.
1194.21(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Product has been developed to conform to this standard subject to the remarks on the right.

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
  • Response to the operating system High Contrast mode
  • Response to the operating system Large Fonts mode

Exceptions:

  1. Bug 21922246: The bottom borders of the Overview editor for the faces configuration file (faces-config.xml) are not visible in High Contrast White theme.
  2. Bug 23039096: The list of projects is not visible in the search tab of the Resource Bundle node in High Contrast Black theme.
  3. 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.
  4. 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.
  5. 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.
  6. Bug 23039029: The advanced menu options in the property inspector are not fully visible in High Contrast themes with Windows Look & Feel.
  7. 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.
  8. Bug 23038970: Section headers are not properly visible in the editor UI for database files in High Contrast themes with Windows Look & Feel.
  9. 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.
  10. Bug 23038365: When a file list is opened for an application and ‘Date modified’ is chosen as the first dropdown value, the UI and the date values are not clearly visible in High Contrast themes with Windows Look & Feel.
  11. 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.
  12. Bug 23038292: The application description on the Create New Application dialog is not clearly visible in High Contrast themes with Windows Look & Feel.
  13. Bug 22981133: When using Oracle Look & Feel, all radio buttons have a contrast ratio (when selected) smaller than 3:1.
  14. 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.
  15. Bug 22386224: Data in the ‘Issues’ window is not readable in High Contrast themes.
  16. 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.
  17. Bug 21932303: The text in the Application Overview page becomes unreadable in High Contrast themes with Windows Look & Feel.
  18. Bug 21932168: Upon configuring a team server, finding and selecting a project from the search list makes the text unreadable in High Contrast themes with Windows Look & Feel.
  19. Bug 21932151: In the team server interface, formatting issues seen in the activity stream that is displayed upon clicking the Dashboard link in High Contrast themes with Windows Look & Feel.
  20. Bug 21932137: When a team server is configured, the confirmation dialog that comes up upon clicking 'Finish' during new project creation is unreadable in High Contrast themes with Windows Look & Feel.
  21. Bug 21932112: Most of the headers in the Task editor are not readable using High Contrast themes with Windows Look & Feel.
  22. 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.
  23. 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.
  24. 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.
1194.21(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. Not Applicable

There is no animation included in the product.

1194.21(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Product has been developed to conform to this standard subject to the remarks on the right.

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
1194.21(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided. Product has been developed to conform to this standard subject to the remarks on the right.

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 21922246: The bottom borders of the Overview editor for the faces configuration file (faces-config.xml) are not visible in High Contrast White theme.
  2. Bug 23039096: The list of projects is not visible in the search tab of the Resource Bundle node in High Contrast Black theme.
  3. 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.
  4. 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.
  5. 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.
  6. Bug 23039029: The advanced menu options in the property inspector are not fully visible in High Contrast themes with Windows Look & Feel.
  7. 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.
  8. Bug 23038970: Section headers are not properly visible in the editor UI for database files in High Contrast themes with Windows Look & Feel.
  9. 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.
  10. Bug 23038365: When a file list is opened for an application and ‘Date modified’ is chosen as the first dropdown value, the UI and the date values are not clearly visible in High Contrast themes with Windows Look & Feel.
  11. 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.
  12. Bug 23038292: The application description on the Create New Application dialog is not clearly visible in High Contrast themes with Windows Look & Feel.
  13. Bug 22981133: When using Oracle Look & Feel, all radio buttons have a contrast ratio (when selected) smaller than 3:1.
  14. 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.
  15. Bug 22386224: Data in the ‘Issues’ window is not readable in High Contrast themes.
  16. 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.
  17. Bug 21932303: The text in the Application Overview page becomes unreadable in High Contrast themes with Windows Look & Feel.
  18. Bug 21932168: Upon configuring a team server, finding and selecting a project from the search list makes the text unreadable in High Contrast themes with Windows Look & Feel.
  19. Bug 21932151: In the team server interface, formatting issues seen in the activity stream that is displayed upon clicking the Dashboard link in High Contrast themes with Windows Look & Feel.
  20. Bug 21932137: When a team server is configured, the confirmation dialog that comes up upon clicking 'Finish' during new project creation is unreadable in High Contrast themes with Windows Look & Feel.
  21. Bug 21932112: Most of the headers in the Task editor are not readable using High Contrast themes with Windows Look & Feel.
  22. 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.
  23. 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.
  24. 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.
1194.21(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. Not Applicable

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

1194.21(l) When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Labels or instructions are provided when the product requires user input
  • 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 22956467: When a shortcut key (Alt + r) is pressed on the Global Search page, the run menu is invoked instead of selecting the Results Filter.
  4. 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.
  5. Bug 21206316: The sections separator labels in the Component Palette are not focusable.
  6. 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

Section 1194.22 Web-based Internet Information and Applications

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.22(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). Not Applicable 
1194.22(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Not Applicable 
1194.22(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Not Applicable 
1194.22(d) Documents shall be organized so they are readable without requiring an associated style sheet. Not Applicable 
1194.22(e) Redundant text links shall be provided for each active region of a server-side image map. Not Applicable 
1194.22(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. Not Applicable 
1194.22(g) Row and column headers shall be identified for data tables. Not Applicable 
1194.22(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. Not Applicable 
1194.22(i) Frames shall be titled with text that facilitates frame identification and navigation. Not Applicable 
1194.22(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Not Applicable 
1194.22(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. Not Applicable 
1194.22(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. Not Applicable 
1194.22(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with ยง1194.21(a) through (l). Not Applicable 
1194.22(n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Not Applicable 
1194.22(o) A method shall be provided that permits users to skip repetitive navigation links. Not Applicable 
1194.22(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not Applicable 

Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) - 1.1, (b) - 1.4, (c) - 2.1, (d) - 6.1, (e) - 1.2, (f) - 9.1, (g) - 5.1, (h) - 5.2, (i) - 12.1, (j) - 7.1, (k) - 11.4.

back to top

Section 1194.23 Telecommunications Products

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.23(a) Telecommunications products or systems which provide a function allowing voice communication and which do not themselves provide a TTY functionality shall provide a standard non-acoustic connection point for TTYs. Microphones shall be capable of being turned on and off to allow the user to intermix speech with TTY use. Not Applicable 
1194.23(b) Telecommunications products which include voice communication functionality shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols. Not Applicable 
1194.23(c) Voice mail, auto-attendant, and interactive voice response telecommunications systems shall be usable by TTY users with their TTYs. Not Applicable 
1194.23(d) Voice mail, messaging, auto-attendant, and interactive voice response telecommunications systems that require a response from a user within a time interval, shall give an alert when the time interval is about to run out, and shall provide sufficient time for the user to indicate more time is required. Not Applicable 
1194.23(e) Where provided, caller identification and similar telecommunications functions shall also be available for users of TTYs, and for users who cannot see displays. Not Applicable 
1194.23(f) For transmitted voice signals, telecommunications products shall provide a gain adjustable up to a minimum of 20 dB. For incremental volume control, at least one intermediate step of 12 dB of gain shall be provided. Not Applicable 
1194.23(g) If the telecommunications product allows a user to adjust the receive volume, a function shall be provided to automatically reset the volume to the default level after every use. Not Applicable 
1194.23(h) Where a telecommunications product delivers output by an audio transducer which is normally held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided. Not Applicable 
1194.23(i) Interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) shall be reduced to the lowest possible level that allows a user of hearing technologies to utilize the telecommunications product. Not Applicable 
1194.23(j) Products that transmit or conduct information or communication, shall pass through cross-manufacturer, non-proprietary, industry-standard codes, translation protocols, formats or other information necessary to provide the information or communication in a usable format. Technologies which use encoding, signal compression, format transformation, or similar techniques shall not remove information needed for access or shall restore it upon delivery. Not Applicable 
1194.23(k)(1) For products which have mechanically operated controls or keys, controls and keys shall be tactilely discernible without activating the controls or keys. Not Applicable 
1194.23(k)(2) For products which have mechanically operated controls or keys, controls do not require tight grasping, pinching or twisting of the wrist to operate. Not Applicable 
1194.23(k)(3) If key repeat is supported, the delay before repeat shall be adjustable to at least 2 seconds. Key repeat rate shall be adjustable to 2 seconds per character. Not Applicable 
1194.23(k)(4) The status of all locking or toggle controls or keys shall be visually discernible, and discernible either through touch or sound. Not Applicable 

back to top

Section 1194.24 Video and Multimedia Products

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.24(a) All analog television displays 13 inches and larger, and computer equipment that includes analog television receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals. As soon as practicable, but not later than July 1, 2002, widescreen digital television (DTV) displays measuring at least 7.8 inches vertically, DTV sets with conventional displays measuring at least 13 inches vertically, and stand-alone DTV tuners, whether or not they are marketed with display screens, and computer equipment that includes DTV receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals. Not Applicable 
1194.24(b) Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry. Not Applicable 
1194.24(c) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain speech or other audio information necessary for the comprehension of the content, shall be open or closed captioned. Not Applicable 
1194.24(d) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain visual information necessary for the comprehension of the content, shall be audio described. Not Applicable 
1194.24(e) Display or presentation of alternate text presentation or audio descriptions shall be user-selectable unless permanent. Not Applicable 

back to top

Section 1194.25 Self Contained, Closed Products

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.25(a) Self contained products shall be usable by people with disabilities without requiring an end-user to attach assistive technology to the product. Personal headsets for private listening are not assistive technology. Not Applicable 
1194.25(b) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not Applicable 
1194.25(c) Where a product utilizes touchscreens or contact-sensitive controls, an input method shall be provided that complies with Section 1194.23 (k) (1) through (4). Not Applicable 
1194.25(d) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided. Not Applicable 
1194.25(e) When products provide auditory output, the audio signal shall be provided at a standard signal level through an industry standard connector that will allow for private listening. The product must provide the ability to interrupt, pause, and restart the audio at anytime. Not Applicable 
1194.25(f) When products deliver voice output in a public area, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. Where the ambient noise level of the environment is above 45 dB, a volume gain of at least 20 dB above the ambient level shall be user selectable. A function shall be provided to automatically reset the volume to the default level after every use. Not Applicable 
1194.25(g) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Not Applicable 
1194.25(h) When a product permits a user to adjust color and contrast settings, a range of color selections capable of producing a variety of contrast levels shall be provided. Not Applicable 
1194.25(i) Products shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Not Applicable 
1194.25(j)(1) The position of any operable control shall be determined with respect to a vertical plane, which is 48 inches in length, centered on the operable control, and at the maximum protrusion of the product within the 48 inch length on products which are freestanding, non-portable, and intended to be used in one location and which have operable controls. Not Applicable 
1194.25(j)(2) Where any operable control is 10 inches or less behind the reference plane, the height shall be 54 inches maximum and 15 inches minimum above the floor. Not Applicable 
1194.25(j)(3) Where any operable control is more than 10 inches and not more than 24 inches behind the reference plane, the height shall be 46 inches maximum and 15 inches minimum above the floor. Not Applicable 
1194.25(j)(4) Operable controls shall not be more than 24 inches behind the reference plane. Not Applicable 

back to top

Section 1194.26 Desktop and Portable Computers

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.26(a) All mechanically operated controls and keys shall comply with Section 1194.23 (k) (1) through (4). Not Applicable 
1194.26(b) If a product utilizes touchscreens or touch-operated controls, an input method shall be provided that complies with Section 1194.23 (k) (1) through (4). Not Applicable 
1194.26(c) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided. Not Applicable 
1194.26(d) Where provided, at least one of each type of expansion slots, ports and connectors shall comply with publicly available industry standards. Not Applicable 

back to top

Section 1194.31 Functional Performance Criteria

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.31(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided. YesSubject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards.
 
1194.31(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for assistive technology used by people who are visually impaired shall be provided. YesSubject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for assistive technology used by people who are deaf or hard of hearing shall be provided. YesSubject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. YesSubject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for assistive technology used by people with disabilities shall be provided. YesSubject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. YesSubject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 

back to top

Section 1194.41 Information, Documentation and Support

Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.41(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. Documentation for this product is provided in HTML format with limited exceptions. 
1194.41(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. Documentation for this product is provided in HTML format with limited exceptions.  
1194.41(c) Support services for products shall accommodate the communication needs of end-users with disabilities. Oracle 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