Oracle Accessibility Conformance Report

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 summaries where appropriate
• Data tables specify ARIA-LABEL or SUMMARY
• 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 30375933: Popup LOV item - When displaying multiple columns in the search results, although the results are announced as a data table, the table is missing an accessible label.
• Bug 34308481: Popup LOV item - When 'Multiple Values' are on, it can be difficult to discern the item's label and value with a screen reader.
• Bug 35177965: Faceted Search region - The number of results for each facet value is difficult to understand for screen reader users.
• Bug 34427572: Items can comprise of multiple distinct elements (for example the help button, inline help and 'Quick Pick' links). All elements associated with an item should be semantically grouped, however they are not.
• Bug 31205979 and 35319783: LABEL elements for page items are always rendered, irrespective of which item type is used. This is fine for page items that use form elements such as text fields, select lists or textareas, however this is incorrect use of HTML for other item types (for example radio groups, checkboxes).
• Bug 35650682: Interactive Report region - When in Single Row View, column names and values are not correctly marked up as readonly fields, and are therefore difficult to understand with a screen reader.
• Bug 36249243: Card region - A card can contain multiple elements, however these are not semantically grouped.
• Bug 36343206: Date Picker item has a visible label, however this is not programmatically associated with the item.
• Bug 36964786: Smart Filters -The issue involves the disappearance of the filter button after applying two filters on an Application Wizard. This problem is intensified for visually impaired users as screen readers users hear all filters as one string, making comprehension difficult.
• Bug 37356204: Date Picker - The button to open a date picker's calendar is labelled with 'Select Date', however this is missing the accessible description referencing the item's label. If a page contains multiple date pickers, then this could make it difficult for screen reader users to easily discern which button is associated with which date picker.
• Bug 37287912: Interactive Grid - The grid contains two invalid child elements according to WAI-ARIA.

The product was tested for:

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

Exceptions:

• Bug 34668049: Interactive Grid region - After selecting 'Add Row', item types that do not fit in the cell (eg Textareas, Radio Groups) are rendered in the DOM at the end of the page, but visually positioned in the relevant grid cell, which can be confusing for screen reader users.

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

Exceptions:

• Bug 32463607: Map region - Polygon layers allow the user to visualize information with the fill color for the polygons on the map, providing a 'thematic map'. Polygons can be filled with different colors, but there is no ability to have patterned fill, if color is not sufficient. As a workaround, the 'Extruded Polygons' can be used instead of simple polygons. The map will become a 3D map, and the attribute is being visualized by the height of the extruded polygon - so color is not the only method to convey the information.
• Bug 34099929: Chart region - No declarative way of defining a chart series pattern. As a workaround, it is possible to do this through customization, please see our Sample Chart > Pattern page for more information.
• Bug 34184229: Interactive Grid and Report regions provide the ability for an end user to define a highlight. This highlight can be either a row, or cell highlight. The user defines a background and a foreground color for the highlight, and some kind of data condition that controls when the highlight displays. Although we guide people into making good color combination choices by showing the luminosity ratio of the highlight text and background colors, the highlight itself is conveyed to the user by color alone.
• Bug 36398841: Workflow Diagram region - The diagram conveys state information through color alone.

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

Exceptions:

• Bug 34099910: Chart region - When a chart shows the label value next to the chart data, this can sometimes cause color contrast issues, where for example the text overlaps part of the chart data section, and the text color with the chart data color does not meet contrast requirements. To workaround this, depending on the chart type and data, it may be possible to adjust the label settings, for example if 'Position' is set to 'Outside Bar Edge' (instead of the default 'Automatic'). In addition, if the chart displays a Tooltip including the value, this can be an alternative.

The product was tested for:

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

Exceptions:

• Bug 36398841: Workflow Diagram region - The 'terminated' state highlight colour and its background have insufficient contrast.
• Bug 37091317: Jet Chart region - The standard colors for charts in the Universal Theme app fail to meet the required 3:1 non-text contrast. Here are few examples: 
  • Green on white - contrast ratio is 2.7:1
  • Blue on white - contrast ratio is 2.954:1
  • Yellow on white - contrast ratio is 1.5:1
    As a workaround, custom colors can be defined.

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

• Bug 31888900: Tooltips used throughout the product fail the 'hoverable' test, because the tooltip disappears if you move the mouse over it.

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:

