Oracle Accessibility Conformance Report

The product and documentation were 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
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

The Data Visualization components are SVG base and use the WAI-ARIA application role instead of HTML elements.

In the case of the Data Visualization components:

The product was tested for:

• Descriptive text about the content of the SVG element is provided via WAI-ARIA aria-label property in the HTML code.
• SVG sub-elements that correspond to navigable data items within a component use of the WAI-ARIA img role.
• The description of the structure of the component is provided via WAI-ARIA aria-label property in the HTML code.

Exceptions:

1. JET-78207: The informational image icon in the message banner (oj-message-banner) is missing an appropriate accessible text alternative.

The product and documentation were 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
• Style sheets are used only to change the layout and presentation on the screen
• info and relationship information is provided via wai-aria attributes in HTML code

The ojDataGrid, ojTable, and Data Visualization components use the WAI-ARIA application role instead of the HTML table or other HTML elements.

In the case of the ojDataGrid and ojTable components:

The product was tested for:

• Descriptive text about the content of the data grid is provided via WAI-ARIA aria-label property in the HTML code
• Description of the structure of the data grid is provided via WAI-ARIA aria-describedby property in HTML code
• Row and column headers are identified via WAI-ARIA aria-labelledby property in HTML code
• Data cells are associated with the appropriate headers via WAI-ARIA aria-labelledby property in HTML code
• Description about the action performed on the data grid is provided via WAI-ARIA status role and alert role in the HTML code

In the case of the Data Visualization components:

The product was tested for:

• Descriptive text about the content of the SVG element is provided via WAI-ARIA aria-label property in the HTML code.
• SVG sub-elements that correspond to navigable data items within a component use of the WAI-ARIA img role.
• The description of the structure of the component is provided via WAI-ARIA aria-label property in the HTML code.

Exceptions:

1. JET-75119: The screen reader is not reading the complete data in the data grid by default.
2. JET-76756: The list view (oj-list-view) reports an incorrect row count regardless of the actual number of rows.
3. JET-77506: The length validator does not announce character-count feedback after the limit is exceeded.
4. JET-78267: The split menu button (oj-c-split-menu-button) does not announce how to open menu options when a screen reader is active.
5. JET-78363: Automatic date adjustments are not announced when a month change alters the day value.
6. JET-77055: A truncated labelled link (oj-c-labelled-link) does not show a tooltip on long press.

The product and documentation were tested for:

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

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

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

The product and documentation were tested for

• Text fields which collect information about the user contain the appropriate autocomplete content attribute.

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

The product and documentation were tested for:

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

Exceptions:

1. JET-78946: At high zoom, list-of-values content is clipped and cannot be fully reached.

The product and documentation were tested for:

• Images of text are not used

The product and documentation were tested for

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.

Exceptions:

1. JET-70484: Dialog (oj-dialog) is not scrollable when content inside the dialog overflows with a browser zoom of 400%.
2. JET-77315: Select multiple dropdown (oj-c-select-multiple) options are not fully visible at 400% browser zoom.
3. JET-78442: Drawer (Drawer-Preact) layout focus does not return to the launcher when zoomed to 400%.
4. JET-78515: Nested List item layout (oj-list-item-layout) content overflows when zoomed at 200% onwards, causing information to be clipped.

The product and documentation were tested for:

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

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

• Dismissable -The content can be dismissed without moving the pointer or keyboard focus
• Hoverable - When 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.

Exceptions:

1. JET-69059: The data tip implementation needs to meet Content on Hover or Focus (Level AA) in the core pack components.
2. JET-78649: Icon-only mixed tabs in the Tab Bar Mixed (oj-c-tab-bar-mixed) do not consistently show a tooltip on mobile tap-and-hold.

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

