Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Financial Reporting 11.2

Product Description:

Oracle Financial Reporting (FR) is an on-premises reporting solution that enables book quality financial and management reporting targeted at meeting the unique requirements of the Finance department or any functional area that requires very highly formatted multidimensional reporting. This financial reporting solution uses EPM on-premises products (Hyperion Financial Management, and Hyperion Planning) as data sources.

A graphical, object based interface enables the rapid creation of reports that combine grids of data and text, charts, graphs, and images. A library of reusable report components simplifies and streamlines the process of building and maintaining complex reports
Users have complete control over layouts, formatting, fonts, and colors, as well as a flexible range of output options enabling wide distribution via print, HTML Web pages, PDF, and online viewing. A scalable, cross-platform report server facilitates easy deployment to large user communities.
Reports and books can be dynamically scheduled, with the ability to generate and email separate report outputs for members in a dimension (bursting).

Note: In order to ensure that reports are accessible, FR report designers will need to enter alternate text for grids, charts, text boxes and images in the properties sheet in FR Web Studio, and enter a report description when saving a report. Please refer to the Financial Reporting Web Studio User's guide for additional details.

Date:

26-Sep-2019

Archive Note:

This VPAT applies to only version 11.2 prior to 21-Feb-2020. It does not apply to any versions of Oracle Financial Reporting after this. This VPAT has been superseded by Oracle Financial Reporting 11.2 (Updated).

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

Support for mobile devices, such as Apple and Android
PDF output format for Financial Reporting reports and books
Support for product documentation in PDF, MOBI, and EPUB format. The information in the product documentation is also available in the accessible HTML format.

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.

