Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Forms 12c 12.2.1.4

Product Description:

This VPAT covers the development and runtime environment of Oracle Forms.  Oracle Forms is used to create custom applications, and includes features to make information available to users of assistive technology. Oracle Forms is capable of rendering content as described within this VPAT, when an application developer uses it according to guidance provided in the reference manual, and follows all other applicable accessibility standards and guidelines.

Date:

10-Jul-2019

Contact Information:

accessible_ww@oracle.com

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/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/Level A - Yes
Level AA - Yes
Level AAA - No
Section 508 as published in 2017, at https://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 Non-Web UI was tested for:

  • Images that convey information have meaningful alternative text
  • Contains no images that are decorative
  • Contains no complex images such as charts
  • Data tables include a summary or caption, programmatically connected with the table
  • Controls have an associated name
  • Contains no time-based media
  • Non-text characters are not used or have meaningful alternative text
  • CAPTCHAs are not used

Note:

  • Toolbar buttons are not directly keyboard navigable, but their functionality is replicated using shortcut keys or menu entries. This is standard Windows behavior.

 

The Web UI was tested for:

  • Images that convey information have meaningful alternative text
  • Contains no images that are decorative
  • Contains no complex images such as charts
  • Data tables include a summary or caption, programmatically connected with the table
  • Controls have an associated name
  • Contains no time-based media
  • Non-text characters are not used or have meaningful alternative text
  • CAPTCHAs are not used

 

The Documentation was tested for:

  • Images that convey information have meaningful alternative text
  • Contains no images that are decorative
  • Contains no complex images such as charts
  • Data tables include a summary or caption, programmatically connected with the table
  • Controls have an associated name
  • Contains no time-based media
  • Non-text characters are not used or have meaningful alternative text
  • CAPTCHAs are not used
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)Supports

The Non-Web UI was tested for:

  • User interface component labels are associated with the fields they are labeling
  • Headings are marked as such
  • Lists are marked as such
  • Tables are marked as such, including row and column headers and table captions/summaries where appropriate
  • Groups of components are marked as such, with a description for the group

 

The Web UI was tested for:

  • User interface component labels are associated with the fields they are labeling
  • Headings are marked as such
  • Lists are marked as such
  • Tables are marked as such, including row and column headers and table captions/summaries where appropriate
  • Groups of components are marked as such, with a description for the group

 

The Documentation was tested for:

  • User interface component labels are associated with the fields they are labeling
  • Headings are marked as such
  • Lists are marked as such
  • Tables are marked as such, including row and column headers and table captions/summaries where appropriate
  • Groups of components are marked as such, with a description for the group
1.3.2 Meaningful Sequence(Level A)Supports

The Non-Web UI was tested for:

  • The platform's built-in AT reading/presentation sequence matches the logical reading sequence

 

The Web UI was tested for:

  • The sequence of elements in the DOM matches a logical reading sequence

 

The Documentation was tested for:

  • The sequence of elements in the DOM matches a logical reading sequence
1.3.3 Sensory Characteristics(Level A)Supports

The Non-Web UI 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.

 

The Web UI 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.

 

The Documentation 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 Non-Web UI was tested for:

  • Information conveyed by color is available in alternative formats, such as shape, text, font weight
  • Information conveyed by color has a contrast ratio of at least 3:1

 

The Web UI was tested for:

  • Information conveyed by color is available in alternative formats, such as shape, text, font weight
  • Information conveyed by color has a contrast ratio of at least 3:1

 

The Documentation was tested for:

  • Information conveyed by color is available in alternative formats, such as shape, text, font weight
  • Information conveyed by color has a contrast ratio of at least 3:1
1.4.2 Audio Control(Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Supports

The Non-Web UI was tested for:

  • Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
  • All other text and images of text have a contrast ratio of at least 4.5:1

 

The Web UI was tested for:

  • Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
  • All other text and images of text have a contrast ratio of at least 4.5:1

 

The Documentation was tested for:

  • Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
  • All 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 Non-Web UI was tested for:

  • Text can be resized up to 200% without loss of content or functionality by changing the operating system font size.

 

The Web UI was tested for:

  • Text can be resized up to 200% without loss of content or functionality.

 

The Documentation was tested for:

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

Images of text are not used.

2.1.1 Keyboard(Level A)Supports

The Non-Web UI was tested for:

  • ability to perform functions from the keyboard only
  • logical movement of focus through the controls
  • proper operation of unique keystrokes, including those listed in the product documentation

 

The Web UI was tested for:

  • ability to perform functions from the keyboard only
  • logical movement of focus through the controls
  • proper operation of unique keystrokes, including those listed in the product documentation

 

The Documentation was tested for:

  • ability to perform functions from the keyboard only
  • logical movement of focus through the controls
  • proper operation of unique keystrokes, including those listed in the product documentation
2.1.2 No Keyboard Trap (Level A)Supports

The Non-Web UI 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.

 

The Web UI 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.

 

The Documentation 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)Not Applicable

Time limits are not used.

2.2.2 Pause, Stop, Hide (Level A)Supports

The Non-Web UI was tested for:

  • Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden

 

The Web UI was tested for:

  • Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden

 

The Documentation was tested for:

  • Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden
2.3.1 Three Flashes or Below Threshold(Level A)Supports

The Non-Web UI was tested for:

  • No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

 

The Web UI was tested for:

  • No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

 

The Documentation 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 Non-Web UI was tested for:

  • Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is always automatically met.

 

The Web UI was tested for:

  • Web UI does not repeat any content across multiple pages.

 

The Documentation 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 Non-Web UI was tested for:

  • The name of the software application is meaningful.

 

