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
• Text summary or alternative is provided for time-based media
• Client-side image maps specify the ALT attribute on each AREA element.

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
• Information not conveyed using time-based media
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

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

Exceptions :

    Bug 36605504 – The af:SelectOneListbox is missing a label value.

    Bug 31971977 – An af:SelectOneChoice with mode=compact is missing a label value.

The product was tested for:

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

Exceptions :

• Bug 36605602 – Screen Reader is not reading the characters when navigating through keyboard on HTTP Analyzer.

The documentation was tested for:

• HTML markup and coding of text that provides a correct and 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
• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

The documentation was tested for:

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

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• Inputs that define a matching purpose are properly identified
• Framework inputs that could be set a matching purpose allow proper identification

The documentation was tested for:

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

Exceptions :

• Bug  32002282 - An inputText created with secret=true does not allow the setting of an autocomplete value.

The product was tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, font weight

The documentation was tested for:

• Information is not conveyed using color

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
• All other text and images of text have a contrast ratio of at least 4.5:1

This product was tested for:

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

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

• Images of text are not used

The product was tested for:

• applicable content does not have two dimensional scrolling at 320px width and 256px height

Exceptions :

• Bug 30924364 - ADF application templates do not meet small screen reflow requirements.
• Bug 30986098 - Longer calendar activity titles get cut off when the activity box is not wide enough to accommodate the user provided text.

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 not available
• Content that requires two-dimensional layout only presents scroll bars in the component used
  to present the two-dimensional content

The product was tested for:

• applicable non-text content meets color contrast requirements

The documentation was tested for:

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

Exceptions :

• Bug 31043778 - Selected row and column indicators do not meet contrast requirements
• Bug 31043753 - Column and row headers do not meet contrast requirements
• Bug 32315276 - The af:InputColor drop down indicator does not meet contrast requirements.
• Bug 32025490 - The af:QuickQuery drop down indicator does not meet contrast requirements.

The product was tested for:

• Text spacing of line height (line spacing) can be adjusted to at least 1.5 times the font size
• Text spacing of following paragraphs is can be adjusted to at least 2 times the font size
• Letter spacing (tracking) can be adjusted to at least 0.12 times the font size
• Word spacing can be adjusted 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:

• Content on hover or focus being dismissable, hoverable, and persistent

The documentation was tested for:

• There is no content that appears on hover or focus

The product and documentation 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)

Exceptions:

• Bug 28573952   - Having problems using the keyboard to open and close tree nodes while using screen reader

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

• keyboard shortcuts implemented using only a letter, punctuation, number, or symbol can be either turned off, remapped, or are active only on focus

The product was tested for:

• Any application timeouts can either be turned off, adjusted, extended, or have a proper exception

Note that an ADF application by default will display a session timeout warning after 60 minutes of no interaction. The warning allows 120 seconds for a response. Both the session timeout and the length the warning popup allows are  configurable for individual apps. Besides this, there are no other time sensitive content included in the product.

The documentation was tested for:

• Time limits are not used

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

The product and 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:

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

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

The product was tested for:

• Pages have a meaningful title specified in the TITLE element

Exception:

• Bug 28630020 – Screen Reader is not reading the characters when navigating through keyboard on HTTP Analyzer.

The documentation was tested for:

• Pages have a meaningful title specified in the TITLE element

The product and 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, 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:

• Pages are contained in a "site map"
• 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 documentation was tested for:

• Pages can be found using the provided "Search" function
• Pages are fully inter-linked to each other
• Pages contain controls that enable reaching other pages

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

• Visual indication of the location of the focus

The product was tested for:

• Multipoint or path-based gesture actions can be completed using a different input modality

The documentation was tested for:

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

The product and documentation was tested for:

• When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion

The product was tested for:

• assigned labels matching the visibly displayed label text

The documentation has been tested for:

• There are no user interface components labeled with text or images of text.

The product and documentation was tested for:

• functionality that can be operated by device motion or user motion can also be operated by user interface components

The product and documentation was tested for:

• Properly set lang attribute for each page.

The product and documentation was tested for:

• Proper use of lang attribute for 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:

• In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components

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 and 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.

The product and documentation was tested for:

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

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:

• The documentation does not have input fields, except for the Search field

The product was tested for:

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

The documentation was tested for:

• Content does not require user input

ADF does not provide suggestions for error correction.

The documentation was tested for:

• Content does not require user input

The product was tested for:

• Submissions can be reversed by the user
• 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

This 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

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
• Frames have a meaningful title specified in the title attribute

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.
• Frames have a meaningful title specified in the title attribute

The product was tested for:

• status messages are coded to be presented to the user by assistive technologies without receiving focus

The documentation was tested for:

• There are no status messages

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

Product does not perform format conversion

Product does not export PDF files

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

BUG 26193542 Product does not provide templates

ADF renders accessible content, when an application developer uses it according to guidance provided in the reference manual, and follows all other applicable accessibility standards and guidelines.

The ADF accessibility information is provided in the Oracle Fusion Middleware Accessibility Guide in the Accessibility Features and Tips for Oracle JDeveloper and Oracle ADF chapter.

Product documentation is in electronic format.