Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Application Framework Release 12.2.9

Product Description:

Oracle Application Framework (OA Framework) is an integrated platform for developing and deploying Oracle E-Business Suite HTML-based applications.

This VPAT only covers OA Framework runtime user interface components, user interface interactivity and functional administration pages.

Date:

27-Jan-2020

Archive Note:

This VPAT applies to only version 12.2.9 prior to 23-Mar-2020. It does not apply to any versions of Oracle Application Framework after this. This VPAT has been superseded by Oracle Application Framework (Updated) Release 12.2.9.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

Oracle JDeveloper with OA Extension (an Oracle E-Business Suite design-time extension) that makes up the integrated development environment (IDE) for OA Framework.
The Look Ahead List of Values (LOV) has type-ahead search capabilities. When an end-user types in a few characters (generally at least three) into an LOV search field, all matching results for the characters are fetched and displayed inline to the LOV component in a Look Ahead LOV window. The Look Ahead LOV is disabled in 'Screen Reader Optimized' accessibility mode. As a workaround, the user may open the classic LOV modal window to search for and select a value and achieve the same functionality. (Bug 17656938)
The Inline Date Picker is disabled in 'Screen Reader Optimized' accessibility mode. The date can be entered manually into the field without using the inline date picker. In "Standard Accessibility" mode, if there is more than one date field associated with the Inline Date Picker, the date may need to be entered manually into the fields or use the Date Picker pop-up window. (Bug 3822637)
Classic and Advanced tables (except table-in-table) by default have the first column set as row header but if the column is hidden or there is no data in that column then there is no row header. (Bugs 12366533 and 13522659)
Three workarounds are
(1) Rearrange the columns via Table Settings
(2) Set the row header through Personalization
(3) Reorder the table column (shifting first column of table to one that is displayed on screen or keeping first column where data exists) through Personalization
Rich interaction in Classic and Advanced tables enable a user to scroll vertically and horizontally with Up/Down arrow keys and Left/Right arrow keys, respectively. In 'Screen Reader Optimized' mode, rather than vertical scrolling, there is pagination so user may select the "Next" and "Previous" links to display next or previous sets of rows.
Personalization Workbench is a WYSIWYG (“What you see is what you get”) Personalization Editor. The workaround is to use Classic Personalization.

For Web UI, the user needs to enable accessibility mode either from the Login page or Preferences page by choosing one of these values for the Accessibility poplist value:

‘Screen Reader Optimized’
‘Standard Accessibility’

Explanation of how the Login screen works:

The accessibility mode only needs to be set once by the user to a value other than 'None' if needed. If a screen reader user forgets to set the mode to 'Screen Reader Optimized' then on the main navigator page, the screen reader will speak "The application is running in inaccessible mode. This can be changed from the preferences screen."
If on the Login page the user selects 'Standard Accessibility' or 'Screen Reader Optimized', a profile gets automatically set to that value which can be seen on the Preferences page.
If user selects 'None' on the Login page, the value on the Preferences page stays to whatever it was last set to.

Please review the Oracle E-Business Suite User's Guide for more detailed information about accessibility features.

Additionally, it is recommended to review and apply "Section 4: Post-Install Critical Fixes" in document Oracle E-Business Suite Release 12.2 Upgrade Considerations for OAF-based Applications and Oracle CRM Technology Foundation, Document 1927975.1.

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.