ADF Faces Rich Client Components (output of JDeveloper), 11g R1 Fusion Apps updated3 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.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	The product was tested for: Meaningful icon/image/object identification including object state change on selection (e.g., folder open on selection) Financial Reporting (FR) Grids represent data tables. The grid name can be defined in FR Studio, it is displayed as SUMMARY Other objects (Chart and Image) have names defined in FR Studio, displayed as Alt Text. Report description is shown as the Page Title Non-text content has information available via alternate methods. CAPTCHA is not used
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	The product was tested for: User interface component labels are associated with the fields they are labeling 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 Groups of components are marked up with their description
1.3.2 Meaningful Sequence(Level A)	Supports with Exceptions	This product was tested for: Logical and meaningful keyboard navigation Exceptions: In the Web Studio while using assistive technologies, cannot open selecting repository objects which have focus using the keyboard (bug #30159937)
1.3.3 Sensory Characteristics(Level A)	Supports	The product was tested for: User interface and dialog checked to ensure that on-screen indicators or instructions do not rely solely on any object's shape, size or position.
1.4.1 Use of Color(Level A)	Not Applicable	The default settings in the product do not use color or font styles to indicate meaning. In Report Designer, the user has the ability to set conditional formatting where they can associate color or font with grid cell values via conditional formatting. There is no ability to add alternate text for conditional formatting. This customization would cause the information to no longer be accessible
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. Tested complete application in High contrast and normal mode provided in the workspace preferences. Verified the FR modules honoring the High contrast and normal mode as per user preference setting.
1.4.5 Images of Text(Level AA)	Supports	The product was tested for: Images of text are not used.
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 Exceptions: In the Explore repository, some of the defined shortcut keys are not operable (Bug 29229166) In the Web Studio, shortcut keys are not defined for the separate panels (e.g. Repository, Summary, Report and Report Properties), so the user can efficiently move focus between them (Bug 29955692) In the Web Studio with a grid selected in the design element table and the grid filling the design area, there is no way/method available to make selections via keyboard in the grid (Bug #30142429). In the Web Studio, in the main content area, within the Report header appears a defined mnemonic shortcut of T to reach the area. This mnemonic does not work. To get to the main content area, the user must use the mnemonic to reach the Summary (Alt+U) and then Tab to the Report area. (Bug #30142283)
2.1.2 No Keyboard Trap (Level A)	Supports	This 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	Application time out message will appear in user inactivity and provide the user option to continue or exit. The time out message set by workspace.
2.2.2 Pause, Stop, Hide (Level A)	Supports	The product was tested for: Moving content is not a pure decoration and is part of an essential activity There is no 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 with Exceptions	The product was tested for: A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page. Exceptions: In the Web Studio with the report selected in the design element table, the frame on the right changes to "Report Properties". The Description field shows a defined mnemonic shortcut of D (underlined character) to reach this field. This mnemonic does not work, focus does not move to field. (Bug #30142466) In the Web Studio, in the main content area, within the Report header appears a defined mnemonic shortcut of T to reach the area. This mnemonic does not work. To get to the main content area, the user must use the mnemonic to reach the Summary (Alt+U) and then Tab to the Report area. (Bug #30142283)
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 tab order through the product controls and selectable elements Exceptions: Incorrect tab order to get to the Report Attachment button in the Annotation Attachment tab (Bug 9177858) In the Web Studio, During forward-navigation into the design element table, the icons of Save, Add, Delete. are not available when the element has focus (Tab does not move focus) to these icons. (Bug #30142340).
2.4.4 Link Purpose (In Context)(Level A)	Supports	The product was tested for: The text of links and their surrounding paragraph, list, table cell (with marked up table headers), or preceding heading is sufficient to describe their purpose
2.4.5 Multiple Ways(Level AA)	Supports	The product was tested for: Reports and books can be found by either browsing the 'Explore' module, via the Workspace File > Open menu and by using the 'Search' functionality.
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 Exceptions: In the Web Studio, when using Tab to navigate into the Report main content area, and specifically to the "Name" in the report design elements table, no focus indicator is present to provide the keyboard user the current focus location. (Bug #30142299) In the Web Studio, when using the mnemonics menu shortcuts to reach the application menus (File, Edit, View, etc), the menu does not show it has received focus (no dashed outline of the menu appears). It is not apparent to the user that the shortcut has worked properly (or at all). (Bug #30142237)
3.1.1 Language of Page(Level A)	Supports	This product was tested for: Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)	Supports	This product was tested for: Proper use of lang attribute for the page, and does not use text passages that are in a different language than that of the page
3.2.1 On Focus(Level A)	Supports with Exceptions	This 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 Exceptions: In the Web Studio, using navigation of the design element table using the down-arrow key, focus is grabbed by the elements (e.g. Grid1) and focus is moved into the grid. This move of focus should not occur during navigation, but only when the element is selected (via Enter or some other defined keystroke) (Bug #30142401)
3.2.2 On Input(Level A)	Supports	This 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. The only pop-up window in FR that may appear is a dialog box within the same browser window. If a new dialog launches, the focus will be on the dialog and the user would need to respond to it to proceed.
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: Meaningful icon/image/object identification including object state change on selection (e.g., folder open on selection)
3.3.1 Error Identification(Level A)	Supports	This 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	This product was tested for: Error messages are meaningful for the end users. 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)	Not Applicable	This product does not contain web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses.
4.1.1 Parsing(Level A)	Supports	This product was tested for: Unique ids are used through out the product for coding purposes Ensure attributes are not duplicated on the same element. Ensure elements are properly nested. Elements in HTML content have complete start and end tags Pages validate to the HTML specification
4.1.2 Name, Role, Value (Level A)	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’. Frames have a meaningful title specified in the title attribute

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	Supports	The product was tested for: Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts
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	Financial Reporting is a web application that uses standard technologies which run in a browser and are not a plugin/applet.
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 WCAG 2.0 Section
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Supports	The product was tested for: File conversions preserve accessibility information
504.2.2 PDF Export	Not Supported	PDF files generated by Financial Reporting utilize Oracle BI Publisher components, which do not generate accessible output.
504.3 Prompts	Not Supported	Bug 26565510: The product does not prompt authors to create content that conforms to WCAG 2.0 AA
504.4 Templates	Not Applicable	Templates are not provided.

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	The product documentation describes: Accessibility modes, at runtime Accessibility-related documentation can be found at: http://docs.oracle.com/cloud/latest/pbcs_common/PBCAC/accessibility_for_financial_reporting.htm#PBCAC-GUID-DF57297A-0D63-4AE4-B6A1-6A8DF684A71C
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.