1. JET-73982: Menu button (oj-menu-button) fails to fire action while using with a screen reader using the spacebar.
2. JET-60038: Tabbing a list item in a button set when in actionable mode should not leave the list item.
3. JET-70464: Keyboard navigation for Button (oj-button) requires two Tab presses to reach a button.
4. JET-73776: Single-select (oj-c-select-single) dropdown keyboard navigation does not cycle from the last option back to the first.
5. JET-73785: Multi-select dropdown (oj-c-select-multiple) keyboard navigation does not cycle from the last option back to the first.
6. JET-75806: Menu items (oj-menu-buttons) become misaligned and unreachable by keyboard on later openings.
7. JET-77092: Thematic map (oj-c-thematic-map) arrow-key navigation is inconsistent and can prevent keyboard users from finding regions predictably.
8. JET-77093: Diagram (oj-diagram) arrow-key navigation is inconsistent and can prevent keyboard users from finding nodes predictably.
9. JET-77411: Keyboard access for the multi-select combobox (oj-combobox-many) does not work when using a render template with managed tabs.
10. JET-78291: The color palette (oj-color-palette) is not reachable or operable with a screen reader.
11. JET-78413: The focus for the editable data grid (oj-data-grid), while navigating via keyboard, gets lost and is restored after multiple attempts of SHIFT+TAB when row headers are absent and cell templates are used.
12. JET-78456: The single-select (oj-c-select-single) list of values cannot be closed when a screen reader is active.
13. JET-78618: The drawer (oj-c-drawer) cannot be closed from a mobile screen reader workflow without an extended keyboard.
14. JET-78738: Popup (oj-c-popup) content cannot be reached using keyboard navigation.

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

• There are no single character keyboard shortcuts.

The product and documentation were tested for:

• Time limits are not used

The product and documentation were tested for:

• There is no moving, blinking or scrolling content.

The product and documentation were tested for:

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

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 are marked up with Header elements outside of repetitive navigation links
• WAI-ARIA Landmark elements are used outside of repetitive navigation links

This product does not provide complete web pages; therefore, this guideline does not apply.

The documentation was tested for:

• Pages have a meaningful title specified in the html "title" tag

This product does not provide complete web pages, therefore this guideline does not apply.

This framework does not provide complete web pages. However for the individual components provided by the framework that have flow,

The product and documentation were tested for:

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

Exceptions:

1. JET-55947: The select single dropdown (oj-select-single) does not keep screen reader focus inside the option list.
2. JET-77685: Input search (oj-input-search) suggestions do not move focus to the first result when results are available.
3. JET-78294: Input Date Picker (oj-c-input-date-picker) error messaging falls out of sync with screen reader focus.
4. JET-78458: The single-select (oj-c-select-single) control exposes unrelated content before the option list during screen reader navigation.

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

• Page contains controls that enable reaching other pages of our product
• Pages can be found using the provided "search" function

The product does not provide complete web pages, therefore this guideline does not apply.

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

• Visual indication of the location of the focus

Exceptions:

1. JET-75624: In the Menu Button (oj-c-menu-button), focus gets lost on selecting any menu option while using it with a screen reader on a mobile device.
2. JET-75069: Focus is not returned to the launcher when the toolbar (oj-toolbar) item has a negative tabindex.
3. JET-76227: Button set (oj-buttonset) focus is shown in the wrong location for screen reader workflows.
4. JET-76743: The focus indicator is not prominent enough for a primary action button (oj-c-button) in a drawer template.
5. JET-76819: Screen reader focus briefly moves to unrelated content when closing the drawer (oj-drawer).
6. JET-77049: The focus ring is too difficult to see in the color spectrum (oj-color-spectrum) demo.
7. JET-77142: The focus ring is missing when navigating between button-set (oj-c-buttonset) buttons with arrow keys.
8. JET-77149: Focus is dropped from the toolbar (oj-toolbar) after interacting with a progress button.
9. JET-77433: Button set (oj-c-buttonset) focus is displayed incorrectly during screen reader navigation.
10. JET-78498: Keyboard focus is lost when tabbing through Conveyor belt (oj-c-conveyor-belt) items at high browser zoom.
11. JET-78996: Keyboard focus on an editable table (oj-table) cell is not sufficiently visible.

The product and documentation were tested for:

• The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.

The product and documentation were tested for

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

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

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

The product and documentation were tested for:

• All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.

The product and documentation were tested for:

• Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.
• The function can be achieved through a different control in the same software that meets this criterion.
• The target is in a sentence, or its size is otherwise constrained by the line-height of non-target text.

Exceptions:

1. JET-78550: The text-tag outline overlaps its label in a small scale and compact density in the select multiple (oj-c-select-multiple).
2. JET-78868: Read-only form fields can report insufficient touch target size and spacing in the form layout (oj-form-layout).

Framework does not provide complete web pages, however the individual components provided by the framework were tested to meet this guideline.

The product and documentation were tested for:

• Properly set lang attribute for each page