The Web UI was tested for:

  • Pages have a meaningful title specified in the TITLE element

 

The Documentation was tested for:

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

The Non-Web UI was tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence.

Note:

  • Toolbar buttons are not directly keyboard navigable, but their functionality is replicated using shortcut keys or menu entries. This is standard Windows behavior.

 

The Web UI was tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence. 

 

The Documentation 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

The Non-Web UI was tested for:

  • The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose

 

The Web UI was tested for:

  • The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose

 

The Documentation was tested for:

  • The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose
2.4.5 Multiple Ways(Level AA)Supports

The Non-Web UI was tested for:

  • Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is always automatically met.

 

The Web UI was tested for:

  • Page contains controls that enable reaching all pages

 

The Documentation was tested for:

  • Page contains controls that enable reaching all pages
2.4.6 Headings and Labels(Level AA)Supports

The Non-Web UI was tested for:

  • Headers describe the topic or purpose of the content below them
  • Labels describe the purpose of the associated field

 

The Web UI was tested for:

  • Headers describe the topic or purpose of the content below them
  • Labels describe the purpose of the associated field

 

The Documentation was tested for:

  • Headers describe the topic or purpose of the content below them
  • Labels describe the purpose of the associated field
2.4.7 Focus Visible(Level AA)Supports

The Non-Web UI was tested for:

  • Visual indication of the location of the focus

Note:

  • Toolbar buttons are not directly keyboard navigable, but their functionality is replicated using shortcut keys or menu entries. This is standard Windows behavior.

 

The Web UI was tested for:

  • Visual indication of the location of the focus

 

The Documentation was tested for:

  • Visual indication of the location of the focus

 

3.1.1 Language of Page(Level A)Supports

The Non-Web UI was tested for:

  • Properly set locale/language

 

The Web UI was tested for:

  • Properly set lang attribute for each page

 

The Documentation was tested for:

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

The non-Web UI was tested for:

Exceptions:

  • There is no assistive technology supported method for marking the language for the different passages or phrases in the non-web document or software, and it would not be possible to meet this success criterion with those technologies.

 

The Web UI was tested for:

  • Proper use of lang attribute for text passages that are in a different language than that of the page

 

The Documentation 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 Non-Web UI was tested for:

  • When an element receives focus, it does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window

 

The Web UI was tested for:

  • When an element receives focus, it does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window

 

The Documentation was tested for:

  • When an element receives focus, it does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window
3.2.2 On Input(Level A)Supports

The Non-Web UI was tested for:

  • Changes in the value of user interface components does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window

 

The Web UI was tested for:

  • Changes in the value of user interface components does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window

 

The Documentation was tested for:

  • Changes in the value of user interface components does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window
3.2.3 Consistent Navigation(Level AA)Supports

The non-Web UI was tested for:

  • Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is always automatically met.

 

The Web UI was tested for:

  • Web UI pages do not span multiple pages.

 

The Documentation 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 Non-Web UI was tested for:

  • Images and controls are used and identified consistently throughout the product

 

The Web UI was tested for:

  • Images and controls are used and identified consistently throughout the product

 

The Documentation was tested for:

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

The Non-Web UI was tested for:

  • When input errors are detected, they are described to the user in text, including identifying the item where the error occurred

 

The Web UI was tested for:

  • When input errors are detected, they are described to the user in text, including identifying the item where the error occurred

 

The Documentation was tested for:

  • The documentation has no input fields, except for the search field.
3.3.2 Labels or Instructions (Level A)Supports

The Non-Web UI was tested for:

  • Labels or instructions are provided when the product requires user input.

 

The Web UI was tested for:

  • Labels or instructions are provided when the product requires user input.

 

The Documentation was tested for:

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

The Non-Web UI was tested for:

  • Where suggestions for fixing an input error are known, they are provided to the user.

 

The Web UI was tested for:

  • Where suggestions for fixing an input error are known, they are provided to the user.

 

The Documentation was tested for:

  • The documentation has no input fields, except for the search field.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

The Non-Web UI was tested for:

  • Data is checked for input errors with an opportunity for the user to correct them

 

The Web UI was tested for:

  • Data is checked for input errors with an opportunity for the user to correct them

 

The Documentation was tested for:

  • The documentation does not allow for changes to data.
4.1.1 Parsing(Level A)Supports

The Non-Web UI was tested for:

  • Markup languages aren't used to generate the Non-Web user interface.

 

The Web UI was tested for:

  • Elements have proper start and end tags and do not duplicate attributes.

 

The Documentation was tested for:

  • Elements have proper start and end tags and do not duplicate attributes.
4.1.2 Name, Role, Value (Level A)Supports

The Non-Web UI was tested for:

  • User interface components have a programmatically associated name and role
  • State information, properties, and values are programmatically exposed for user interface components

 

The Web UI 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’.

 

The Documentation was tested for:

  • HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.

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 FeaturesSupports

The Non-Web UI was tested for:

  • Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts
 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 PreferencesSupports

The Non-Web UI was tested for:

  • Responds to platform settings for color, contrast, font type, font size, and focus cursor
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 Non-Web UI was tested for:

  • File conversions preserve accessibility information

 

The Web UI was tested for:

  • File conversions preserve accessibility information
504.2.2 PDF ExportNot Applicable

Product does not use or create PDF content

504.3 PromptsNot Supported

The product does not prompt authors to create content that conforms to WCAG 2.0 AA

504.4 TemplatesNot Applicable

Product does not provide templates

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

Please refer to the Accessibility in Oracle Forms Applications White Paper at http://www.oracle.com/us/corporate/accessibility/resources/forms-applications-accessibility-1358647.pdf

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.

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.