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=””, CSS background images, or font icons
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
• Objects and Applets are not used
• Controls have an associated name
• Time-based media are not used
• Client-side image maps are not used
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used
• Functionality is discoverable by screen reader users

Exceptions:

• Data Grid: Column Menus: Incorrect Screen Rdr Instructions for Column Sorting (bug 21122956)
  When column sorting is enabled, but column menu is not enabled, the text read by a screen reader says that the Space bar opens the column menu, which is incorrect. It actually sorts the column.

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 or ARIA roles are 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:

• Data Grid: Clmn Groups,Cntxt Menu/Cog,Slctor Clmn: Table Structure Not Accurate (bug 19990454)
  When using the Data Grid with the optional features Column Groups, Context Menu (Cog Wheel), and/or Selector Column, navigating the Data Grid in JAWS virtual cursor mode does not work correctly.  Navigating in JAWS Forms mode does work correctly, so recommend using JAWS in Forms mode
   
• Data Grid: Context Menu: Info and Relationships: Various Issues (bug 21115549)
  (1) When the context menu is opened with the Windows keyboard Menu key (as opposed to activating the gear icon button), a screen reader will speak "row menu", but provide no further information or instructions.  The context menu does work correctly.  A workaround is to use the gear icon buttons. (2) There is no indication by a screen reader that the row menu (gear icon) column is available.  The gear icon column does work correctly.  A workaround is to navigate to the gear icon column from the first data column using the Shift+Tab or Left Arrow keys.
  (3) When navigating to a submenu item, a screen reader provides more information than is necessary at that point.  A workaround is to interrupt speech.
   
• Data Grid: Client Sorting: Info And Relationships: Various Issues (bug 21116287)
  When a column heading cell gets focus from a data row cell, a screen reader says, "...Press Space to sort by column," which is true.  However, the screen reader does not explain that Control+Space can be used to specify a secondary sort.
   
• Data Grid: Column Types: Cost/%: No Immediate Screen Reader Notification of Invalid Value (bug 22394619)
  When using a screen reader, if the user enters an invalid value in a Cost or Percent column cell, there is no immediate notification to the the user that the cell value is invalid.
  A workaround is to navigate back to the cell, in which case a notification is given.
   
• Data Grid: Grouped Rows: Grouped Row Header Should Be role="rowheader" (bug 23238692)
  Currently, grouped row headers, which span the entire grid, have role="gridcell". They should have role="rowheader".  This means that AT may not recognize the grouped row headers as row headers.  The text of the grouped row headers is still available to AT, so a workaround is to read the text of the grouped row header.

The product was tested for:

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

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

• Data Grid: High Contrast: Firefox: Can't always identify selected cells (bug 21099795)
  In Firefox, in high contrast themes, when more than one row is selected, or the focused row is not within the selected rows, there is not always a visual indicator as to which cell or cells are selected.
  Since all selected cells are in the same column, and since all cells of the selected rows in that column are selected, and since one of the cells in the column has a visual indicator, the user can assume that all cells in selected rows in the column with the visually selected cell are selected.
   
• Data Grid: Column Groups: High Contrast: column group top border lines missing (bug 24935653)
  When columns are grouped, a separate border line is drawn around each group of columns to identify the group.  In high contrast themes, the top border is not visible.
  A workaround is to use the left and right borders of the column groups to identify each group of columns.
   
• Data Grid: Focused data cell difficult to identify (bug 28722141)
  The focused data cell in the data grid is identified by a different background color, as well as a thicker border.  In a normal theme, it is not easy to visually distinguish a focused data cell from an unfocused data cell in the same row.
  If the user finds it too hard to distinguish between focused and unfocused data cells, a workaround is to use a high-contrast theme.  In a high-contrast theme, the thicker borders of the focused data cell are clearly visible.
   
• Data Grid: Text Input and Selection: Select column: High Contrast: down arrow icon not displayed properly (bug 28749373)
  In a high-contrast theme, in a select column in the data grid, the down-arrow (v) icon that normally acts as visual indicator of a select dropdown menu appears as a rectangle.
  The user can assume that, in a high-contrast theme, a rectangle on the right side of the cell indicates a select dropdown menu.
   
• Shuttle:  In high contrast theme, can't tell which nodes in list are selected (bug 28985094)
  When a high contrast theme is used, the user can't tell which nodes in either list are selected.
  The user should review any actions taken on the selected nodes to ensure that the correct nodes were acted upon.

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

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

Exceptions:

• Data Grid: Page Scrolls To Top On Context Menu Action (bug 24744248)
  When an action is selected in the context menu, the action occurs correctly, but the UI page is scrolled to the top automatically.
  A workaround is to scroll the page back to where it was.

Images of text are not used.

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)

Exceptions:

• Search: Advanced Link Not Keyboard Operable in Firefox and Internet Explorer (bug 20924266)
  The Advanced link in the Search pattern does not work properly when activated from the keyboard.
  An alternative for developers is to configure the Search pattern with the Advanced dropdown instead
   
