Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Application Express (APEX) (Updated) 18.x

Product Description:

Oracle APEX is a modern web-based development framework for building web applications, and a no-cost feature of the Oracle Database. The framework relies on modern web technologies and standards including HTML5, JavaScript, CSS and WAI-ARIA.

There are known issues with this product, which are listed in this document under one or more of the following categories where appropriate:

  • Development Environment - The development environment for APEX.
  • Database Applications - Standard, developer-built web applications using the full framework capability.
  • Websheet Applications - Targeted not just at developers, 'Websheets' allow non-technical users to also put content on the web, and provide a different interface to the more common 'Database' applications.
  • Documentation - The documentation for APEX.

Date:

20-Aug-2021

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

  • Interactive Grid Component - The Interactive Grid is a native region type that supports powerful reporting and multi-row editing capability. It is available to use in applications built with APEX, and also used in the Development Environment on a small number of pages. An alternative for the reporting capability is the Interactive Report region type. An alternative for the multi-row editing capability is the Tabular Form region type.
  • SQL Workshop Module - Module used to maintain database objects for your applications. An alternative would be to connect to your database schema via a different tool (such as SQL Developer), if direct access to the database is available.
  • Theme Roller - Module available to developers allowing declarative definition of look and feel.
  • Data Grids in the Websheet runtime - Sub-module of a Websheet application, where ad-hoc multi-row data can be maintained. There is currently no alternative.
  • External content (web pages served from non-APEX-Workspace domains).
  • PDF.
  • Oracle Help Center, Library Version.

Oracle APEX is capable of generating web applications that meet the standards, as long as the developer follows the guidelines and applies accessibility standards appropriately. To help achieve this, please see the product documentation described in section 602.2.

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/index.html

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018Yes

Terms

The terms used in the Conformance Level information are defined as follows:

Supports
The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Partially Supports
Some functionality of the product does not meet the criteria.
Does Not Support
Majority of functionality of the product does not meet the criteria.
Not Applicable
The criteria are not relevant to the product.

WCAG 2.1 Report

Table 1 also documents conformance with:

  • Section 508: Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria
Conformance Level
Remarks and Explanations
1.1.1 Non-text Content (Level A)Partially Supports

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

Exceptions:

Affecting Database Applications:

  • Applications defined to use a logo ot type 'Image', or 'Image and Text' render an image with no ALT tag. This issue is tracked with Oracle bug 32393990.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Supports The product was tested for:
  • No Pre-recorded audio-only or video-only content is being used
1.2.2 Captions (Prerecorded) (Level A)Supports The product was tested for:
  • No Pre-recorded video content is being used
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Supports The product was tested for:
  • No pre-recorded video is being used
1.2.4 Captions (Live) (Level AA)Supports The product was tested for:
  • No live audio content in video is being used
1.2.5 Audio Description (Prerecorded) (Level AA)Supports The product was tested for:
  • No pre-recorded video is being used
1.3.1 Info and Relationships (Level A)Partially Supports

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 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 Database Applications:

  • The 'Buttons Container' region template is used as an invisible container for buttons on a page. Regions using this template render a hidden (but accessible to screen readers) HTML heading, with the region title as the heading text. Buttons can then be positioned in certain template positions, however some of these positions (specifically where the button is positioned on the left of the region), result in these buttons appearing before the heading, which is confusing for screen reader users. This issue is tracked with Oracle bug 31972352.

Affecting 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.

  • In many places across the development environment, the BOLD tag is used to emphasize text. This should be replaced with the STRONG tag. This issue is tracked with Oracle bug 29347790.

  • Summary style pages, typically shown at the end of wizards in APEX contain summary information that is difficult to understand with a screen reader. This issue is tracked with Oracle bug 31566352.

  • Search results pages for the APEX Advisor, and for Application Search, are difficult to navigate with a screen reader. This issue is tracked with Oracle bug 31972162.

  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.
  • APEX provides two main ways in which page items can be rendered as non-editable, firstly the 'Display Only' item type, and secondly any item type whose 'Read-only' condition evaluates to true. For both of these scenarios, APEX renders a SPAN 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. This issue is tracked with Oracle bug 31200377.
  • LABEL elements for page items in APEX 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). This issue is tracked with Oracle bug 31205979.
  • Links in list items that contain an icon do not announce their link text correctly when using JAWS keystroke 'i' to navigate between them. This issue is tracked with Oracle bug 32119718.
  • In Interactive Grid regions, inconsistent row counts are announced to screen readers when pagination type is 'Scroll', 'Show Total Row Count' is on, and there are more rows that initially displayed. This issue is tracked with Oracle bug 32075361.

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.
1.3.2 Meaningful Sequence(Level A)Partially Supports

