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-74295: The screen reader is repeating the pagination information.
2. JET-74245: While using a screen reader in a virtual cursor mode to read a table, it fails to announce the newly inserted row between that loading row and the previous rows while 'loading'.
3. JET-73860: Label hint is not getting read by the screen reader for the checkboxset (oj-c-checkboxSet).
4. JET-73485: The content of the input-text (label & value) is read twice with the screen reader while using oj-c-input-text with the length (max and count-by) property.
5. JET-73431: While using oj-c-menu-button with screen reader, when the user presses 'space' to open the menu, it reads out menu information in 3 different ways, all at once.
6. JET-73254: Whenever a user focuses on a new row in the data grid, along with the row and column details, the row number should not be read out by the screen reader just before the data present in the focused cell is read.
7. JET-73147: Moving through the items with arrow keys in the Color Palette, the screen reader does not read out the value, nor does it say what was selected when you press Enter or the spacebar.
8. JET-72957: While using oj-list-item-layout with screen reader, it is reading the label and remove button multiple times.
9. JET-72065: aria-label should not be put on buttons (oj-c-button) if a visible text is rendered, as the screen reader will read it twice.
10. JET-71077: The expanded submenu in the mobile with a screen reader is read incorrectly as a collapsed submenu
11. JET-76111: The screen reader is not able to announce the value of the pie slice of the oj-chart while tabbing on the pie sections.
12. JET-75767: One of the column headers of the oj-table is read out twice by the screen readers because of the header tooltip.
13. JET-75329: While using the oj-c-buttonset-single, the screen reader focus goes to the button label (e.g., B), but it does not give any information about it; we need to swipe again, and then the focus is on the entire button.
14. JET-75307: The screen reader does not provide any instruction on how to exit from the LOVs for a Select Multiple (oj-c-select-multiple) input control.
15. JET-75119: The screen reader is not reading the complete data in the data grid by default.
16. JET-76150: While navigating to the Select multiple using a screen reader on mobile devices, it wrongly announces, 'Press Backspace or Delete to remove the selected value,' which is not a valid message for mobile devices.
17. JET-76170: When a user tries to use the Progress Button (oj-c-progress-button) with a screen reader, it announces the progress status too late, and it does not match the actual completed status, which could mislead visually impaired users.
18. JET-75108: While navigating to the Select Single (oj-select-single) with screen reader, the page title gets announced twice.

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-72458: While using oj-popup with browser zoom of 400%, when the element takes up the entire screen space, two instances of pop-up are seen on the screen when we open it. On the top and bottom of the popup button.
3. JET-76033: While using the List View (oj-list-view) with browser zoom of 400%, the user cannot reorder or drag/drop.
4. JET-75661: The default focused submenu option is not visible when the submenu opens, and we need to scroll to view it with browser zoom of 400%.
5. JET-71107: When the browser is zoomed at 400%, a user is unable to scroll through the data grid, and header texts are getting cut (in small view too).
6. JET-73448: Scrolling Menu Button (oj-menu-button) with browser zoom of 400%, causes flickering of menu.

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 corepack components.

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-73495: In a single-select input field with a dropdown, when a user types any character inside the input box and presses the "Enter" key, it should not automatically select the first item.
3. JET-60038: Tabbing a list item in a button set when in actionable mode should not leave the list item.

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-65082: When using oj-c-select-multiple inside an oj-drawer-popup, the options drawer is not working with a screen reader in mobile due to a lack of focus inside the drawer.
2. JET-69551: While using the pop-up with a screen reader on mobile , one has to navigate backwards to read popup content.
3. JET-62253: In Collection components for instance DataGrid where actionable mode is enabled, having a select-single as the only actionable child in a region causes content of the component to disappear when a user attempts a 'shift+tab' operation.
4. JET-76109: While using a screen reader on an iPad, focus does not move inside menu options after clicking on the Menu button.
5. JET-76205: Swiping forward in any of the chip in the popup (oj-c-popup) leads to focusing out of the popoup.
6. JET-76159: The Toolbar (oj-toolbar) gets focus even if it contains one disabled button.
7. JET-69222: The user is unable to enter the actionable mode using the programmatic focus in the oj-list-view.

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-72842: Buttons inside a dialog are not getting focused when used with a screen reader.
2. JET-76144: In Select Single (oj-c-select-single), the focus ring appears as a solid blue outline instead of the fine dashed line.
3. JET-76032: In Tree View (oj-tree-view), the focus is not visible after the cut and paste for grouping leaf reorder.
4. 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.

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.

Exceptions:

1. JET-76160: List View (oj-list-view) reordering is not working properly when a user tries using it with a screen reader enabled on a mobile device.

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.

• A particular presentation of the target is essential or is legally required for the information being conveyed.

Exceptions:

1. JET-70481: Target size failure (insufficient target size) is reported for the component InputDateMask, InputTimeMask in the compact mode.

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.

Exception:

1. JET-73370: Tabbing through waterfall (oj-waterfall) layout unexpectedly lands on a button inside a panel.

The product and documentation were tested for:

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

Exceptions:

1. JET-75575: The screen reader is suggesting the user use left and right arrow keys to navigate through the options instead of up and down arrow keys from the second instance of navigating through the options in the oj-c-menu-button component.

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.

Exception:

1. JET-73445: With the screen reader enabled, error messages are not being read out in the oj-drawer-popup.

The product and documentation were tested for:

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

Exception:

1. JET-72228: While using InputTimeMask and InputDateMask, the screen reader is announcing the deletion of the dates only for the first time.

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-72279: The expand/collapse icon does not have a label in the Row Expander table (oj-row-expander).
2. 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 they are not checked.
3. JET-72888: When navigating via keyboard on read-only values, the screen reader announces each value as 'selected' even if they are not selected.
4. 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.
5. 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.
6. JET-75163: Table should have a role='grid' instead of role='application' which could help Assistive Technologies to recognize it as a table.
7. JET-73268: In the Tab Bar Mixed (oj-c-tab-bar-mixed), the div containing aria-activedescendant should contain children.
8. JET-72559: The oj-list-view should not have role="grid" for an unordered-list and role="gridcell" for a division.
9. JET-71640: While using the oj-list-view component having display as 'card,' the HTML structure contains a UL tag with role="row".

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-76064: While using List View (oj-c-list-view) with the assistive technologies, it is not able to read the 'No items to display' message for empty lists.
2. JET-76172: Progress Button's (oj-c-progress-button) in-progress status is not getting read by the screen reader when used with a mobile.

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-75830: Unable to open the context menu with assitive technology ON. When the user triple taps to open the Context menu (which is the correct gesture for voiceover on mobile) on List view, it just selects the text.

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