Oracle Accessibility Conformance Report

• Images that convey information have meaningful alternative text using ALT
• Images that are decorative are marked up using ALT=”” or CSS background images
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
• Controls have an associated name

• No Pre-recorded audio-only or video-only content is being used

• No Pre-recorded video content is being used

• No pre-recorded video is being used

• No live audio content in video is being used

• No pre-recorded video is being used

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

Affecting the Application Express Development Environment:

• The 'Quick Edit' and 'Live Template Options' features, available as a developer of an application via the developer toolbar, are inaccessible to screen readers user. You can use quick edit with keyboard-alone, where the cursor keys allow you to navigate through the runtime page and select the page component you wish to edit, however these components do not have any accessible label, meaning screen readers will not be able to identify them. Because Live Template Options is available via the Quick Edit feature, then this also means this is not accessible to screen reader users. Screen readers users will need to navigate to components to edit via the App Builder in the traditional way, so without the convenience of being able to go straight to a component to edit from the runtime. Also Template Options will need to be edited in the App Builder and saved, and then the page refreshed to see the effect of the change in the runtime, so without the convenience of the Live Template Option feature. This issue is tracked with Oracle bug 25153940.

  Affecting Development Environment, Websheet Applications and Database Applications:

• Classic and Interactive report regions of Application Express currently have no declarative way of defining row headers. This issue is tracked with Oracle bug 14198644.
• The modern inline date pickers are not usable with screen readers or magnification due to focus not being set correctly. The data table is also missing a caption or summary text to describe the data in the table. Users can however enter the date manually into the date input field. This issue is tracked with Oracle bug 9740473.

Affecting Documentation:

• The left page navigation section visible on some pages of documentation, is not marked up in a way that would make it easily identifiable with assistive technologies. This issue is tracked with Oracle bug 25168796.

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

Exceptions:

Affecting the Documentation:

• There are some inconsistencies on several pages between tab and visual order, where tabbing through the elements on the page does not follow the expected visual order. These issues are tracked with Oracle bugs 25168757, 25168784.

• Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound

• Information conveyed by color is available in alternative formats, such as shape, text, font weight

• No automatically playing audio is used

• 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

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

• Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential

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

Affecting Documentation:

• The 'Welcome' and 'Choose Language' menus in the header and footer bars respectively cannot be reached with keyboard, as they rely on mouse hover functionality to open the menus. This issue is tracked with Oracle bug 25168767.

• Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control

• Time limits in the product can be turned off before they are encountered

Affecting Development Environment and Websheet Applications:

• The Maximum Session Length and Maximum Session Idle Time time-outs, which are configured by the Application Express instance administrator, cannot be extended by an end-user. This issue is tracked with Oracle bug 14616880.

• There is no moving, blinking or scrolling content

• 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

Exceptions:

Affecting Development Environment, Websheet Applications and Database Applications:

• There are no 'Skip to Main Content' links implemented in APEX. This issue is tracked with Oracle bug 27782291.

• Pages have a meaningful title specified in the TITLE element

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

• 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 can be found using the provided "search" function
• Page contains controls that enable reaching all pages

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

Exceptions:

Affecting Development Environment:

• In Page Designer (where developers build and edit pages in APEX), the current heading structure needs improving to improve usability for users of Assistive Technology. This issue is tracked with Oracle bug 27782249.

• Visual indication of the location of the focus

• Properly set lang attribute for each page

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

• 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

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

• When input errors are detected, they are described to the user in text, including identifying the item where the error occurred

Exceptions:

Affecting Development Environment, Websheet Applications and Database Applications:

• 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. This issue is tracked with Oracle bug 20697217.

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

• Where suggestions for fixing an input error are known, they are provided to the user

• Data is checked for input errors with an opportunity for the user to correct them
• When using the component creation wizards, the component data can be reviewed, corrected, and confirmed by the user before it is finalized

• Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs

Exceptions:

Affecting Database Applications:

• If more than one Interactive Report Region are defined on one page, where more than one of those define a 'Link' column, then the 'Link' column heading rendered will contain duplicate ID values of 'LINK'. This issue is tracked with Oracle bug 20687795.

• 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 programatically exposed name
• Frames have a meaningful title specified in the title attribute

Exceptions:

Affecting Development Environment:

• The Code Editor item type, which is used in many places to enter SQL, PL/SQL and JavaScript code includes an auto-complete feature, providing suggestions specific to the code type. For example, in SQL and PL/SQL auto-complete provides suggestions of database objects, or page item names defined in the application that may need to be referenced from the code. The auto-complete functionality is not conveyed to assistive technologies. This issue is tracked with Oracle bug 20696803.

Affecting Documentation:

• The left page navigation section visible on some pages of documentation contains a 'Table of Contents' sub-section, which should be coded to the WAI-ARIA 'Tree' guidelines. This issue is tracked with Oracle bug 25168801.

See the responses in the WCAG 2.0 section of this report.

The product contains no instance of either converting content from one format to another, or saving content in multiple formats.

Classic Report and Interactive Report native region types in APEX have the capability to export their data in PDF format. The PDF is not accessible, but the HTML used to render the report on the page is accessible.

We mandate certain accessibility related attributes when building APEX applications (for example page titles, region titles, and button labels). The developer is responsible for ensuring the text provided is appropriate and meaningful.

APEX includes a built-in tool called the Advisor, which can be run by developers as part of quality assurance of an APEX application. To help with other non-mandatory attributes defined by a developer, the Advisor includes a set of accessibility checks to highlight possible common accessibility problems (for example page items with no labels, or page regions with no row headers defined). The developer should review and fix such problems as part of their ongoing development process. We recommend to fix issues identified by the Advisor before doing other accessibility testing, for example testing with Assistive Technologies.

Developers should use the default 'Universal Theme' when building applications in APEX. This theme contains templates for different component types, which have been accessibility tested. In addition, developers can select different 'Theme Styles' for styling their applications in different ways. Theme Styles are labelled as being 'Accessibility Tested' if they have undergone accessibility testing. The default 'Vita' is accessibility tested.

In our documentation, we have an Accessibility Guide, dedicated to helping you both use APEX, and build APEX apps that meet accessibility guidelines. Please visit the APEX documentation homepage and then select 'Accessibility Guide'.

In addition, we list accessibility specific bugs (with workarounds where possible), in our product Release Notes.

Documentation is provided in electronic formats.