The product and documentation were tested for:

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

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

• 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

The product does not provide complete web pages, therefore this guideline does not apply.

The product and documentation were tested for:

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

The product and documentation were tested for: 

• Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.

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.

Exxceptions:

1. JET-78652: Compact user-assistance popups are not visible on mobile devices in general for all form controls.

The product and documentation were tested for:

• Labels or instructions are provided when the product 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:

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

The product was tested for:

• 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 product and documentation were tested for:

• There are no occurrences of information that the user needs to enter which has been previously entered.

The product and documentation were tested for:

• Authentication is not required.

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

Exception:

1. JET-73231: When navigating through the button set (oj-c-buttonset) with the up/down arrow with the screen reader enabled, it announces each button as checked when it is not checked.
2. JET-66760: The IconButton with an aria-label renders a tooltip with the aria-describedby attribute pointing to it. But, when this aria-describedby is not removed when the tooltip is not shown. This results in the component having aria-describedby pointing to a non-existent ID.
3. JET-73590 With the screen reader enabled, when there are two buttons (oj-c-button) next to each other in a region, the second button reads out the region info again.
4. JET-75163: Table should have a role='grid' instead of role='application', which could help assistive technologies to recognize it as a table.
5. JET-65502: Compact user-assistance density can set aria-describedby to a missing element in the input text (oj-c-input-text).
6. JET-75122: A mobile screen reader can reach non-interactive content behind an open sheet in the menu button (oj-menu-button).
7. JET-76686: Overlay drawer (oj-drawer-*) layout allows touch interaction with content underneath the empty drawer area.
8. JET-76844: The screen reader, while reading an expand icon in the tree view (oj-tree-view), announces an expand/collapse action that does not work.
9. JET-78280: A mobile screen reader reads empty space in a menu sheet as a close button of the menu button (oj-menu-button).
10. JET-78286: A chart (oj-chart) exposes an undefined accessible label after re-rendering with more data.
11. JET-78451: The sort icon is announced as an image rather than its intended control meaning in the table (oj-table).
12. JET-78455: A screen reader can navigate to hidden live-region text in a single-select (oj-c-select-single) control.
13. JET-78457: A popup (oj-c-popup) causes the screen reader to announce encoded characters.
14. JET-78459: The multi-select combobox (oj-c-combobox-many) has screen reader interaction issues on a tablet.
15. JET-78519: Screen reader focus moves to hidden content and repeats the number of matches found in the select single (oj-c-select-single).
16. JET-78657: A truncating badge (oj-c-truncating-badge) remains focusable when its content is not truncated.
17. JET-78520: The row does not announce that it is selectable in the table (oj-table).

The product and documentation were tested for:

• Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

Exceptions:

1. JET-76518: The empty state announces "loaded" when no meaningful status update is needed in the list view (oj-c-list-view).
2. JET-78453: The combobox components (oj-combobox-*) announce filter and item-count information even when no list of values is provided.

The product was tested for:

• Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts.

Exceptions:

1. JET-72917: Buttonset (oj-buttonset) does not remain navigable when used with the screen reader.
2. JET-76558: A popup (oj-c-popup) can close from a hidden screen reader link without firing the before-close event.
3. JET-78234: The input date picker (oj-c-input-date-picker) sheet cannot be closed by mobile screen reader users without a hidden dismiss control.
4. JET-78379: A menu button (oj-menu-button) closes immediately after opening when a screen reader is active.
5. JET-78674: After selecting a menu button (oj-menu-button) item and navigating away, focus returns to the old menu button.

The  product was tested for:

• Responds to platform settings for color, contrast, font type, font size, and focus cursor

The product documentation describes:

• special keystrokes needed to operate controls
• workarounds

Accessibility-related documentation can be found at: Develop Accessible Oracle JET Apps.

A reference guide for keystrokes and touch gestures can be found at: https://www.oracle.com/pls/topic/lookup?ctx=jetlatest&id=OJACC

Product documentation is in electronic format.

Oracle JET is an open-source product that provides support through community forums only.  There is no phone-based support.

Technical Support can be found in the Community Forums at: 

https://community.oracle.com/tech/developers/categories/16409-oracle-jet

Oracle JET is an open-source product that provides support through community forums only.  There is no phone-based support.

Technical Support can be found in the Community Forums at: 

https://community.oracle.com/tech/developers/categories/16409-oracle-jet