• Bug 32463573: Map region - Spatial objects drawn on the map are currently not accessible with the keyboard. It is possible to hover over these with the mouse and get more information about them, however this is not possible with the keyboard. The only workaround currently available to developers is to create alternative content on the page that conveys the same information, that is keyboard accessible (for example a report).
• Bug 34455843: Application Search region - When focused on the pagination controls, if the user presses Shift+Tab, this can sometimes trigger pagination.
• Bug 28293186: Although icon buttons used in our development environment and in Applications have an accessible name (using ARIA-LABEL), they also have a TITLE attribute which displays to mouse users on hover, however keyboard users have no way of perceiving this text.
• Bug 31971687: Region Display Selector region - This region renders tabs based on the regions on a page. The keyboard interaction is not properly initialized immediately after page load, resulting in every tab being a tab stop for keyboard users. As soon as the user selects a tab using cursor keys, the correct keyboard interaction is added and the tabs function as a single tab stop, as expected.
• Bug 33309025: Modal pages that submit and reload the modal page can lose focus.
• Bug 33824433: Markdown Editor region - Region does not keep text selection when navigating to the toolbar by keyboard (for example to bold selected text).
• Bug 34200659: Interactive Grid region - If a Dynamic Action is defined on a column that sets the value of another column, when keyboard users interact with the column, they can be taken to the next row unexpectedly.

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

Exceptions:

• Bug 32109673: Classic Report region - Region needs to better identify its contents with landmarks.
• Bug 34041752: Regions would benefit from landmarks to identify where items in the region are, and where any sub-regions in the region are.
• Bug 34960903: Regions defined to use landmarks will be missing their landmark information if the region also participates as a region controlled by a Region Display Selector on a page.
• Bug 35079324: Page items can be co-located in a region with the region's other contents (for example a table of data). In this case, it can be difficult for screen reader users to quickly find the items, because there is no landmark around them.
• Bug 35079782: Region templates define custom 'Positions', within which different page components can position themselves. These positions are missing landmarks, making it potentially difficult for screen reader users to quickly locate these components.
• Bug 36964683: Smart Filters - The suggested filters page section would benefit from having a containing landmark.
• Bug 36964453: Smart Filters - The applied filters page section would benefit from having a containing landmark.
• Bug 36964291: Smart Filters - All search related elements would benefit from having a containing landmark.
• Bug 36857238: Interactive Grid - The grid footer sits inside the main grid element, which could be confusing for screen reader users.

The product was tested for:

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

Exceptions:

• Bug 34017628: Interactive Grid region - Focus issues when window loses focus while editing. If the user is editing a field with a popup (eg Popup LOV, Color Picker), if they navigate away from the page to another window, then switch back, focus is taken to a hidden element on the page and the page may also be scrolled down to near the end.
• Bug 34071241: Item help can be displayed using Alt+F1, however this sometimes fails to load correctly with a screen reader. When this happens, screen reader users can workaround this by navigating to the end of the page, where the help dialog will be located.
• Bug 36941560: Interactive grid - The 'Edit' button can create confusion for screen reader users. When pressed, focus moves to a grid cell. If the grid cell contains interactive content (for example the 'Select Row' checkbox), this can be difficult to navigate to for a screen reader user.

The product was tested for:

• Headers describe the topic or purpose of the content below them
• Labels describe the purpose of the associated field

Exceptions:

• Bug 34492904: Date Picker item - Duplicate label when Display As attribute set to Inline.
• Bug 32867611: Faceted Search region - The facet chart button should not be part of the facet heading.
• Bug 33859790: Faceted Search region - Facet's expand / collapse button has a duplicate label.
• Bug 35215504: Interactive Grid region - If the region title contains some HTML, this HTML will be exposed in the table's accessible name.
• Bug 35132319: When a page item uses help text, the label used for the help button is too long ('View help text for [item label]'). This forces a screen reader user to listen to 'View help text for' before the item label for every help button. To workaround this issue, define the Text Message 'APEX.ITEM.HELP_TEXT' with text 'Help for %0', to shorten the accessible name used for help buttons.
• Bug 36249681: Card region - The main card link and heading are announced with the same label, which results in unnecessary duplication when using a screen reader.
• Bug 37356737: When links are within heading tags, adding aria-roledescription of 'action link' or 'dialog link' to these links results in the header disappearing. This causes confusion for users relying on screen readers as it disrupts the identification and navigation of headings.

The product was tested for:

• Visual indication of the location of the focus

Exceptions:

• Bug 25153460: Interactive Grid region - Some interactive controls do not show focus.

The product was tested for:

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

Exceptions:

• Bug 36795685: Item help dialogs sometimes block focusable elements. When a help dialog opens, focus moves to the dialog and it is possible (depending on the current viewport) that the dialog obscures other focusable elements. If the user then leaves the dialog but keeping it open (for example by using Alt+F6), then presses the Tab key, they may be in a situation where the dialog now obscures the element in focus. The user has no way of revealing the focused element without first focusing back to the item help (Alt+F1 again), and hitting ESC.

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

