Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Utilities Analytics 2.7.0.1

Product Description:

Oracle Utilities Analytics (OUA) is a suite of pre-built analytics applications for the utilities industry built on Oracle Business Intelligence Enterprise Edition (OBIEE) platform. It is a single data repository with pre-built data integration to the Oracle Utilities Source Applications, please see price list mapping for details

OUA user interface accessibility is predicated on OBIEE.  

This VPAT is only applicable to interacting with content that has already been created according to the best practices / appendix document. Here is the accessibility best-practice guidelines document:

http://docs.oracle.com/middleware/1221/biee/BIEUG/appaccess.htm#BIEUG2756

Date:

11-Jul-2019

Contact Information:

accessible_ww@oracle.com

Notes:

Oracle® Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition has a section called Accessibility Features that describes the steps required for configuration.

Accessibility mode is either enabled at the login screen or in the My Account settings preference dialog.

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/us/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 with Exceptions

The product was tested for:

  • Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
  • Non-text content having text alternative that serves equivalent purpose.
  • CAPTCHAs are not used
Known Issues:
  • Bug  29718659 - Two pages (Failure and repair analysis and Maintenance Cost Analysis) have tables where no accessible text is defined. This may cause screen reader not to read information on these pages 
  • Bug  29723448 - The gauge reports in Preventive maintenance page are not readable by screen readers.
  • Bug  29724045 - Damage assessment map is not converted to data table and hence the report data may not be readable by screen readers.
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 with Exceptions

The product was tested for:

  • Style sheets used only to change the layout and presentation of the screen.
  • Data tables use the TH, TD, SUMMARY or CAPTION attributes.
  • Complex data tables use the TH, TD, SUMMARY or CAPTION attributes.
  • HTML generated by OBIEE uses TD and TR for drop down lists.

Known Issues :

  • Bug  29724225 - Tables on the two pages (Customer outages and Storm analysis) are incorrectly labelled as data tables rather than layout tables.This may lead to incorrect interpretation by screen readers.
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

There are no shape, size, visual location, orientation, or sound elements in the product.

1.4.1 Use of Color(Level A)Supports

Color is not used as the only visual means of conveying information.

1.4.2 Audio Control(Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Supports with Exceptions

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
  Known issues:
  • Bug 29861735 - The minimum required contrast ratio between foreground and background colors in tabs of Apex admin tool pages is not maintained. This can result in incorrect visual representation for the user. 
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.
  • Logical movement of focus through the controls.
  • Proper operation of unique keystrokes and access keys.
  • The ability to use the product with OS keyboard aids.

Known issues:

  • Bug  29759119 - While creating a new schedule on Schedule configuration page of admin tool, the user is unable to navigate for selecting values for the child pop up fields directly through keyboard Tab key . The user can alternatively click on the first child pop up field and then navigate through other fields using Tab key.
     

 

 

2.1.2 No Keyboard Trap (Level A)Supports

The product was tested for:

  • Movement of focus through controls 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:

  • Time limits in the product can be adjusted to at least 10 times longer before encountered.
2.2.2 Pause, Stop, Hide (Level A)Supports

The product contains no animation.

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:

  • Skippable repetitive navigation links.
  • Appropriate use of headers.
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

The product was tested for:

  • Ability to perform functions from the keyboard only.
  • Logical movement of focus through the controls.
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) is sufficient to describe their purpose.

 

2.4.5 Multiple Ways(Level AA)Supports

The product was tested for:

  • Navigating from one Web page to another Web page.
2.4.6 Headings and Labels(Level AA)Supports

Product was tested for:

  • Topics are well described with valid heading and labels, which conveys the purpose.
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 pages.
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

There are no navigational mechanisms that are repeated.

3.2.4 Consistent Identification(Level AA)Supports with Exceptions

The product was tested for:

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

Known Issues: 

  • Bug  29723312 - Work and Asset analytics pages which are having more than one table have multiple elements with the same id attribute and may not be programmatically identified.
  • Bug  29724193 - Outage analytics pages which are having more than one table have multiple elements with the same id attribute and may not be programmatically identified.
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 with Exceptions

The product was tested for:

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

Known issues:

  • Bug  29723516 - Change in month field in date picker is not read by screen reader. This will impact Outage analytics pages which are having date picker in filter.
  • Bug  29759145 - Screen reader reads columns as “Clickable” for even non clickable column contents in Apex admin tool pages.
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:

  • 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.
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

Known Issues:

  • Bug  29723312 - Work and Asset analytics pages which are having more than one table have multiple elements with the same id attribute and may not be programmatically identified.
  • Bug  29724193 - Outage analytics pages which are having more than one table have multiple elements with the same id attribute and may not be programmatically identified.
4.1.2 Name, Role, Value (Level A)Supports with Exceptions

The product was tested for:

  • User interface components have alternate text.
  • 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’.

Known Issues:

  • Bug 29724045 - Damage assessment map is not converted to table and hence not readable by screen readers.

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 FeaturesNot ApplicableThe product is designed to be isolated from the underlying platform.
 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesNot ApplicableThe product is designed to be isolated from the underlying platform.
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingNot ApplicableThe product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot ApplicableThe product is not an authoring tool.
504.2.2 PDF ExportNot ApplicableThe product is not an authoring tool.
504.3 PromptsNot ApplicableThe product is not an authoring tool.
504.4 TemplatesNot ApplicableThe product is not an authoring tool.

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 Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition has instructions on how to configure accessibility.   Below is link of Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.   https://docs.oracle.com/cd/E23943_01/bi.1111/e10544/appaccess.htm
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 documents are 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 http://www.oracle.com/us/corporate/accessibility/oracle-accessibility-program-173235.html) 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/us/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.