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.

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-75329: While using the oj-c-buttonset-single on a mobile device, the screen reader focus goes to the button label, but it does not give any information about it; the user needs to swipe again, and then the focus goes on the entire button.
2. JET-74439: The screen reader reads dialog aria-describedby text when the user tabs from a field in the "body" slot to a button in the "footer" slot.

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.

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-75661: The default focused submenu option should be visible when the submenu opens, unlike currently when the user has to scroll to view it at 400% browser zoom.
3. JET-77315: At 400% browser zoom, options in the oj-c-select-multiple dropdown should be fully visible, like how it appears in the JET cookbook demo.
4. JET-76915: At 400% browser zoom, when the context menu opens, the default focused option should be visible; focus is seen only when we press the up/down arrow.

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 in the core pack data visualization components are missing the ‘Hoverable’ criteria.

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 using the spacebar while being used with a screen reader enabled.
2. JET-60038: Tabbing a list item in a button set (oj-buttonset) when in actionable mode should not leave the list item.
3. JET-73785: The Select Multiple dropdown fails cyclic keyboard navigation, preventing seamless movement from the last to the first option.
4. JET-73776: The Select Single dropdown lacks cyclic keyboard navigation, failing to loop from the last to the first option for screen reader users.
5. JET-76443: After collapsing the submenu (oj-c-menu-button) with a screen reader enabled in mobile, double-tap fails to reopen it.

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-76205: Swiping forward in any of the chips in the popup (oj-c-popup) leads to focus jumping out of the popup.
2. JET-77685: oj-input-search with suggestionItemTemplate does not automatically focus on the first row of dropdown results, hindering keyboard accessibility.
3. JET-77411: While using data-oj-manage-tabs with 'oj-combobox-many' as list items inside oj-c-list-view, pressing Tab should move focus to the next focusable component outside the oj-c-list-view instead of getting back to oj-combobox-many.

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 mobile.
2. JET-78095: Programmatic focus on Switch component lacks visible focus ring indicator, making it unclear where focus is for users.
3. JET-77149: Focus is lost from toolbar when pressing Enter the progress button (oj-c-progress-button), preventing further arrow key navigation within the toolbar.
4. JET-77142: In the Safari browser, oj-c-buttonset single/multiple lacks a visible focus ring when navigating between buttons with arrow keys after the initial click.
5. JET-77041: In Safari, the oj-c-date-picker focus ring disappears when navigating with arrow keys after clicking restricted dates.
6. JET-76819: On mobile with screen reader enabled, focus momentarily jumps to "is not supported" text before returning to Toggle End button when closing drawer (oj-drawer).
7. JET-75069: Focus fails to return to toolbar (oj-toolbar) item with tabindex=-1 after drawer closes, preventing proper keyboard navigation.
8. JET-76743: Focus indicator not prominent for primary action (oj-c-button) while being used in the drawer template.
9. JET-77433: oj-c-buttonset-single focus position is misaligned when navigated with screen readers, causing the focus indicator to appear in the middle of buttons.
10. JET-70464: Keyboard navigation should require only one tab to reach oj-button/oj-c-button while using it with a screen reader.

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.

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.

Exceptions:

1. JET-76796: Focus moves away from the Chart component to the body after progressive loading completes, requiring manual refocus.

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.

The product and documentation were tested for:

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

Exceptions:

1. JET-75575: While navigating through menu button (oj-c-menu-button) options for the second time, the screen reader incorrectly suggests using left/right arrow keys for navigation instead of up/down.
2. JET-76844: The screen reader wrongly announces "double tap to expand" for expandable tree view icons in the Tree view (oj-tree-view), as double tap fails to expand/collapse.

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-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.
2. JET-75163: Table (oj-table) should have a role='grid' instead of role='application,' which could help assistive technologies to recognize it as a table.
3. JET-77045: The screen reader announces the oj-c-select-multiple field as blank even when values are selected, unlike the expected behavior of reading selected values.
4. JET-73409: oj-select-single dropdowns lack the aria-activedescendant attribute for screen reader navigation, which could potentially result in restricted visibility to navigate and understand the page.
5. JET-75122: While navigating the menu options of the Menu button (oj-c-menu-button) by swiping in mobile with a screen reader, the screen reader focuses and it reads non-interactable options that are behind the popup.
6. JET-76197: The screen reader is initially reading a selected field blank even though the value is populated in the oj-select-single dropdown.
7. JET-78280: While swiping to move focusable elements in the menu button (oj-c-menu-button), the screen reader on mobile wrongly reads empty space as 'Close Button.'
8. JET-77055: Long press on a truncated labelled link in Safari on mobile does not show a tooltip and removes the truncation instead.
9. 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 actually not checked.
10. JET-77275: aria-labelledby value is not getting passed to the header slot, when the title is placed inside the body slot of the oj-c-dialog.

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 screen reader should not read the empty state as loaded in the oj-c-list-view.

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-54189: A user is unable to select date, hours, or AM/PM from oj-input-date-time while using it with a screen reader.
3. JET-74245: The screen reader virtual cursor fails to update when loading rows are replaced with loaded data in the Table (oj-c-table), leaving focus on the outdated loading area.
4. JET-76558: oj-popup fails to trigger onBeforeClose event when closed via a hidden screen reader link in mobile, unlike when using a mouse or when the screen reader is not enabled.
5. JET-78234: Screen reader users on mobile cannot find or use the hidden close link in the oj-c-input-date popup to dismiss it, unlike legacy oj-input-date.

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: http://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