• Bug 36920761: Combobox/Select Many - Items with value chips fail the 24px target size requirement due to their default height of 16px. They also don't meet the spacing exception because clicking above or below the chip activates the input.
• Bug 36921663: Calendar - The default height of events in the calendar does not meet the 24px minimum target size. Single-day events are 16px tall, and multi-day events are 20px, both falling short of the required 24px. 

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

Exceptions:

• Bug 20697217: Errors displayed in Interactive Report dialogs (for example when attempting to save a Filter with an empty 'Expression' value) just display a red border around the field in error, with no text explaining what the error is.

The product was tested for:

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

Exceptions:

• Bug 34896075: Interactive Grid region - Advanced JavaScript configuration allows to display a sequence number as the first column in the grid. These sequence numbers are not perceivable to screen readers.

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’ or 'invalid'
• 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

Exceptions:

• Bug 34891616: Popup LOV item - When 'Manual Entry' is off, currently a readonly input element is rendered, however this gives the impression the field's value cannot be changed (which it can via the Popup).
• Bug 32085649: If a page item is a required field, developers can define this both using the 'Value Required' attribute on the item, and by defining one of the required label templates. If the 'Value Required' attribute is set, the rendered interactive element correctly uses the ARIA-REQUIRED attribute. However, if just the required label template is chosen, the interactive element is missing the ARIA-REQUIRED attribute, so users would not know the field is required at time of input.
• Bug 31964989: Interactive Grid region - Row state information such as deleted, inserted or changed is conveyed visually, however this state information is not conveyed to screen reader users.
• Bug 30375933: Popup LOV item - Search results visually highlight the searched text, however this causes screen readers to no longer read the searched word naturally, and instead the characters will be separated by the searched text and non-searched text.
• Bug 30375933: Popup LOV item - When displaying multiple columns in the search results, extra 'No results found' text will be incorrectly announced to screen readers.
• Bug 32138852: Where menus are used for page navigation, the menu item corresponding to the current page is missing the ARIA-CURRENT property.
• Bug 33882274: With Modal Dialog pages, if the page setting 'Focus on first item' is used, a screen reader user will have difficulty in reaching the dialog 'Close' button and the modal dialog title.
• Bug 33844482: Faceted Search region - Region uses a listbox implementation for the radio and checkbox style facets. This listbox implementation has some nesting and incorrect WAI-ARIA attribute issues.
• Bugs 33571036 and 35021433: The following places have interactive elements that open dialog content, but where the ARIA-HASPOPUP attribute is missing:
  • Create application page contains links that open modal dialog regions.
  • 'Cards' regions that expose action buttons that open modal dialog pages.
  • Page buttons that redirect to modal dialog pages.
  • Page buttons that open inline dialog regions.
  • Report links that open modal pages.
  • Main menu option 'SQL Developer Web' (available from the SQL Workshop menu, when there is an available SQL Developer Web environment).
