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:

• A minority of page items display helper text after the item such as expected formats, which is not semantically tied to the page item and could therefore easily be missed by users of Assistive Technology. This issue is tracked with Oracle bug #20085481.
• Flot Pie Chart region types, used 5 times to show charting information contain a chart legend with incorrect table markup. This issue is tracked with Oracle bug 20669311.
• Flot Pie Chart region types, used 5 times to show charting information uses an inaccessible CANVAS element, which is completely ignored by Assistive Technologies. This issue is tracked with Oracle bug 20669311.

  Affecting Development Environment, Websheet Applications and Database Applications:

• All native report regions of Application Express currently have no declarative way of defining row headers. This issue is tracked with Oracle bug 14198644.

• 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

• 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 the Application Express Development Environment:

• Flot Pie Chart region types, used 5 times to show charting information contains tooltips which are inaccessible to keyboard users, resulting in keyboard users not being able to associate any section of the chart with the corresponding value. This issue is tracked with Oracle bug 20669311.

• 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

• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links

• 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

Exceptions:

Affecting the Application Express Development Environment:

• Across the development environment there are many report pages, with 'Edit' icons on each row of the report, to take the user to edit a particular component relevant to that page and row. In many places across these pages, this icon contains an image with either missing, or empty ALT text, which therefore means the wrapping anchor does not get correct link text. This issue is tracked with Oracle bug 16911835.

• 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 the Application Express Development Environment:

• 'Next' and 'Previous' style navigation buttons, used to allow navigation across related components in the development environment sometimes have button text of just '>' and '<'. This is insufficient in clearly describing the purpose of the button. This issue is tracked with Oracle bug 16322302.

• 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

Exceptions:

Affecting Development Environment, Websheet Applications and Database Applications:

• Item types that have an option to submit the page when the item's value changes (for example 'Select List' item type with the 'Page Action on Selection' attribute set to 'Submit Page') reload the page when the value is changed, and also cause focus to be reset to the start of the page. This issue is tracked with Oracle bug 20697122.

• 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

Exceptions:

Affecting the Application Express Development Environment:

• The 'Template Option' item type, used to display a particular template type's configurable options render a group of form controls, and the group is not labelled. This issue is tracked with Oracle bug 20388455.

• 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 Development Environment and Database Applications:

• The 'Text Field with autocomplete' native item type fails to convey the autocomplete list to assistive technologies. This issue is tracked with Oracle bug 18918806.

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

Information may not be preserved when converting formats.

Classic Report and Interactive Report native region types in Application Express 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.

There are currently no such prompts, or built-in tools to assist developers in creating accessible applications.

Developers should use the default theme 'Universal Theme' when building applications in Application Express. 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 currently provide information regarding our accessibility modes, and also other information for keyboard-only and screen reader users of Application Express. This documentation is available in the 'Accessibility in Oracle Application Express' appendix in the 'Application Builder User's Guide' book of the product documentation.

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

We do not currently provide a full developer guide for how to build accessible applications in Application Express.

Documentation is provided in electronic formats.