Oracle Accessibility Conformance Report

The documentation was tested for:

• Images that convey information have meaningful alternative text using ALT
• Images that are decorative are marked up using ALT=”” or CSS background images
• Controls have an associated name
• Time-based media is not used
• Non-text characters are not used
• CAPTCHAs are not used

The launcher was tested for:

• Images that convey information have meaningful alternative text using ALT
• Images that are decorative are marked up using ALT="" or CSS background images
• Controls have an associated name
• Time-based media is not used
• Non-text characters are not used
• CAPTCHAs are not used

The documentation was tested for:

• User interface component labels are associated with the fields they are labeling.
• Headings are encoded with HTML heading tags
• List markup is used for marking up lists
• Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate.
• Layout tables use appropriate markup.
• Groups of components are marked up with their description.
• Style sheets are used only to change the layout and presentation on the screen.

The launcher was tested for:

• User interface component labels are associated with the fields they are labeling.
• Headings are encoded with HTML heading tags
• Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
• Groups of components are marked up with their description
• Style sheets are used only to change the layout and presentation on the screen

Exceptions:

Bug 36110274: In the project creation web application, and in the individual guides pages, some interactive controls are nested. Screen readers may not always announce them or can cause focus problems.

Bug 35240422: On the About page, a data table doesn't have an accessible name or header information. It requires adding the caption tag, or the aria-labelledby, aria-label, or title attributes.

Bug 35240468: On the Modules page, data tables do not have an accessible name or header information. It requires adding the caption tag, or the aria-labelledby, aria-label, or title attributes.

The documentation and the launcher were tested for:

• The sequence of elements in the DOM matches a logical reading sequence

The documentation and the launcher were tested for:

• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

The documentation and the launcher were tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.

Exceptions:

Bug 35240505: On a guide page, in responsive mode, portrait orientation, with the sidebar expanded, the page title is cut; code snippets are unreadable. Suggested workaround: hide the sidebar.

The documentation and the launcher were tested for:

• There are no text fields that collect information about the user.

The documentation and the launcher were tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, and font weight.
• Information conveyed by color has a contrast ratio of at least 3:1.

The documentation and the launcher were tested for: 

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

Exceptions:

Bug 35240632: In the project creation web application, the Basic/Advanced switcher, in the active state, has lower color contrast (2.46) between foreground and background than the minimum ratio allowed (4.5:1).

Bug 35240640: On the Getting Started page and individual guides pages, commands/code inside tags, inlined in the text, and links in the Related Documentation section do not have sufficient color contrast.

The documentation and the launcher were tested for:

• Text can be resized up to 200% without loss of content or functionality.

The documentation and the launcher were tested for:

• Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential.

The documentation and the launcher were tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.
• Content that requires a two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

The documentation and the launcher were tested for:

• Non-text items have a contrast ratio of at least 3:1.

The documentation and the launcher were tested for:

• When the following attributes and no others are modified there is no loss in functionality or content:
  • Line height (line spacing) to at least 1.5 times the font size
  • Spacing following paragraphs to at least 2 times the font size
  • Letter spacing (tracking) to at least 0.12 times the font size
  • Word spacing to at least 0.16 times the font size

The documentation and the launcher were tested for:

• Dismissable -The content can be dismissed without moving the pointer or keyboard focus.
• Hoverable - When the pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing.
• Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
• The visual presentation of the additional content is controlled by the user agent and is not modified by the author.

The documentation and the launcher were tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
• The ability to use the product with OS keyboard aids: Sticky Keys and Slow Keys

The documentation and the launcher were tested for:

• Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents the focus from moving away from any control.

The documentation and the launcher were tested for:

• There are no single-character keyboard shortcuts.

The documentation and the launcher were tested for:

• Time limits are not used.

The documentation and the launcher were tested for:

• There is no moving, blinking, or scrolling content.

The documentation and the launcher were tested for:

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

The documentation and the launcher were tested for:

• Structure and hierarchy are marked up with Header elements outside of repetitive navigation links.

The documentation and the launcher were tested for:

• Pages have a meaningful title specified in the TITLE element.

The documentation and the launcher were tested for:

• Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence.

The documentation and the launcher were tested for:

• The text of links and their surrounding paragraph, list, or table cell (with marked-up table headers), is sufficient to describe their purpose.

The documentation and the launcher were tested for:

• Pages are contained in a "site map."
• Pages are fully interlinked with each other.

The documentation and the launcher were tested for:

• Headers describe the topic or purpose of the content below them.
• Labels describe the purpose of the associated field.

The documentation and the launcher were tested for:

• Visual indication of the location of the focus.

Exception:

Bug 36847316: On the individual guides pages, the focus indicator is not visible on the "Copy" buttons within the code snippets.

The documentation and the launcher were tested for:

• There are no multipoint or path-based gesture actions.

The documentation and the launcher were tested for:

• There are no single pointer operations.

The documentation and the launcher were tested for:

• User interface components that include text or images of text and have a label; have a name that contains the text that is presented visually.

The documentation and the launcher were tested for:

• There are no functions that require motion of the device.

The documentation and the launcher were tested for:

• Properly set the lang attribute for each page.

The launcher was tested for:

• The launcher only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable.

The documentation was tested for:

• Proper use of lang attribute for text passages that are in a different language than that of the page

The documentation and the launcher were tested for:

• When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window.

The documentation and the launcher were tested for:

• Changes in the value of user interface components do not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window.

The documentation and the launcher were tested for:

• Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time

The documentation and the launcher were tested for:

• Images and controls are used and identified consistently throughout the product.

The launcher was tested for:

• When input errors are detected, they are described to the user in text, including identifying the item where the error occurred.

The documentation was tested for:

• The documentation does not have input fields.

The launcher was tested for:

• Labels or instructions are provided when the product requires user input.

The documentation was tested for:

• The documentation does not have input fields.

The launcher was tested for:

• Where suggestions for fixing an input error are known, they are provided to the user.

The documentation was tested for:

• The documentation does not have input fields.

The launcher was tested for:

• Data is checked for input errors with an opportunity for the user to correct them.
• Data can be reviewed, corrected, and confirmed by the user before they are finalized.

The documentation was tested for:

• The documentation does not require user input that modifies user-controllable data.

The documentation and the launcher were tested for:

• Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs.
• Pages validate to the HTML specification.

The documentation and the launcher were tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
• Frames have a meaningful title specified in the title attribute

Exception:

Bug 36749300: The learn more icons on the project creation wizard page, tagged with <a aria-hidden="true">, should not be focusable.

The documentation and the launcher were tested for:

• There are no status messages

The product documentation describes:

• Special keystrokes needed to operate controls
• Workarounds

Product documentation is in electronic format.