Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Utilities Application Framework (OUAF) 4.4.0.2.0

Product Description:

The product is Oracle Utilities Application Framework which is the underlying framework technology for most of the Utilities applications in UGBU.

It has web based GUI and heavily uses AJAX.

The mobile component of Oracle Utilities Application Framework enables applications built using the framework to use the mobile features/functionality, such as being able to run a sub set of applications features on android or IOS mobile devices. Not all the applications built on framework use this feature. It is based on application specific requirements.

Date:

26-Aug-2019

Archive Note:

This VPAT applies to only version 4.4.0.2.0 prior to 21-Feb-2020. It does not apply to any versions of Oracle Utilities Application Framework (OUAF) after this. This VPAT has been superseded by Oracle Utilities Application Framework (OUAF) 4.4.0.2.0 (Updated).

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

Application Viewer: This feature of the product is not for production use. This feature in the product is intended for an implementer/developer in Customer's IT team and it provides a view of the metadata in the product. This is only intended to be deployed in the development environment of a customer.

Oracle Utilities Application Framework - Software Development Kit (OUAF-SDK): This feature is not for production use. It is not to be deployed with the product. The OUAF-SDK consists of an eclipse plugin and is designed for usage by an implementer/developer in Customer's IT team to customize the product (if required).

Dependent Products

This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.

Evaluation Methods Used:

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

Accessibility Standards/Guidelines

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

