Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Application Express (APEX) 20.2

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:

08-Oct-2020

Archive Note:

This VPAT applies to only version 20.2. It does not apply to any versions of Oracle Application Express (APEX) after this. This VPAT has been superseded by Oracle Application Express (APEX) (Updated) 21.1.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

Calendar Component, Month and Week Views - The calendar is a native region type that supports viewing calendar and event information. 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 to the month and week views is the list view, which is covered by this VPAT and available in the same 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.
The Oracle by Example (OBE) tutorials are using templates that have not been accessibility tested. This issue is tracked with Oracle bug 26608336.
Help documentation provided in PDF format.
External content (web pages served from non-APEX-Workspace domains).

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.

Dependent Products

This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.

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/Guideline	Included In Report
Web Content Accessibility Guidelines 2.1	Level A - Yes Level AA - Yes Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018	Yes

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)	Supports
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Supports	The product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)	Partially Supports	The product was tested for: No Pre-recorded video content is being used. Exceptions: Affecting Documentation: Videos on the Application Express YouTube channel are missing closed captions. This issue is tracked with Oracle bug 29370906.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Supports	The product has no multimedia.
1.2.4 Captions (Live) (Level AA)	Supports	The product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)	Supports	The product has no multimedia.
1.3.1 Info and Relationships (Level A)	Partially Supports	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: 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 and Database Applications: In the Faceted Search region component, the form controls displayed for a facet should be grouped by the facet label to provide extra context. This issue is tracked with Oracle bug 30380808. In the Faceted Search region component, if a facet count is displayed, this can be difficult to understand for screen reader users. This issue is tracked with Oracle bug 31964057. The Markdown item type is not correctly labelled. This issue is tracked with Oracle bug 30902322. 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. In the Popup LOV item component, when displaying multiple columns in the search results, although the results are announced as a data table, the table is missing an accessible label. This issue is tracked with Oracle bug 30375933. 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.
1.3.2 Meaningful Sequence(Level A)	Supports
1.3.3 Sensory Characteristics(Level A)	Supports
1.3.4 Orientation (Level AA)	Supports
1.3.5 Identify Input Purpose (Level AA)	Partially Supports	The product was tested for: Text fields which collect information about the user contain the appropriate autocomplete content attribute. The autocomplete attribute is defined in the 'Custom Attributes' page item property in APEX. Exceptions: Affecting Development Environment and Database Applications: The autocomplete attribute is missing from the pages in APEX that collect information about the user. This issue is tracked with Oracle bug 31978520.
1.4.1 Use of Color(Level A)	Supports
1.4.2 Audio Control(Level A)	Supports	The product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)	Partially Supports	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: Affecting Documentation: The 'JavaScript API Reference' chapter of the documentation has text that does not meet the minimum contrast requirements. This issue is tracked with Oracle bug 29370357.
1.4.4 Resize text(Level AA)	Supports
1.4.5 Images of Text(Level AA)	Supports
1.4.10 Reflow (Level AA)	Partially Supports	The product was tested for: Text information reflows so that only one direction of scrolling is required while at 400% zoom. Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content. Exceptions: Affecting Development Environment: Horizontal scroll is required throughout the development environment, when zoomed at 400%. This issue is tracked with Oracle bug 31964090.
1.4.11 Non-text Contrast (Level AA)	Supports
1.4.12 Text Spacing (Level AA)	Supports
1.4.13 Content on Hover or Focus (Level AA)	Partially Supports	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. Exception: Affecting Development Environment and Database Applications: Tooltips used throughout APEX fail the 'hoverable' test, because the tooltip disappears if you move the mouse over it. This issue is tracked with Oracle bug 31888900.
2.1.1 Keyboard(Level A)	Partially Supports	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: 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 Faceted Search region component, users have no easy way to navigate with keyboard from the facet region to the results region, other than tabbing through all the facet controls. This issue is tracked with Oracle bug 30380719. 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. Affecting Database Applications: When using the Universal Theme, a developer has two choices for the app's navigation menu system, 'Top', and 'Side'. When using 'Side' navigation, the app's navigation will appear in a tree structure on the side of the page. In addition, the end user has the option to expand or collapse the navigation menu, using a toggle button on the page. This expand / collapse functionality has two further developer options, 'Hidden' (the default) where the collapsed state actually hides the navigation menu completely, and 'Icon', where the navigation menu just collapses down to icons. When using the 'Icon' option, the icons cannot receive keyboard focus. This issue is tracked with Oracle bug 31112489. A keyboard user can workaround this by expanding the navigation menu, to be able to interact with it. When a Popup LOV item is used on a modal page, and where the Popup LOV is based on a Shared List of Values with multiple columns defined, keyboard navigation breaks and the user is unable to move down the list of options. This issue is tracked with Oracle bug 31676267. Note: As the issue only occurs under these exact circumstances, developers can work around it by either not using a modal page, or by using a Shared List of Values that just uses a display and return column, instead of multiple columns.
2.1.2 No Keyboard Trap (Level A)	Supports
2.1.4 Character Key Shortcuts (Level A)	Supports
2.2.1 Timing Adjustable(Level A)	Supports
2.2.2 Pause, Stop, Hide (Level A)	Supports
2.3.1 Three Flashes or Below Threshold(Level A)	Supports
2.4.1 Bypass Blocks(Level A)	Partially Supports	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: Affecting Development Environment and Websheet Applications: There are no 'Skip to Main Content' links implemented for the Development Environment, or in Websheet Applications. 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.
2.4.2 Page Titled(Level A)	Supports
2.4.3 Focus Order(Level A)	Partially Supports	The product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence Exceptions: Affecting Development Environment: 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 was tested for: The text of links and their surrounding paragraph, list, table cell (with marked up table headers), or preceding heading is sufficient to describe their purpose Exceptions: Affecting Database Applications: In a Database Application using the Universal Theme, when the 'Card' report template has the template option 'Display Subtitle' unchecked, this results in the text "#CARD_SUBTITLE#" still being rendered in the link text. This issue is tracked with Oracle bug 29348961. Affecting Development Environment: On the Shared Components page in the Application Builder, there are two links 'Data Sources > REST Enabled SQL' and 'Security > Web Credentials', that visually display a '>' right arrow to the right of the link, to indicate that these link to workspace-scoped (not just application-scoped) components. The '>' text is not accessible to screen reader users. This issue is tracked with Oracle bug 31964540. 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
2.4.6 Headings and Labels(Level AA)	Partially Supports	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: 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: Native checkbox and radio group item types contain duplicate labelling. This issue is tracked with Oracle bug 27810346.
2.4.7 Focus Visible(Level AA)	Partially Supports	The product was 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)	Supports
2.5.2 Pointer Cancellation (Level A)	Supports
2.5.3 Label in Name (Level A)	Supports
2.5.4 Motion Actuation (Level A)	Supports
3.1.1 Language of Page(Level A)	Supports
3.1.2 Language of Parts(Level AA)	Supports
3.2.1 On Focus(Level A)	Supports
3.2.2 On Input(Level A)	Supports
3.2.3 Consistent Navigation(Level AA)	Supports
3.2.4 Consistent Identification(Level AA)	Supports
3.3.1 Error Identification(Level A)	Partially Supports	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: 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
3.3.3 Error Suggestion (Level AA)	Supports
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports
4.1.1 Parsing(Level A)	Partially Supports	The product was tested for: Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs 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 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 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 just renders as a standard HTML list, and does not follow the Tabs design pattern. This issue is tracked with Oracle bug 30515581. Affecting Development Environment: 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. 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. 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. The Faceted Search region component requires better notifications of partial page updates for screen reader users. This issue is tracked with Oracle bug 30380762. The Markdown item type renders a custom editor for defining the markdown. Screen readers can miss details of some text entered into the editor. This issue is tracked with Oracle bug 30902322. Affecting Development Environment, Websheet Applications and Database Applications: In the Popup LOV item component, 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. This issue is tracked with Oracle bug 30375933. In the Popup LOV item component, when displaying multiple columns in the search results, extra 'No results found' text will be incorrectly announced to screen readers. This issue is tracked with Oracle bug 30375933. 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.
4.1.3 Status Messages (Level AA)	Supports

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria	Conformance Level	Remarks and Explanations
302.1 Without Vision	Not Applicable
302.2 With Limited Vision	Not Applicable
302.3 Without Perception of Color	Not Applicable
302.4 Without Hearing	Not Applicable
302.5 With Limited Hearing	Not Applicable
302.6 Without Speech	Not Applicable
302.7 With Limited Manipulation	Not Applicable
302.8 With Limited Reach and Strength	Not Applicable
302.9 With Limited Language, Cognitive, and Learning Abilities	Not Applicable

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 AA	Supports	See the responses in the WCAG 2.0 section of this report.
502 Interoperability with Assistive Technology	Heading cell - no response required	Heading cell - no response required
502.2.1 User Control of Accessibility Features	Not Applicable
502.2.2 No Disruption of Accessibility Features	Not Applicable
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable
502.3.2 Modification of Object Information	Not Applicable
502.3.3 Row, Column, and Headers	Not Applicable
502.3.4 Values	Not Applicable
502.3.5 Modification of Values	Not Applicable
502.3.6 Label Relationships	Not Applicable
502.3.7 Hierarchical Relationships	Not Applicable
502.3.8 Text	Not Applicable
502.3.9 Modification of Text	Not Applicable
502.3.10 List of Actions	Not Applicable
502.3.11 Actions on Objects	Not Applicable
502.3.12 Focus Cursor	Not Applicable
502.3.13 Modification of Focus Cursor	Not Applicable
502.3.14 Event Notification	Not Applicable
502.4 Platform Accessibility Features	Not Applicable
503 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Not Applicable
503.3 Alternative User Interfaces	Not Applicable
503.4 User Controls for Captions and Audio Description	Heading cell - no response required	Heading cell - no response required
503.4.1 Caption Controls	Not Applicable
503.4.2 Audio Description Controls	Not Applicable
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Supports	The product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Supports	The product is not an authoring tool.
504.2.2 PDF Export	Partially Supports	The product was tested for: PDF files conform to PDF/UA-1 Where a component supports it, the 'Include Accessibility Tags' option should be checked when exporting to PDF. This is currently supported with the Interactive Grid native region type. Exceptions: Affecting Development Environment, Websheet Applications and Database Applications: Classic Report regions allow PDF export that does not include the necessary accessibility tags. This issue is tracked with Oracle bug 31961351. Note: Interactive Report and Interactive Grid regions do support the 'Include Accessibility Tags' option, and therefore are supported. In addition, APEX provides an API, APEX_REGION.EXPORT_DATA, which allows for any component in APEX with a data source (which includes Classic Reports), to export supported PDF (where the parameter p_pdf_accessible is set to true).
504.3 Prompts	Supports	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 Templates	Supports	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.

Chapter 6: Support Documentation and Services

Criteria	Conformance Level	Remarks and Explanations
602 Support Documentation	Heading cell - no response required	Heading cell - no response required
602.2 Accessibility and Compatibility Features	Supports	The product documentation describes: Accessibility Guide, dedicated to helping you both use APEX, and build APEX apps that meet accessibility guidelines. Special keystrokes needed to operate controls Please visit the APEX documentation homepage and then select 'Accessibility'.
602.3 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support Documentation	Not Applicable
603 Support Services	Heading cell - no response required	Heading cell - no response required
603.2 Information on Accessibility and Compatibility Features	Supports	Oracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication Needs	Supports	Oracle 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.

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.