• Bugs 34585616: Display Only item - Renders a SPAN element visually displaying the value of the item. Because this is not an HTML form element, this information could be missed by users of Assistive Technology.
• Bug 31200377: Text field using a Subtype other than the default 'Text', in read-only mode - Renders a SPAN element visually displaying the value of the item. Because this is not an HTML form element, this information could be missed by users of Assistive Technology.
• Bug 34305870: Rich Text Editor in read-only mode - This information could be missed by users of Assistive Technology.
• Bugs 34836092 and 34836385: Checkbox and Checkbox Group in read-only mode: Uses DISABLED attribute but should use READONLY attribute 
• Bug 34489941: Popup LOV item - Renders its popup list of values in a dialog, however this dialog is not modal when used with a screen reader.
• Bug 34456004: Dialogs rendered by apex.message.showDialog (and used for example in the Date Picker item type to render the calendar popup) do not follow the WAI-ARIA Dialog design pattern.
• Bug 34258753: Popup LOV item - Item implements the WAI-ARIA Combobox design pattern, however it is missing defining ARIA-CONTROLS on the combobox element pointing to the popup container element.
• Bug 34184254: Interactive Grid and Report regions - Both provide the ability for an end user to define a highlight. This highlight can be either a row, or cell highlight. The user defines a background and a foreground color for the highlight, and a data condition that controls when the highlight displays. Screen reader users have no easy way of knowing which cells / rows are currently highlighted.
• Bug 34910599: Interactive Grid region - If a Control Break is defined, in the grid the control break header is difficult to understand, and collapsed state is not conveyed to screen reader users.
• Bug 34970326: Interactive Grid region - Row states 'Inserted', 'Updated', 'Deleted' and 'Error' are not perceivable are not conveyed to screen reader users.
• Bug 35112161: Modal dialog pages currently render an IFRAME inside the modal dialog element, however this should be with the IFRAME outside of the modal dialog element.
• Bug 35135038: Faceted search region - Facets are presented as a group of sections that can be expanded or collapsed, however they are not coded to the WAI-ARIA Accordion design pattern, making them difficult to use with a screen reader.
• Bug 35474289: Combobox select interface (used by Smart Filters region, Text with Autocomplete item and Combobox item) - Element used to convey dynamic information to screen readers is also perceivable as an element, so creates unecessary UI for a screen reader user to navigate.
• Bug 35474276: Combobox select interface (used by Smart Filters region, Text with Autocomplete item and Combobox item) - Some operations cause screen readers to duplicate their current context.
• Bug 35338019: Popup LOV item - When Manual Entry is off, the Popup LOV renders a non-editable field, with a button to open a popup, where a value can be searched and selected. The non-editable field is defined as read-only, which could give screen reader users the false impression the field cannot be updated (it can be edited, just not manually and only via selecting from the list in the popup.
• Bug 36036649: Jet Chart region - If a Chart Title is defined, the title gets duplicated in the accessible name for the chart's container element with role of 'application'. 
• Bug 36113722: Application Logo - The application logo markup includes a link that takes the user to the home page of an application. This should contain aria-current="page" when the current page is the home page.
• Bug 36473524: Interactive Grid region - Selection mode is not easily perceivable by screen reader users.
• Bug 37044386: Popup LOV item -  The selected items shown as chips in the field container, aren't announced by screen readers as expected. Instead, screen reader users must navigate to these chips to determine the selected values.
• Bug 36964724: Smart Filters - When a filter has been applied, a delete icon button is visible, however this button is not perceivable to a screen reader user. To workaround this issue, screen reader users may be able to leverage the native keyboard behaviour of being able to move between applied filters with arrow keys, then pressing either Delete or Backspace to remove the active filter.
• Bug 37126437: Quick Picks - screen reader users aren't notified of changes made by quick pick links, wrongly implying the links don't work.
• Bug 37288044: Interactive Grid - aria-sort is used to indicate the current primary sorted column, however this is placed on an element inside the table header cell, rather than on the table header itself.
• Bug 37356338: Quick Picks - Adding aria-roledescription of 'action link' or 'dialog link' to links that already contain an aria-roledescription, results in the original value being overwritten. This could be confusing for users.

The product was tested for:

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

Exceptions:

• Bug 34455843: In the Application Search region, screen reader users are not notified when using pagination controls.
• Bug 29348302: When logging into a workspace, or an Application using an appropriate authentication scheme, if the instance is set to have a delay for failed login attempts (setting in Instance Admin > Security > General Settings > Delay after failed login attempts in Seconds), and the user enters incorrect login details, a notification displays that includes a count down of the number of seconds before they can attempt logging in again. This countdown is not announced properly to screen reader users.
• Bug 30380762: The Faceted Search region component requires better notifications of partial page updates for screen reader users.

The product was tested for:

• PDF files conform to PDF/UA-1
• Components that support export to PDF respect either the APEX_PDF_ACCESSIBLE user preference, or the 'Include Accessibility Tags' option (where supported)

Exceptions:

• Bug 31961351: Classic Report region - Regions do not provide a direct way to allow an end user to select accessible PDF, although it is possible to export accessible PDFs from classic reports if the relevant user preference has been set. There are four ways in which this user preference can be set, outlined below:
  • Interactive Report dialogs include an 'Include Accessibility Tags' option, which when checked will be saved as a preference for the current user.
  • Interactive Grid dialogs include an 'Include Accessibility Tags' option, which when checked will be saved as a preference for the current user.
  • The preference can be directly set by a developer, for example: APEX_UTIL.SET_PREFERENCE( 'APEX_PDF_ACCESSIBLE', 'Y', );
  • The API APEX_REGION.EXPORT_DATA is available, which allows for any component with a data source (which includes Classic Reports), to export supported PDF (where the parameter p_pdf_accessible is set to true). Once this API has been called with p_pdf_accessible set to true, the APEX_PDF_ACCESSIBLE preference will be set for the current user.

The documentation includes a Developer Guide that includes information about the components available in APEX. Please visit the Oracle APEX documentation homepage and then 'Develop Apps'.

Product documentation is in electronic format.