Oracle Accessibility Conformance Report

The product 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
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
• Titles for Objects and Applets are provided
• Controls have an associated name
• Client-side image maps specify the ALT attribute on each AREA element.
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

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.
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table).
• Controls have an associated name.
• CAPTCHAs are not used.

This product 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 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.
• Data tables specify SUMMARY or CAPTION.
• 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 product was tested for:

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

The documentation was tested for:

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

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

The documentation 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.

This product was tested for:

• Product does not support landscape orientation. 

Bug ID 31977233 Accessibility - Workspace UI to support portrait orientation 

The documentation was tested for:

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

The product was tested for:

• This product is not designed to collect personal information of the user.

The documentation was tested for:

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

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

The documentation 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.

The product was 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

The documentation was 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.

The product was tested for:

• There is a loss of content/functionality and the layout gets distorted while resizing the text into 200%.

Bug ID: 31977378 - Loss of content/functionality while resizing the text to 200%

The documentation was tested for:

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

The product was tested for:

• Images of text are not used.

The documentation was 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 product was tested for:

• Vertical scrolling content at a width equivalent to 320 CSS pixels;
• Horizontal scrolling content at a height equivalent to 256 CSS pixels.

Bug 31989043 - Make Workspace UI to support Reflow 

The documentation was tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.
• An alternative mobile user interface is available and is accessed from the main application.

The product was tested for:

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

The documentation was tested for:

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

The product was 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 was 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 product was tested for:

• Dismissable: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
• Hoverable: If pointer hover can trigger the additional content, then 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 documentation was tested for:

• Information appears on hover or focus using default browser behavior, such as the title attribute of components.

The product was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
• Proper operation of unique keystrokes and access keys, including those listed in the product documentation
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)

The documentation was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes.

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.

The documentation 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.

The product was tested for:

• There are no single character keyboard shortcuts.

The documentation was tested for:

• There are no single character keyboard shortcuts.

The product was tested for:

• Time limits are not used.

The documentation was tested for:

• Time limits are not used.

The product was tested for:

• There is no moving, blinking or scrolling content.

The documentation was tested for:

• There is no moving, blinking or scrolling content.

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• Workspace UI is a "single page application" and not multiple web pages so there is no repeated content to skip.

The documentation was tested for:

• A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links.
• WAI-ARIA Landmark elements are used outside of repetitive navigation links.

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

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

The documentation was tested for:

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

The product was 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 was 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 product was tested for:

• Since the workspace UI is a "single page application" and not multiple web pages the criteria does not apply.

The documentation was tested for:

• Pages can be found using the provided "search" function.
• Pages are in a site table of contents.
• Pages are fully inter-linked to each other.
• Page contains controls that enable reaching all pages.

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• Visual indication of the location of the focus

The documentation was tested for:

• Visual indication of the location of the focus.

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function.

The documentation was tested for:

• There are no single pointer operations.

The product has been 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 has been 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.

This product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• Properly set lang attribute for each page

The documentation was tested for:

• Properly set lang attribute for each page.

This product was tested for:

• There are no text passages that are in a different language than that of the page.

The documentation was tested for:

• There are no text passages that are in a different language than that of the page.

The product was 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 was 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 product was tested for  

• Changes in the value of user interface components 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 was tested for:

• Changes in the value of user interface components 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 product was 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 was 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.

This product was tested for:

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

The documentation was tested for:

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

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.

The documentation was tested for:

• There are no input errors.

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

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

The documentation was tested for:

• There are no input errors.

The product does not manage or verify input of customer legal commitments or financial transactions. The customer uses the product to create business process workflows and thus has the responsibility to manage end user input of legal commitments or financial transactions. 

1. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
2. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

The documentation was tested for: 

• Documentation does not have input fields that change data.

The product was 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 was 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 product was tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
• Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’.
• Custom controls have appropriate roles specified using the role attribute.
• Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes.
• Custom controls have a meaningful programmatically exposed name.

The documentation was tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.

This product was tested for:

• In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. 

The documentation was tested for:

• There are no status messages.

The product documentation describes:

• Special keystrokes needed to operate controls
• Workarounds

Accessibility-related documentation can be found at:  https://docs.oracle.com/en/cloud/accessibility/accessibility-features-and-tips-oracle-digital-assistant.html#GUID-53B55D8A-5DD8-4501-B2C9-B4618D768CF1

Product documentation is in electronic format.