The product and documentation were tested for:

  • 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.
1.3.3 Sensory Characteristics(Level A)Supports

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
1.3.4 Orientation (Level AA)Not Supported

This product has not yet been evaluated for this criteria

1.3.5 Identify Input Purpose (Level AA)Not Supported

This product has not yet been evaluated for this criteria

1.4.1 Use of Color(Level A)Supports

The product and documentation were tested for:

  • Information conveyed by color is available in alternative formats, such as shape, text, font weight
1.4.2 Audio Control(Level A)Supports The product was tested for:
  • No automatically playing audio is used
1.4.3 Contrast (Minimum) (Level AA)Supports

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

 

1.4.4 Resize text(Level AA)Supports

The product and documentation were tested for:

  • Text can be resized up to 200% without loss of content or functionality
1.4.5 Images of Text(Level AA)Supports

The product and documentation were tested for:

  • 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
1.4.10 Reflow (Level AA)Not Supported

This product has not yet been evaluated for this criteria

1.4.11 Non-text Contrast (Level AA)Not Supported

This product has not yet been evaluated for this criteria

1.4.12 Text Spacing (Level AA)Not Supported

This product has not yet been evaluated for this criteria

1.4.13 Content on Hover or Focus (Level AA)Not Supported

This product has not yet been evaluated for this criteria

2.1.1 Keyboard(Level A)Partially Supports

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:

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.

Affecting Development Environment and Database Applications:

  • Although icon buttons used in our development environment and in Database 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. This issue is tracked with Oracle bug 28293186.
  • In the Interactive Grid region component, when the grid is editable and displaying 'Single Row View', form controls are no longer in the tab order if 'Exclude Null Values' is selected. Users can workaround this by switching to 'Grid View'. This issue is tracked with Oracle bug 25164412.
  • In the Interactive Grid region component, when 'Single Row View' is selected, columns with custom markup containing links or buttons cannot be activated and may contain extra hidden tab stops. Users can workaround this by switching to 'Grid View'. This issue is tracked with Oracle bug 25245829.
  • The Region Display Selector 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. This issue is tracked with Oracle bug 31971687.
2.1.2 No Keyboard Trap (Level A)Supports

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
2.1.4 Character Key Shortcuts (Level A)Not Supported

This product has not yet been evaluated for this criteria

2.2.1 Timing Adjustable(Level A)Partially Supports

The product and documentation were tested for:

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

 

Exceptions:  

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.
2.2.2 Pause, Stop, Hide (Level A)Supports

The product and documentation were tested for:

  • There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)Supports

The product and documentation were tested for:

  • No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz
2.4.1 Bypass Blocks(Level A)Partially Supports

The product and documentation were 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:

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.

Affecting Database Applications:

  • Currently in Universal Theme, we make some use of landmark regions (for example for the main content, and page footer), however we do not make use of landmark regions in the native region templates. This issue is tracked with Oracle bug 31972231.
  • In Universal Theme, page structure needs to be better identified with landmarks. This issue is tracked with Oracle bug 32102597.

Affecting Development Environment and Database Applications:

  • Classic report regions need to better identify their contents with landmarks. This issue is tracked with Oracle bug 32109673.
  • Interactive report regions need to better identify their contents with landmarks. This issue is tracked with Oracle bug 32095473.
2.4.2 Page Titled(Level A)Supports

The product and documentation were tested for:

  • Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)Partially Supports

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:

Affecting Development Environment:

  • On the workspace login page, at the bottom of the page there are three vertical sections containing links to further resources. Below the three sections there are four icons linking to different social media channels. Focus order takes you to the four social icons after tabbing through second section, however focus should instead take you to the four social icon links after tabbing through the third section. This issue is tracked with Oracle bug 29347837.
  • When deleting components in Page Designer, keyboard focus goes back to the top of the page, which can result in a disruptive experience for keyboard and screen reader users. This issue is tracked with Oracle bug 31355918.

Affecting Development Environment, Websheet Applications and Database Applications:

  • When a validation fails on a form page, although the error will be announced to screen readers, we do not explicitly set the focus to help the user more quickly deal with fixing the errors. This issue is tracked with Oracle bug 26878709.
2.4.4 Link Purpose (In Context)(Level A)Partially Supports

The product and documentation were 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

Exceptions:

Affecting Database Applications:

  • The 'HTML 5 Bar Chart' region plug-in used in the development environment, and in the Packaged Apps renders links with confusing link text and structure, where multiple links with different link text all go to the same link target. This issue is tracked with Oracle bug 30902888.

Affecting Development Environment:

  • In the Create Application wizard, we display a large '+' icon link, and immediately adjacent to this an 'Add Page' text link. Both of these links go to the same place (the add page dialog), however the first icon link has no link text. This issue is tracked with Oracle bug 31965257.
2.4.5 Multiple Ways(Level AA)Supports

The product and documentation were tested for:

  • 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
2.4.6 Headings and Labels(Level AA)Partially Supports

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

 

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.
  • One of the administration pages for the Attribute Dictionary in APEX contains a 'Check All' style checkbox in the report's column header, which is missing label text. This issue is tracked with Oracle bug 20310474.

  Affecting Database Applications and Development Environment:

  • In the Interactive Grid region component, some form fields rendered have either no label, or labels that require improvement. This issue is tracked with Oracle bug 25153552.

Affecting Development Environment, Websheet Applications and Database Applications:

  • Rendering a native check box item renders a DIV with role="group" that acts as a container for the group of check boxes and an ARIA-LABELLEDBY attribute providing the label for the group. This works well for check boxes that have more than one check box in the group, but when the check box only has one check box, it is incorrect to render this grouping markup. This issue is tracked with Oracle bug 18188460.
  • Native checkbox and radio group item types contain duplicate labelling. This issue is tracked with Oracle bug 27810346.
  • Native textarea item types contain duplicate labelling. This issue is tracked with Oracle bug 31200582.
2.4.7 Focus Visible(Level AA)Partially Supports

The product and documentation were tested for:

  • Visual indication of the location of the focus

Exceptions

Affecting Development Environment and Database Applications:

  • In the Interactive Grid region component, some interactive controls do not show focus. This issue is tracked with Oracle bugs 25153460 and 25162731.
  • In the Interactive Grid region component, additional hidden tab stops are present after a configuration dialog has been opened. This issue is tracked with Oracle bug 25245934.

Affecting Database Applications:

  • The Tab Container region template which is used to render regions on a page as tabs, contains a 'tablist' element that does not show keyboard focus. This issue is tracked with Oracle bug 30515581.
2.5.1 Pointer Gestures (Level A)Not Supported

This product has not yet been evaluated for this criteria

2.5.2 Pointer Cancellation (Level A)Not Supported

This product has not yet been evaluated for this criteria

2.5.3 Label in Name (Level A)Not Supported

This product has not yet been evaluated for this criteria

2.5.4 Motion Actuation (Level A)Not Supported

This product has not yet been evaluated for this criteria

3.1.1 Language of Page(Level A)Supports

The product and documentation were tested for:

  • Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)Supports

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
3.2.1 On Focus(Level A)Supports

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

 

3.2.2 On Input(Level A)Partially Supports

The product and documentation were tested for:

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

  • In Page Designer, some property changes can result in focus being unexpectedly moved to the top of the page. This issue is tracked with Orcale bug 32069876.
  • Wizard pages sometimes contain a grid element allowing to choose for example a page type in the create page wizard. This grid has some custom behaviour where if you click or select the grid item, this submits the page and moves to the next page of the wizard. This can be confusing for screen reader users, who may have just wanted to select the grid item. This issue is tracked with Oracle bug 32360759.