Oracle JavaScript Extension Toolkit (JET) 6.0.0

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.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.gov	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.
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 with Exceptions	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) Titles for Objects and Applets are provided Controls have an associated name Text summary or alternative is provided for time-based media Client-side image maps specify the ALT attribute on each AREA element. CAPTCHAs are not used Exceptions: Navigator in global menu has a search field with x icon to clear out the field without alternative text (Bug 22583698) Client-side image map area does not have alt text in Firebox browser (Bug 12422818)
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.4 Captions (Live) (Level AA)	Not Applicable	The product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	The product has no multimedia.
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 captions/summaries where appropriate Data tables specify SUMMARY or CAPTION 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: Checkboxes are not grouped together (Bug 14389672) Gantt chart tables do not have row headers (Bug 16811950) Content container with bulleted list should have a heading tag (Bug 22085737) Search and Select: LOV does not have row header (Bug 18807487) Manage Favorites page has table with wrong row header (Bug 17405723) Copy Personalization page has a table without summary defined (Bug 23241341) Create Look and Feel page has inner table within advanced table without a summary (Bug 17400523) Need to implement WAI-ARIA landmark roles (Bug 27656173) Shuttle controls with description fields have same labels (Bug 21440621) Simplified home page has optional announcement section without heading tag (Bug 29011633) List Search has field with value 'New Search' which needs a title or aria-label (Bug 29795464) About this page has table summaries with internal ids rather than meaningful descriptions (Bug 29588805) The workaround to set or change Classic, Advanced and LOV table row headers and summaries is to use Personalization.
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 Instructions provided which refer to graphics include a reference to the text alternative of the graphic
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 Information conveyed by color has a contrast ratio of at least 3:1
1.4.2 Audio Control(Level A)	Not Applicable	The product has no multimedia.
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 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 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: Keyboard only users are not able to move inline attachment windows nor pop-up windows (Bugs 20316651 and 22661773) Navigator in global menu has a search field with x icon to clear out the field and it is not keyboard navigable (Bug 22583698) A workaround for keyboard only user is to press the backspace key to clear the search field. Hide/Show button does not activate with Space Bar key (Bug 29133685) A workaround is to activate the Hide/Show button with Enter key. Optional Multi select choice controls are not keyboard only enabled (Bug 27448225)
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	The product was tested for: User Session Limits can be set by a System Administrator with profile options 'ICX: Session Timeout' and 'ICX: Limit Time'. User Session Limits and Session Timeout Behavior is documented in the Oracle E-Business Suite Security Guide, Part No. E22952-17
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: 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
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 with Exceptions	The product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence Exception: If a table is detached, focus doesn't automatically move to it (Bug 29601790)
2.4.4 Link Purpose (In Context)(Level A)	Supports	The product was tested for: The text of links and their surrounding paragraph, list, or table cell (with marked up table headers), is sufficient to describe their purpose
2.4.5 Multiple Ways(Level AA)	Supports	The product was tested for: Pages can be found using the provided "search" function Page contains controls that enable reaching pages
2.4.6 Headings and Labels(Level AA)	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
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	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
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	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
3.3.2 Labels or Instructions (Level A)	Supports	The product was tested for: Labels or instructions are provided when the product requires user input
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 Data can be reviewed, corrected, and confirmed by the user before they are 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 Pages validate to the HTML specification Exception: All IDs are not unique (Bug 21700059)
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’. 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: The Favorites and Navigator menus in the global header need to be marked up as WAI-ARIA menu buttons which open dialogs (Bug 24413789) Tab pages are links and need WAI-ARIA tab role (Bug 19501349) The home page navigator tree needs to be a WAI-ARIA tree view widget (Bug 17214262) HGrid tables should be WAI-ARIA tree view widgets (Bug 17214504) Messages need WAI-ARIA alert role (Bug 19518333) Simplified home page springboard favorites icons are marked up with WAI-ARIA tab role but should be links (Bug 20759893) Modal dialogs need aria-modal set to true (Bug 29030043)

2017 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria	Conformance Level	Remarks and Explanations
302.1 Without Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of Color	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without Speech	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited Manipulation	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and Strength	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning Abilities	Not Applicable	The 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 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	The product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility Features	Not Applicable	The product is designed to be isolated from the underlying platform.
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and Headers	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.4 Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.6 Label Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.8 Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.10 List of Actions	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on Objects	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.14 Event Notification	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
503 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Not Applicable	The product is designed to be isolated from the underlying platform.
503.3 Alternative User Interfaces	Not Applicable	The product does not have assistive technology features.
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	The product has no multimedia.
503.4.2 Audio Description Controls	Not Applicable	The product has no multimedia.
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Not Applicable	The product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product is not an authoring tool.
504.2.2 PDF Export	Not Applicable	The product is not an authoring tool.
504.3 Prompts	Not Applicable	The product is not an authoring tool.
504.4 Templates	Not Applicable	The product is not an authoring tool.

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	For additional information, refer to My Oracle Support Knowledge documents and E-Business Suite documents: Oracle E-Business Suite User's Guide, Part No. E22956 Oracle Application Framework Personalization Guide, Part No. E22031 Oracle Application Framework Profile Options, Document 1315510.1 Oracle Application Framework Developer's Guide, Document 1315485.1 Oracle Application Framework Release Notes for Release 12.2.9, Document 2567090.1. Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Documents, Document 1302189.1
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	Product documentation is in electronic format.
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.