• Data Grid: Client Sorting: Sticky Keys: Secondary Sort Doesn't Work (bug 21274792)
  When a grid column is enabled for sorting, the standard behavior of Control+Space in the column header is to set a secondary sort on that column. This does not work with StickyKeys; it defines a primary sort.
   
• Dashboard: Cut Tile Has No Visual Cue (bug 23064751)
  When the user uses the Cut-Paste context menu to move/reorder a tile, the tile being cut/moved is not highlighted in any way to indicate that it has been select for cut/move.
  Upon pasting the tile, the user should confirm that the correct tile has been cut and pasted.
   
• Page Template: Infotiles: Focus lost after tile selection (bug 24766296)
  Selecting an infotile causes the infotile to lose focus.
  A workaround is to navigate back to the tile using the Tab key.
   
• Data Grid: Selector Column: Can't Use (De-)Select All Checkbox With Keyboard (bug 24797793)
  The Select/Deselect All check box at the top of the Selector column doesn't work with the keyboard (Space key).  The check box itself becomes checked or unchecked, but it has no effect on the individual selector column check boxes in the data rows.
  A workaround is to select and deselect the selector column check boxes individually.
   
• Data Grid: link column: wrong keystroke to activate link (bug 28722241)
  A data grid configured with both a row selector column and one or link columns cannot be fully operated from the keyboard.
  An alternative for developers is to not configure these two features together in the same data grid instance.
   
• Data Grid: Check box column sort doesn't work (bug 28951873)
  When column sorting is configured for a check box column, the data grid does not function correctly.
  If sorting is not actually required for the check box column, an alternative for developers is to not configure sorting for the check box column.
  If sorting is required, an alternative for developers is to configure a different column type for a boolean selection, such as a select column with Yes and No choices.
   
• Data Grid: Can't always read entire value in text column with keyboard only (bug 28958349)
  When the length of a read-only text value in a text column cell exceeds the column width, the keyboard-only user is unable to read the entire text value.
  A workaround is to copy the cell value, paste the value into another window or text input field, and read the text value there.
  An alternative for developers is to configure the column width to be wide enough to display all valid text values for the column.
   
• Shuttle:  Selecting an item twice in a row doesn't work (bug 29012500)
  If a list item is selected, then deselected, then immediately reselected, the item cannot be moved or removed.
  A workaround is to select another item in the list, then go back and select the desired item.
   
• Data Grid: Filtering: Left Arrow from first data cell to filter field -> filter value also appears in first data cell (bug 29038015)
  If the user navigates from the first data cell to the last column filter field using the Left Arrow key, then types a value into the column filter field, the value will be entered in both the column filter field and the first data cell.
  A workaround is to use Shift+Tab rather than the Left Arrow key to navigate to the column filter field.

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

Exceptions:

• Dashboard: Keyboard Navigation Issue With List View In Tile In Add Tile Dialog (bug 22910840)
  If the content of a Dashboard tile includes a certain component (Oracle JET List View), and the tile is listed in the Dashboard Add Tile dialog, the keyboard navigation of the tiles listed in the dialog does not work, and in certain cases, can become a keyboard trap.
  One alternative for developers is not to use the Oracle JET List View in Dashboard tile content.  Another alternative for developers is not to allow Dashboard tiles whose content includes an Oracle JET List View to be removed from the Dashboard.

Time limits are not used.

There is no moving, blinking or scrolling content that is subject to this success criterion.

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

• 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

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

• The text of links and their surrounding paragraph, list, table cell (with marked up table headers), or preceding heading is sufficient to describe their purpose

• Pages are fully inter-linked to each other
• Pages are steps in a process

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

• Visual indication of the location of the focus

Exceptions:

• Nav Tree: High Contrast Theme: No Visible Focus When Focus is on Selected Item (bug 21098661)
  When focus is on the selected item in the Navigation Tree, there is no visible focus.
  A workaround is to navigate to another item in the Navigation Tree.  This will restore visible focus.
   
• Autocomplete: High-Contrast: Menu Items Have No Visible Focus (bug 23076167)
  The menu items in the Autocomplete suggestions menu do not have visible focus.
  A workaround is to look at the text in the search field, which mirrors the text of the currently focused suggestion menu item.

• Properly set lang attribute for each page

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

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

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

This product does not directly perform any of the operations listed.

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

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 programatically exposed name
• The product has no frames.

Exceptions:

• Data Grid: Find and Filter: Column Filter Row Has No Row Header (bug 24914932)
  The column filter row in the grid does not have a cell identified as the row header.
   
• Data Grid:  Chrome:  Value of text column or link column cell not read by screen reader (bug 28529031)
  In the Chrome browser, when focus is on a data cell in a link column, the screen reader does not read the cell value.
  A workaround is to use the Firefox browser.
   
• Dashboard: Tile cut/paste menu not clearly explained by screen reader (bug 28986259)
  When the screen user reader navigates to the location of the tile cut/paste menu, the screen reader does not correctly explain how to invoke the menu.
  A workaround is to press Shift+F10 to invoke the menu.

This product has no documentation that is provided to the customer.

This product has no non-electronic support documentation.

Support services are provided for the products that use this product, not for this product itself.

Support services are provided for the products that use this product, not for this product itself.