Affecting Database Applications and Development Environment:

  • Sorting a column of a classic report region causes focus to be unexpectedly moved to the top of the region. This issue is trackecd with Oracle bug 32075821.
3.2.3 Consistent Navigation(Level AA)Supports

The product and documentation were 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 each time
3.2.4 Consistent Identification(Level AA)Supports

The product and documentation were tested for:

  • Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)Partially Supports

The product and documentation were tested for:

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

  • When defining validations in APEX, the developer has the choice to define the 'Display Location' for the associated error message. This can either be 'Inline with Field and in Notification' (default), 'Inline with Field', 'Inline in Notification' or 'On Error Page'. When using the 'Inline with Field' location (where the error message will just appear next to the item with the error), a screen reader user is not notified that the error has occurred. So after submitting the form, the user would just stay on the same page, and would have to go back through the form fields and listen for details of any items with errors (which does with a screen reader because the error message is programmatically associated with the relevant page item). This issue is tracked with Oracle bug 31205839. To workaround this issue, developers should select any location including the 'Notification' position.

  • In APEX, there are two main styles of validation, the traditional server-side validation, where validations are defined on an APEX page, the developer chooses various options related to the validation such as type, error location, error message etc, and then the framework displays the error accordingly. When client-side validation is used (for example if the 'Value Required') item attribute is set, then the user experience is completely different, a generic alert is displayed saying 'Correct errors before saving', and then an inline error is displayed against the item with the error. The user experience and messages are inconsistent to what is displayed in the server-side case. This should be made consistent, giving users the same user experience irrespective of whether the error is a client-side, or server-side validation. This issue is tracked with Oracle bug 31964453.

3.3.2 Labels or Instructions (Level A)Supports

The product and documentation were tested for:

  • Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion (Level AA)Supports

The product and documentation were tested for:

  • Where suggestions for fixing an input error are known, they are provided to the user
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

The product and documentation were tested for:

  • 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
4.1.1 Parsing(Level A)Partially Supports

The product and documentation were tested for:

  • 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.
4.1.2 Name, Role, Value (Level A)Partially Supports

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’ 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 Database Applications:

  • The Tab Container region template which is used to render regions on a page as tabs, contains a 'tablist' element that is not labelled. This issue is tracked with Oracle bug 30515581.
  • In Universal Theme, the 'Collapsible' region template does not clearly indicate its explanded state. This issue is tracked with Oracle bug 32532058.
  • In Universal Theme, when using 'Side' navigation, if the menu is in a collapsed state, the menu no longer works as expected. This issue is tracked with Oracle bug 32086482. To workaround this issue, the menu can be expanded.
  • In Universal Theme, when using 'Side' navigation, the tree widget used contains malformed WAI-ARIA elements. This issue is tracked with Oracle bug 32774466.
  • In Universal Theme, breadcrumb markup is missing some WAI-ARIA information that would make it easier to use with screen readers. This issue is tracked with Oracle bug 32139056.

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.
  • Currently in the Property Editor, the display groups are marked up as DIV elements that are focusable with the keyboard. When focused, users can navigate between display groups with the Up and Down arrow keys, which aids keyboard support of the Property Editor. However, when the DIV is focused, screen readers can announce the display group title twice, and in addition can fail to announce the ARIA expanded state when the display group first gets focus (however, it is announced upon expand or collapse). This issue is tracked with Oracle bug 20693220.
  • In Page Designer, it is possible to edit multiple components at the same time, however when using a screen reader, there is no indication that multiple items are selected. This issue is tracked with Oracle bug 29283988.
  • In Page Designer, the splitter controls used to manage layout are poorly labelled and are missing ARIA-CONTROLS to point to relevant page area. This issue is tracked with Oracle bug 20693603.
  • When using Spotlight search with JAWS, the search output can be confusing and sometimes duplicated. This issue is tracked with Oracle bug 31972027.
  • The Wizard Selection plugin, used in our development environment in creation wizards (for example to select the page type in the create page wizard), is difficult to use with a screen reader. This issue is tracked with Oracle bug 31973124.
  • Wizards used throughout the development environment display a progress train to indicate progress through the wizard. These currently use visually hidden text to convey the current active step to assistive technology, however this should instead use ARIA-CURRENT. This issue is tracked with Oracle bug 32118618.
  • In Page Designer, the tabs used to the different page elements (eg Rendering, Dynamic Actions, Processing etc) use aria-expanded, which is not valid for tabs. This issue is tracked with Oracle bug 32103943.
  • Incorrect shortcut text conveyed to screen readers for accessing application search. This issue is tracked with Oracle bug 32087187.
  • Some buttons in the create page wizard can become difficult to activate with a screen reader. This issue is tracked with Oracle bug 32360759.
  • In the create page wizard, when selecting the 'Parent Navigation Menu Entry' for the Navigation Menu, some options appear visually but disabled (because they are sub-pages that cannot be selected as a parent). Screen reader users do not percieve this information. This issue is tracked with Oracle bug 32360759.

