Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

ADF Faces Rich Client Components (output of JDeveloper), 11g R1 Fusion Apps updated3.1 Rel11

Product Description:

This VPAT only covers Application Development Framework (ADF) Faces Rich Client Components 11g R1 Fusion Apps Rel11, (output of Oracle JDeveloper 11g R1 Fusion Apps Rel11). It does not cover the issues when developing native mobile apps or that are built on ADF Mobile Browser framework that uses Apache MyFaces Trinidad components. Please also refer to the ADF Mobile VPAT for any application issues that were built on ADF Mobile Browser framework using Apache MyFaces Trinidad components and not on ADF Faces rich client components. For the JDeveloper user environment, refer to the Oracle JDeveloper 11g R1 Fusion Apps Rel11 VPAT.

ADF is capable of rendering content as described below, when an application developer uses it according to guidance provided in the reference manual, and follows all other applicable accessibility standards and guidelines, and in conjunction with the following 3 runtime modes: To provide content that is optimized for screen reader users, then the "accessibility mode" option should be set to "screenReader" in the application's trinidad-config.xml file. To provide content that is optimized for users who leverage platform high-contrast capabilities, then the "accessibility-profile" option should be set to "high-contrast" in the trinidad-config.xml file. To view content in large font that works in conjunction with browser zoom, then the "large-fonts" option should be set in trinidad-config.xml file. These options can all be dynamically specified on a per-user basis. For more information, see the Apache Trinidad Developer's Guide. The information provided in this VPAT only applies when the relevant mode is enabled for each applicable technical standard.

Date:

16-Mar-2018

Archive Note:

This VPAT applies to only version 11. It does not apply to any versions of ADF Faces Rich Client Components (output of JDeveloper), 11g R1 Fusion Apps after this.

Contact Information:

accessible_ww@oracle.com

Notes:

Configuring accessibility is done in the Trinidad.xml file. The system administrator will need to configure the file for screen reader support.

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 JDeveloper 11g R1 Fusion Apps updated3.1 REL11

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/index.html

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/Guideline	Included In Report
Web Content Accessibility Guidelines 2.1	Level A - Yes Level AA - Yes Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018	Yes

Terms

The terms used in the Conformance Level information are defined as follows:

Supports: The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Partially Supports: Some functionality of the product does not meet the criteria.
Does Not Support: Majority of functionality of the product does not meet the criteria.
Not Applicable: The criteria are not relevant to the product.

WCAG 2.1 Report

Table 1 also documents conformance with:

Section 508: Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Partially 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) 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 : Bug# 13414846 : In Screen Reader mode, Gauge components will render in PNG format and include a simple client-side image map with the ALT attribute set on each AREA element. This can sometimes cause screen reader technologies to read the underlying data multiple times. Furthermore, if the Gauge component is data-bound to a collection such that it renders a series of multiple gauges, then the resulting image map structure can be at odds with use of the Tab key to navigate through the resulting GaugeSet. Bug# 18170173: The screen reader labels do not have the complete information for the Browser Based Theme Editor (BBTE) section . Bug# 20383948: In the ADF table component, add an extra header that spans several columns and give this header a label and a tooltip. Now, when we run the workbook and give focus to the first cell of the extra header, the screenreader does not announce that the cell "has comment" (tooltip). Pressing "ALT+SHIFT+'" also does nothing. The workaround is to give keyboard focus to the cell that contains the label text for the extra header row. Press tab or right arrow until we hit the cell where the screeenreader reads "has comment". Now, pressing "ALT+SHIFT+'" makes the screeenreader read the tooltip text.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	Audio/video content is not included in the product.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	Audio/video content is not included in the product.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	Audio/video content is not included in the product.
1.2.4 Captions (Live) (Level AA)	Not Applicable	Audio/video content is not included in the product.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	Audio/video content is not included in the product.
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 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 Exception : Bug# 21278388 : In accessibility mode, the column width of af:column is different across browsers. Additionally, the column stretching is disabled due to which the column fails to expose the content inside it completely to user. BUG 21784789: Tables in product documentation are missing row headers
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 included a reference to the text alternative of the graphic
1.3.4 Orientation (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.3.5 Identify Input Purpose (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
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)	Not Applicable	Audio/video content is not included in the product.
1.4.3 Contrast (Minimum) (Level AA)	Partially Supports	The product was tested for: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 Other text and images of text have a contrast ratio of at least 4.5:1 Exceptions : Bug# 14751806: While using high contrast accessibility settings, the thumbs are not visible on the inputRangeSlider component. Bug# 18170177: In the Browser Based Theme Editor (BBTE), some errors are seen when color contrast is enabled. Bug# 16682226: In the high contrast mode, the borders do not show up for the input textfield and the drop down list. Bug# 14828981 Visual indication is not present to distinguish which items are disabled in a list in high contrast mode. BUG 25026225 Color contrast issues while in screen reader mode in multiple areas
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
1.4.10 Reflow (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.4.11 Non-text Contrast (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.4.12 Text Spacing (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.4.13 Content on Hover or Focus (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
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# 8760162 : Some elements of the Hierarchy Viewer are not reachable using just the keyboard. Bug# 7610581 : Unable to scroll the DVT Flash graph using just the keyboard. Bug# 16068227: In ScreenReader mode and with AutoSubmit turned on, pressing Enter in InputNumberSpinBox does not fire ValueChangeEvent. However, tabbing out of the box does fire this event. Bug# 11892309: The ADF tree cannot be navigated through completely with only the keyboard. Bug# 17210559: In the Show details pop-up, when the 'OK' button is clicked, no action is performed, and the popup still remains open. Bug# 16306021: In the DVT diagrammer, the palette and the legend elements of HTML 5 diagrams are currently not accessible. Bug# 20546800: In the screenreader mode, the clienlistener on an active component does not get called at all, which results in the Toaster in EM not working in the screenreader mode. Bug# 19254790 : Screen reader does not read the associated header member when focused on "Expand/Collapse" drill link in pivot table header cell. Bug# 21817208 : Gantt attributes that are disabled in the UI are still shown in accessibility mode (Split, Completed Through) with some invalid data values. Bug# 21945185 : In the screen reader mode, the Hierarchy Viewer component in Copy Configurations page is overlapping with the table below it, making the text and the graphic icons look jumbled. There are no such issues found in the normal mode. Bug# 25948384: In Read Only table with screen reader, using down arrow key doesn't bring row keyboard navigation down into the table rows. Bug# 25959754: When using inputComboboxListOfValues in screen reader mode, user is not able to select values from Drop Down Bug# 25971487: Selection of row(s) in the editable tree component is lost when accessing the table toolbar
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.1.4 Character Key Shortcuts (Level A)	Not Supported	This product has not yet been evaluated for this criteria
2.2.1 Timing Adjustable(Level A)	Not Applicable	There is no time sensitive content included in the product.
2.2.2 Pause, Stop, Hide (Level A)	Not Applicable	There is no flashing or moving content included in the product.
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 WAI-ARIA Landmark elements are used 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)	Partially Supports	The product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence Exceptions : Bug# 21351294 : We are not able to expand the tree node correctly in the screenreader mode. The focus exits the forms mode when trying to expand the tree, to get the focus back, we need to press 'Esc' or 'Enter'. Bug# 16530272: After creating a new node in a tree table,the focus goes to the Create button link instead of the child node.
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 are contained in a "site map" Pages can be found using the provided "search" function Pages are in a site table of contents Pages are fully inter-linked to each other Page contains controls that enable reaching all 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.
2.5.1 Pointer Gestures (Level A)	Not Supported	This product has not yet been evaluated for this criteria
2.5.2 Pointer Cancellation (Level A)	Not Supported	This product has not yet been evaluated for this criteria
2.5.3 Label in Name (Level A)	Not Supported	This product has not yet been evaluated for this criteria
2.5.4 Motion Actuation (Level A)	Not Supported	This product has not yet been evaluated for this criteria
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 : 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
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)	Partially Supports	The product was tested for: Labels or instructions are provided when the product requires user input Exceptions : Bug# 22023901 : In the af:codeEditor component of the Datacomposer, the attribute label of its textarea field is not specified.
3.3.3 Error Suggestion (Level AA)	Partially Supports	The product was tested for: Where suggestions for fixing an input error are known, they are provided to the user Exception : Bug# 22384911 : Suggestions for correction of input errors are not provided.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Partially Supports	The product was tested for : Submissions can be reversed by the user 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 Bug# 25949728: With af:autoSuggestBehavior, while in screen reader mode, when autoSubmit is set on, then AutoSuggest behavior results in "Invalid value" error.
4.1.1 Parsing(Level A)	Supports	This 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
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’. 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 Exception : Bug# 17822011: In the Preferences --> Search page, the description for the icons in the Graphic list of the screen reader does not match their enabled/disabled status as shown on the screen. Bug# 18170095: In the Browser Based Theme Editor, while tabbing through the different links, what the screen reader reads before editing varies from what it reads after editing. Bug# 25241174: While in screen reader mode, duplicate frame title in multiple areas Bug# 25755813: While in screen reader mode, in the Chrome Browser, message dialog is not being read Bug# 25774947: While in screen reader mode, drop down menu with Role button contains an error Bug# 25866976: In screen reader mode, Date Picker expects user to type in date, but description indicates how to get to calendar Bug# 26160206: When selectBooleanRadio is embedded in a table, unselected buttons are not accessible via keyboard. This is true in Default mode and Screen Reader mode
4.1.3 Status Messages (Level AA)	Not Supported	This product has not yet been evaluated for this criteria

2018 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	Supports	See the responses in the WCAG 2.0 section of this report.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	ADF Faces Rich Client Components do not perform format conversion
504.2.2 PDF Export	Not Applicable	Product does not export PDF
504.3 Prompts	Supports	Oracle JDeveloper, the product that provides the ADF components, provides Audit Rules functionality that provides users feedback on content to conform to Accessibility requirements.
504.4 Templates	Supports	Product does not provide templates

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	Not Supported	Product does not have Accessibility Features documentation, BUG 26175494
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.