Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Utilities Testing Accelerator 6.0.0.3

Product Description:

Oracle Utilities Testing Accelerator (OUTA) is comprised of a Web Application for designing, managing & executing automated test suites. It additionally has an eclipse IDE plug-in for executing tests. The tests can be executed either in the eclipse IDE or via the web application.

Date:

15-Mar-2021

Archive Note:

This VPAT applies to only version 6.0.0.3. It does not apply to any versions of Oracle Utilities Testing Accelerator after this. This VPAT has been superseded by Oracle Utilities Testing Accelerator 7.0.0.0.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following:

Eclipse IDE: This is a 3rd party application. Refer to https://help.eclipse.org/oxygen/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Fconcepts%2Faccessibility%2Faccessmain.htm
Test Execution Plugin for Eclipse: As an alternative use the browser based test execution feature for running automated tests

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.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)	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 Titles for Objects and Applets are provided Controls have an associated name CAPTCHAs are 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)	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. Layout tables use appropriate markup. Exceptions: Bug 29427036 - Content in language based flow definition and rest body editor is not read by screen reader Bug 29239422 - Screen reader does not read type of the chart for chart's present under analytics tab in dashboard page Bug 31523233 - Doesn't always read out the combo box contents properly in define subroutine interface dialog Bug 31516543 - Screen reader does not read the column name for each cell in the table in the view component definition screen. The entire row content (component line definition) is read in order without specifing the column name for each cell.
1.3.2 Meaningful Sequence(Level A)	Supports	The product was tested for: The sequence of elements in the Document Object Model (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.
1.3.4 Orientation (Level AA)	Supports	The product was tested for : Text is displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)	Not Applicable	The product was tested for: There are no text fields that collect information about the user.
1.4.1 Use of Color(Level A)	Supports	The product was tested for: Information conveyed by color is available in text.
1.4.2 Audio Control(Level A)	Not Applicable	The product has no multimedia.
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 31516719 - The contrast ratio for the "Passed" text in flow set history page is low
1.4.4 Resize text(Level AA)	Partially Supports	The product was tested for: Text can be resized up to 200% without loss of content or functionality. Exceptions: Bug 30721409 - In search component drop downs are not visible properly when zoomed in Bug 30721542 - Names of the main tabs in the application are missing when zoomed in Bug 30721575 - When zoomed in,context menu is visible at the bottom of the page,only when scrolled down options are visible Bug 30721593 - In create component page few buttons are not visible properly when zoomed in. Bug 30721633 - Update flow page content is missing when zoomed in. Bug 30721638 - Edit test data table rows are not visible when zoomed in. Bug 30721657 - Flow icon and text is getting overlapped with view logs button when zoomed in. Bug 30721682 - Flow execution history page's data is getting cut when zoomed in. Bug 30721690 - Update flowset window data is missing. when zoomed in. Bug 30721698 - In execute flowset window few buttons are missing when zoomed in. Bug 30721717 - Subroutine interface variable table rows are missing when zoomed in.
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	The product was tested for: Text information reflows so that only one direction of scrolling is required while at 400% zoom. Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content Exceptions: Bug 31685019 - At 400% zoom, application's UI does not work.
1.4.11 Non-text Contrast (Level AA)	Supports	The product was tested for: Non-text items have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)	Partially Supports	The product was tested for: When the following attributes and no others are modified there is no loss in functionality or content: Line height (line spacing) to at least 1.5 times the font size Spacing following paragraphs to at least 2 times the font size Letter spacing (tracking) to at least 0.12 times the font size Word spacing to at least 0.16 times the font size Exceptions: Bug 31684965 - When modifying text spacing,the function name in the function libraries table is getting truncated Bug 31684929 - When modifying text spacing,the flow name in the email summary page(both flow and flowset) is getting overlapped
1.4.13 Content on Hover or Focus (Level AA)	Supports	The product was tested for: Dismissable -The content can be dismissed without moving the pointer or keyboard focus Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
2.1.1 Keyboard(Level A)	Partially Supports	The product was tested for: Ability to perform functions from 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: Sticky Keys and Filter Keys (feature names may be different on different platforms) Exceptions: Bug 31523110 - Clicking on enter key when focus is set on the hyperlink to Oracle Utilities Application Framework based application(the environment name of the application being tested) in the view execution summary dialog closes the execution summary dialog instead of opening the application defined on the hyperlink in a browser window.
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 Applicable	The product was tested for: There are no single character keyboard shortcuts.
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 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)	Supports	The product was tested for: Blocks of content are not repeated.
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 29427013 - Focus is not set properly for flow, component and flow definition tree, after selecting copy/paste options from context menu Bug 29426903 - Data grid in find component usage dialog is not focused on dialog open Bug 29426511 - File chooser is not focused on load of import page
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)	Partially Supports	The product was tested for: Page contains controls that enable reaching all pages Exception: Bug 29536400 - User should be able to find pages in the application using search function
2.4.6 Headings and Labels(Level AA)	Supports	The product was tested for: Headings 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 Applicable	The product was tested for : There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)	Not Applicable	The product was tested for : There are no single pointer operations
2.5.3 Label in Name (Level A)	Supports	The product has been tested for : User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually.
2.5.4 Motion Actuation (Level A)	Not Applicable	The product was tested for : There are no functions that require motion of the device.
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)	Not Applicable	The product was tested for: There are no passages or phrases 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 in the page, an additional change of keyboard focus or the spawning of a pop-up window.
3.2.3 Consistent Navigation(Level AA)	Supports	The product was tested for: Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time.
3.2.4 Consistent Identification(Level AA)	Supports	The product was tested for: Images and controls are used and identified consistently throughout the product.
3.3.1 Error Identification(Level A)	Partially 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. Exceptions: Bug 29529515 - Field in error doesnt receive focus after the error message
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)	Partially Supports	The product was tested for: Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicates and have unique ID's. Exceptions: Bug 29231677 - Flow definition page has duplicate id's and few elements in the page don't have labels . Bug 31516457 - In rest test data page id attribute value of save is not unique-in pre validations Bug 31516698 - Id attribute values of buttons & fields is not unique in flow set gui - id attribute value is no unique for : Refresh,Ok buttons , abort button,search flow Search box on flow set execution, id of fields in flow & user set configuration. Bug 31516748 - ID attribute value must be unique for the toggle button in workbench pages Bug 31565471 - ID attribute value must be unique for close button in edit request page and the settings dialogue in the edit request page Bug 31565595 - ID attribute value must be unique for "Replace Test Data" button and Find Component Usage Dialog. The form element "header checkbox's" label in the Find Component Usage Dialog is not being read.
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' Frames have a meaningful title specified in the title attribute Exceptions: Bug 31516726 - Flow definition page frame doesn't have title attribute Bug 31523090 - The hyperlink to the Oracle Utilities Application Framework based application that is being tested(the environment name of the application being tested) is being read as close in the summary dialog in flow email summary page
4.1.3 Status Messages (Level AA)	Supports	The product was tested for : Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

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	Not Applicable	The product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product is not an authoring tool.
504.2.2 PDF Export	Not Applicable	The product is not an authoring tool.
504.3 Prompts	Not Applicable	The product is not an authoring tool.
504.4 Templates	Not Applicable	The product is not an authoring tool.

Chapter 6: Support Documentation and Services

Criteria	Conformance Level	Remarks and Explanations
602 Support Documentation	Heading cell - no response required	Heading cell - no response required
602.2 Accessibility and Compatibility Features	Supports	OUTA accessibility reference document contains information on accessibility features. The product documentation contains or refers to Oracle JavaScript Extension Toolkit (JET) documentation that describes: special keystrokes needed to operate controls workarounds Accessibility-related documentation can be found at: https://docs.oracle.com/en/middleware/developer-tools/jet/9/develop/developing-accessible-applications.html A reference guide for keystrokes and touch gestures can be found at: http://www.oracle.com/pls/topic/lookup?ctx=jetlatest&id=OJACC
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	Support 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.