Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Application Express 5.0.4

Product Description:

Oracle Application Express is a web-based development framework for building web applications. There are known issues with this product, which have been cited in this document under one or more of the following categories:

  • Development Environment - The development environment for Application Express.
  • 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.

Application Express is a modern, web-based development framework, and as such relies on modern web technologies including HTML5, JavaScript, CSS and WAI-ARIA. The information supplied in this VPAT only applies when the product is used with Firefox and JAWS. Additionally, the accessibility runtime modes 'Screen Reader' or 'High Contrast' must be set accordingly, as listed below.

Significant defects found during testing that impact multiple technical standards are:

Affecting Development Environment, Websheet Applications and Database Applications:

  • 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. Workaround for Database Applications: Use the 'Classic Datepicker' which is coded to the standards. Workaround for Development Environment: Enter the date manually into the date input field. This issue is tracked with Oracle bug 9740473.
  • The modern calendar region type is not coded to standard and as such has many accessibility issues. Workaround for Database Applications: Use the 'Legacy Calendar' which is coded to standards. Workaround for Development Environment: Use the report page showing the same underlying information, which can be filtered or sorted by date to provide a similar view of information. This issue is tracked with Oracle bug 20696874.

Date:

23-Aug-2017

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:
  • 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.
  • All sample applications, available from the Packaged Applications page in the Application Express development environment.
  • The following non-sample applications, available from the Packaged Applications page in the Application Express development environment; APEX Application Archive, Application Standards Tracker, Bug Tracking, Checklist Manager, Community Requests, Customer Tracker, Data Reporter, Decision Manager, Expertise Tracker, Feedback, Go Live Checklist, Group Calendar, Incident Tracking, Live Poll, Meeting Minutes, Opportunity Tracker, P-Track, Survey Builder, Use Case Status.
  • External content (web pages served from non-APEX-Workspace domains).
  • System generated emails.
There are 2 accessibility modes available in Application Express:
  • Screen Reader Mode - If you are using Application Express with a screen reader, please ensure you have Screen Reader Mode enabled.
  • High Contrast Mode - If you are running a Websheet application in Application Express in conjunction with Windows High Contrast Mode, please ensure you have High Contrast Mode enabled. Please note, the Application Express development environment does not require any mode be enabled to support Windows High Contrast Mode.
 To enable these modes:
  • For the Application Express development environment, Screen Reader Mode is enabled via the select list in the 'Accessibility Mode' region on the workspace home page.
  • For Application Express Websheet applications, both Screen Reader and High Contrast modes are enabled via links at the bottom of the Websheet application home page.
 To learn more about what these modes do and also other information for keyboard-only and screen reader users of Application Express, please see the 'Accessibility in Oracle Application Express' appendix in the 'Application Builder User's Guide' book of the product documentation.

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/us/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.0, at http://www.w3.org/TR/2008/REC-WCAG20-20081211/Level A - Yes
Level AA - Yes
Level AAA - No
Section 508 as published in 2017, at http://www.Section508.govYes

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.
Supports with Exceptions
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.0 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.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria
Conformance Level
Remarks and Explanations
1.1.1 Non-text Content (Level A)Supports The product was 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
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)Supports with Exceptions 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 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.
1.3.2 Meaningful Sequence(Level A)Supports The product was tested for:
  • The sequence of elements in the DOM matches a logical reading sequence
1.3.3 Sensory Characteristics(Level A)Supports The product was 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.4.1 Use of Color(Level A)Supports The product was 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 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
1.4.4 Resize text(Level AA)Supports The product was 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 was 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
2.1.1 Keyboard(Level A)Supports with Exceptions 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 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.
2.1.2 No Keyboard Trap (Level A)Supports The product was 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.2.1 Timing Adjustable(Level A)Supports with Exceptions The product was 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 was tested for:
  • There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)Supports The product was 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)Supports The product was tested for:
  • Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
2.4.2 Page Titled(Level A)Supports The product was tested for:
  • Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)Supports The product was tested for:
  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
2.4.4 Link Purpose (In Context)(Level A)Supports with Exceptions 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 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.
2.4.5 Multiple Ways(Level AA)Supports The product was 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)Supports with Exceptions 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 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.
2.4.7 Focus Visible(Level AA)Supports The product was tested for:
  • Visual indication of the location of the focus
3.1.1 Language of Page(Level A)Supports The product was tested for:
  • Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)Supports The product was 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 was 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)Supports with Exceptions The product was 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, 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.
3.2.3 Consistent Navigation(Level AA)Supports The product was 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 was tested for:
  • Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)Supports with Exceptions 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.
3.3.2 Labels or Instructions (Level A)Supports with Exceptions The product was tested for:
  • 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.
3.3.3 Error Suggestion (Level AA)Supports The product was 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 was 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)Supports with Exceptions 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)Supports with Exceptions 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 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.

back to top

2017 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 ConversionNot Supported

Information may not be preserved when converting formats.

504.2.2 PDF ExportNot Supported

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.

504.3 PromptsNot Supported

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

504.4 TemplatesSupports

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.

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 with Exceptions

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.

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 http://www.oracle.com/us/corporate/accessibility/oracle-accessibility-program-173235.html) 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/us/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.