Standard/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 web UI 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 Titles for Objects are provided Controls have an associated name Non-text characters are not used or have meaningful alternative text CAPTCHAs are not used The IOS UI was tested for: Controls have an associated name Non-text characters are not used or have meaningful alternative text CAPTCHAs are not used The Android UI was tested for: Controls have an associated name Non-text characters are not used or have meaningful alternative text CAPTCHAs are not used Exceptions: Bug 30170586 - Screen reader is not reading radio button control as button in android (The screen reader still reads the radio button options and users can switch between the options)
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 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 Groups of components are marked up with their description Style sheets are used only to change the layout and presentation on the screen The IOS UI was tested for: User interface component labels are associated with the fields they are labeling through use of the label's text as the Label trait of the labeled field The Android UI was tested for: User interface component labels are associated with the fields they are labeling
1.3.2 Meaningful Sequence(Level A)	Supports	The web UI was tested for: The sequence of elements in the DOM matches a logical reading sequence The IOS UI was tested for: The VoiceOver reading/presentation sequence matches the logical reading sequence for IOS mobile application The Android UI was tested for: The TalkBack reading/presentation sequence matches the logical reading sequence for Android mobile application
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.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 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 Exceptions: Bug 30101407 - Button descriptions do not have recommended color contrast ratios in all pages of both android and ios mobile application
1.4.4 Resize text(Level AA)	Supports with Exceptions	The Web UI was tested for: Text can be resized up to 200% without loss of content or functionality The Android UI was tested for: Text can be resized up to 200% without loss of content or functionality using the Android Zoom feature The IOS UI was tested for: Text can be resized up to 200% without loss of content or functionality using the iOS Zoom feature Exceptions in: Bug 29206091 - Dashboard, scroll bar alignment and visibility issues when sizing to 200% zoom level in web UI. Some widgets in the application toolbar get pushed to a second line with no ability to scroll. The main area of the page is reduced such that only a small amount of data is visible and the scrolling that reduced area supports scrolling. The suggested work around is to zoom out to 175%. The results are more usable.
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: Bug 29455243 - when using ctrl+shift+x in a pop-up search within script (Business Process Assistant - BPA) - whole script window closes (This functionality is specific to developers/ implementers using the web UI, it doesnt affect the application's actual business functionality) Bug 29865579 - Unable to navigate options in home menu pop up in IOS platform using gestures (Users can navigate by clicking on the options provided in the home menu popup) Bug 29865541 - Date picker is not accessible in IOS platform in service history completion page (Hot fix is being made available to fix this issue)
2.1.2 No Keyboard Trap (Level A)	Supports	The web UI 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. The Android UI was tested for: Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control using the built-in TalkBack and Switch Control assistive technologies. The IOS UI was tested for: Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control using the built-in VoiceOver and Switch Control assistive technologies.
2.2.1 Timing Adjustable(Level A)	Supports	The Web UI was tested for: Time limits are longer than 20 hours (Can be configured by the user) The Android and IOS UI were tested for: Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)	Supports	The product was tested for: Moving, blinking, or scrolling content that isn't a pure decoration is part of an essential activity
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)	Not Applicable	The product does not include repeated content.
2.4.2 Page Titled(Level A)	Supports with Exceptions	The Web UI was tested for: Pages have a meaningful title specified in the TITLE element. The IOS UI and the Android UI were tested for: The name of the software application is meaningful. Exceptions: Bug 29318978 - No heading applied to the page title for ui maps popped up by BPA (Business Process Assistant) script. This issue is specific to web UI.
2.4.3 Focus Order(Level A)	Supports with Exceptions	The product was tested for: Logical movement through the focussable components using only the keyboard, in an order that follows a meaningful sequence Exceptions in Web UI: Bug 29629288 - Order of keyboard tabbing not proper in process flow in web UI (The current tabbing order 'zone header > panel fields > train stops > actions buttons' should instead be 'zone header > train stops > panel fields > actions buttons') Bug 29353001 - On the Inbound Web Service deployment page, the WSDL link on each line gets focus only after tabbing through all the broadcast links in web ui Bug 29262470 - In portal based maintenance pages, when clicking Edit or Duplicate and then subsequently cancelling, the cursor focus returns to the beginning of the page in web ui. (Users will have to navigate again to the edit or duplicate buttons, if they need to redo the action) Bug 29262367 - key-nav - upon page load focus is not set on first editable/clickable field in portal based pages in web ui (Users can navigate to the first editable field manually using accessibility options) Bug 29262183 - In script maintenance, when selecting a record from the search, the cursor focus is on the Main tab rather than on the first editable field in web ui (as in other similar pages, users can navigate to the field manually using accessibility options). Bug 29262171 - In query zones, after clicking search, the cursor focus remains in place rather than focusing on the first row of result set in web ui (Users can navigate to the first row in result set manually using accessibility options) Bug 28976510 - In the web ui Attachment Add dialogue, the Filename field remains highlighted even after uploading with valid data on the field (The field should no longer be highlighted as the upload is complete. This can be done manually by navigating away from the field using accessibility options) Exceptions in Android UI: Bug 30070800 - Screen reader is reading the labels in every page twice in android (Hot fix available) Exceptions in both Android & IOS UI: Bug 30169800 - Previous page focus is reflecting in next page in android and ios (The focus appears to be set on to an element in the new page which is inline with an element which had focus on the previous page. Users can navigate manually to the first field in the page using accessibility options)
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 web UI was tested for: Pages can be found using the provided "search" function Page contains controls that enable reaching pages The IOS UI and the Android UI were tested for: Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is always automatically met.
2.4.6 Headings and Labels(Level AA)	Supports with Exceptions	The product was tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field Exceptions in Web UI: Bug 29329961 - Dynamic fields in old style pages not getting label associated in Web UI (In old style(non-ui hint based) pages where java script is used to dynamically show a field based on other conditions, the appropriate label for the field is not accessible. For example, in old style pages where address fields are dynamic based on Country, the derived fields are not correctly associated with their labels) Bug 29262678 - Country page : some form elements dont have labels Bug 29215951 - Checkbox in a list gives "no label" error Bug 28872589 - support label override using meta data for screen reader without the need for hidden label Bug 28764067 - Tables generated from ui hints without a label use generic label - using screen reader
2.4.7 Focus Visible(Level AA)	Supports with Exceptions	The product was tested for: Visual indication of the location of the focus. Exceptions: Bug 28746710 - Cursor focus not clearly visible after using zone explorer menu (After interacting with the zone menu or various pop-ups that the option prompts the cursor focus returns to the top of the page, where as the expectation would be that the focus returns to the explorer zone menu)
3.1.1 Language of Page(Level A)	Supports with Exceptions	The product was tested for: Properly set lang attribute for each page The IOS UI and Android UI was tested for: Properly set language property, where it differs from that of the underlying platform using the *accessibilityLanguage* property Exceptions: Bug 30219732 - Screen reader unable to programatically determine the language in both IOS and Android UI as accessibilityLanguage is not set
3.1.2 Language of Parts(Level AA)	Supports with Exceptions	The Web UI was tested for: Proper use of lang attribute for text passages that are in a different language than that of the page The IOS UI and Android UI were tested for: Properly set language property, where it differs from that of the underlying platform using the *accessibilityLanguage* property Exceptions: Bug 30219732 - Screen reader unable to programatically determine the language in both IOS and Android UI as accessibilityLanguage is not set
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 consistent navigation: 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. Exceptions: Bug 28748333 - Explorer zone menu is not read properly in Firefox by screen reader (The reader doesn't give audible indications that the the explorer zone menu has additional options in the Web UI. The reader doesnt indicate the correct count of explorer zone menu items)
3.3.1 Error Identification(Level A)	Supports with Exceptions	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. Exceptions: Bug 29417415 - Focus issue for combined date/time fields in error in Web UI Bug 29480125 - Error from default validation for a field in a list not marking field in Web UI. This is isolated to a page that includes an expiration date where only the month and year are visible. The system tries to default the hidden day portion of the date. If there is something invalid about the month / year entered, then the defaulting issues an error, but the list occurrence is not available so it doesn't mark the date. However, the error occurs immediately so the user is on the correct page and will know what field is in error. Bug 30169793 - Text field is not highlighting when input error is occurred in Android and IOS UI
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
4.1.1 Parsing(Level A)	Supports	The Web UI was tested for: Elements in HTML content have complete start and end tags, are properly nested and do not contain duplicate attributes Pages validate to the HTML specification The IOS UI and Android UI were tested for: Markup elements have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique Ids Markup content validate to the appropriate markup specification(s) Markup languages are used internally in ways never available to assistive technology or to a user agent
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’. 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 Frames have a meaningful title specified in the title attribute The iOS UI and Android UI was tested for: User interface components have a programmatically associated name and role using the Label property and appropriate Attributes

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	Supports with Exceptions	The product was tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor Exceptions: Bug 30101484 - Page font is not changing when bold text and larger text options are changed in IOS mobile accessibility settings
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	Not Applicable	The Oracle Utilities Product Documentation uses standard web browsing techniques and does not contain accessibility or compatibility features.
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	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.