Affecting Development Environment and Database Applications:

  • When logging into a workspace, or a Database 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 count down is not announced properly to screen reader users. This issue is tracked with Oracle bug 29348302.
  • The List View of the native Calendar region type uses DIVs with WAI-ARIA headings for the event list, however this should be implemented using more structured HTML. This issue is tracked with Oracle bug 27941145.
  • In Page Designer > Property editor, the Yes / No style property types currently emit ARIA-REQUIRED on the grouping DIV around the input elements. This is invalid use of ARIA-REQUIRED. This issue is tracked with Oracle bug 27782266.
  • Some configurations of 'required' attributes produce inconsistent output by screen readers, and may confuse users of assistive technology. This can lead to inconsistencies in what is emitted, and possibly confuse a user of Assistive Technology. This issue is tracked with Oracle bug 23761182.
  • In the Interactive Grid region component, when the grid is editable, some inline errors are not discernible to screen reader users. This issue is tracked with Oracle bug 25153917.
  • Row state information such as deleted, inserted or changed is conveyed visually, however this state information is not conveyed to screen reader users. This issue is tracked with Oracle bug 31964989.
  • Interactive report regions can expose different views (for example report view, icon view etc.), which is selected with buttons in the interactive report toolbar. However these buttons do not currently provide anything to assistive technologies to state they are currently selected. This issue is tracked with Oracle bug 32123748. 
  • Where menus are used for page navigation, the menu item corresponding to the current page is missing the ARIA-CURRENT property. This issue is tracked with Oracle bug 32138852.
  • Classic report region current column sort not pereivable with Assistive Technologies. This issue is tracked with Oracle bug 32079384.
  • Interactive report regions contain a column header popup menu that allows fast column-centric operations such as filtering, sorting etc. by the user. This functionality is implemented in such a way that is confusing to screen reader users, becuase it is not clear that it is a popup, and also it is difficult to navigate between the column header, and the popup. This issue is tracked with Oracle bug 32080813.
  • Interactive report regions can sometimes become unusable with screen readers, after the data has been dynamically refreshed. This issue is tracked with Oracle bug 32284084.

Affecting Development Environment, Websheet Applications and Database Applications:

  • When Modal Dialogs are used, the non-modal dialog content is not hidden to screen reader users. This issue is tracked with Oracle bug 30666675.

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.
4.1.3 Status Messages (Level AA)Not Supported

This product has not yet been evaluated for this criteria

back to top

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria
Conformance Level
Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility FeaturesNot ApplicableThe product is designed to be isolated from the underlying platform.
 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesNot ApplicableThe product is designed to be isolated from the underlying platform.
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingSupports

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

504.2.1 Preservation of Information Provided for Accessibility in Format ConversionSupports

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

504.2.2 PDF ExportNot Supported

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.

504.3 PromptsSupports

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.

504.4 TemplatesSupports

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.

 

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

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.

602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Documentation is provided in electronic formats.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory. International hearing-impaired customers should use the TRS at +1.605.224.1837. An Oracle Support engineer will respond to technical issues according to the standard service request process.

back to top

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicableStandards/Guidelines, subject to Oracle's interpretation of those standards(available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.

This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.