ACR: Oracle APEX Development UI 26.1

Oracle Accessibility Conformance Report

VPAT® Version 2.5

Name of Product:

 Oracle APEX Development UI 26.1

Product Description:

Includes:

The responses to many of the technical standards are based on functionality provided by underlying technologies : please see the ACR listed in the Dependencies section for more information.

Report Date:

29-APR-26

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following product areas:

Dependent Products


This product interacts with or is built with the other Oracle products listed in this section. Click below to view information about the accessibility of these dependent products. Products listed are the versions available at the time of publication of this document; newer documents may be available that supersede these 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/

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.0Level A - Yes
Level AA - Yes
Level AAA - No
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Web Content Accessibility Guidelines 2.2Level 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.2 Report

Table 1 also documents conformance with:

Note: When reporting on conformance with the WCAG 2.2 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)Not ApplicableThe product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.4 Captions (Live) (Level AA)Not ApplicableThe product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableThe 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:

  • Bug 25153940: The 'Quick Edit' and 'Live Template Options' features, available as a developer of an application via the developer toolbar, are inaccessible to screen reader users. 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.
  • Bug 33637363: In the create list wizard on the page used to define list entries, the input elements are displayed in a grid format, however the markup used is not consistent with this, making it difficult to navigate with a screen reader.
  • Bug 35649157: When configuring the Self Service Signup Wizard in Instance Administration, there is an option to enable a survey. The Question and Answer fields are displayed in a grid format, however the markup used is not consistent with this, making it difficult to navigate with a screen reader.
  • Bug 35637020: When defining Substitutions in App Builder > Edit Application Properties, the substitution string fields are displayed in a grid format, however the markup used is not consistent with this, making it difficult to navigate with a screen reader.
  • Bug 37127451: The account menu in App Builder poses a navigation issue for screen reader users. When using screen readers, the menu appears disconnected and at the end of the page rather than near the activated button. This makes it challenging for users to navigate and understand their on-screen position.
  • Bug 38072346: Interactive Report columns using the “APEX 25.1 List Item (Single Column)” template component cannot specify a single row header value, so screen readers treat the entire cell content as the row header text.
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)Supports
1.4.1 Use of Color (Level A)Supports
1.4.2 Audio Control (Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Supports
1.4.4 Resize text (Level AA)Supports
1.4.5 Images of Text (Level AA)Supports
1.4.10 Reflow (Level AA)Supports
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)Supports
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:

Bug 35194834: The following two places in the development environment allow users to select a color, and where the color name provided using the TITLE attribute, which displays to mouse users on hover, however keyboard users have no way of perceiving this text:

Create App Wizard > Choose Application Icon > Pick an Icon

Instance Admin > Define Environment Banner > Color

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)Supports
2.4.2 Page Titled (Level A)Supports
2.4.3 Focus Order (Level A)Supports
2.4.4 Link Purpose (In Context) (Level A)Supports
2.4.5 Multiple Ways (Level AA)Partially 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

Exceptions:

  • Bug 34991575: In Instance Administration, although pages are fully inter-linked to each other, there is no search functionality.
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:

  • Bug 34130672: Help button labels that contain HTML are announced as unescaped HTML to screen reader users.
  • Bug 35222938: In the Object Browser > Sample Queries Grid, the 'Copy' and 'Run' buttons are incorrectly labelled by the current grid cell's context.
2.4.7 Focus Visible (Level AA)Supports
2.4.11 Focus Not Obscured (Level AA)Supports
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
2.5.7 Dragging Movements (Level AA)Partially Supports

The product was tested for:

  • All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.
  • The functionality of dragging movements are determined by the user agent and not modified by the author.

Exceptions:

  • Bug 36836211: The Workflow Designer currently requires either mouse dragging or keyboard usage for node rearrangement.
2.5.8 Target Size (Minimum) (Level AA)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.2.6 Consistent Help (Level A)Supports
3.3.1 Error Identification (Level A)Supports
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
3.3.7 Redundant Entry (Level A)Supports
3.3.8 Accessible Authentication (Minimum) (Level AA)Supports
4.1.1 Parsing (Level A)Not ApplicableThis criterion is considered as always satisfied for any content using HTML or XML.
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 programmatically exposed name
  • Frames have a meaningful title specified in the title attribute

Exceptions:

  • Bug 29283988: 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.
  • Bug 33839482: In Page Designer, as tooltips are displayed a corresponding hidden DIV is added to the bottom of the DOM. These are not visible, however are perceivable with a screen reader and worsen the user experience.
  • Bug 34401775: The email sent from the Purge Workspace notification has text that indicates the user should press a button to action the purge, although the action button looks like a button, it is actually a link, which is confusing to screen reader users.
  • Bug 34859370: On the App Builder homepage, the report can optionally be rendered using 'Icon View'. In this view, for each application, a group of elements is displayed (link to the app, edit button, and run button) and these elements are not semantically grouped. To workaround this issue, please choose the 'Report View'.
  • Bug 35074290: In Page Designer on the 'Search' tab, all elements in the tab panel have ARIA-CONTROLS pointing to an unlabelled element.
  • Bug 35156073: In Page Designer, when using the layout option 'Two Pane Mode', the 'Rendering' tree becomes unusable with a screen reader. To workaround this issue, use 'Three Pane Mode'.
  • Bug 35454775: From the login page, some instance configurations will cause a confirmation dialog to be shown on the APEX login page. This dialog appears modal visually, however it is not coded as a modal dialog.
  • Bug 39160531: Three Code Editor fields are missing labels, making it difficult for screen reader users to identify those fields.
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 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.

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
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionSupports
504.2.2 PDF ExportSupports
504.3 PromptsSupports

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

Oracle APEX includes a built-in tool called the Advisor, which can be run by developers as part of quality assurance of an 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. 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 DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

The documentation includes a general Developer Guide. Please visit the Oracle APEX documentation homepage and then select 'Develop Apps'.

In addition, there is dedicated help for accessibility, comprising:

  • Accessibility Guide, dedicated to helping you both use Oracle APEX, and build Oracle APEX apps that meet accessibility guidelines.
  • Special keystrokes needed to operate controls.

Please visit the Oracle APEX documentation homepage and then select 'Accessibility'.

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

Product documentation is in electronic format.

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.

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicable Standards/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.