Oracle Accessibility Conformance Report

The product does not utilize the following:

• Time-based media.
• CAPTCHA.
• Tests that contain non-textual content.

The product was tested for:

• Non-text content that is presented to the user has a text alternative.
• Controls that accept user input have meaningful labels and describes its purpose.
• Non-text content that is for presentation purposes only is implemented in a way that it can be ignored by an AT.
• Images that convey information have meaningful alternative text using ALT.

The product does not utilize audio-only or prerecorded video-only media.

The product does not utilize prerecorded audio content.

The product does not utilize video synchronized media.

The product does not utilize live audio content.

The product does not utilize prerecorded video content.

The product was tested for:

• Column and Row headers on data tables.
• No information is solely conveyed through the style sheet.
• Layout tables use appropriate markup
• 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
• Data tables specify SUMMARY or CAPTION

Exceptions to the above are as follows:

• An issue was identified where a  table used for layout is missing Aria tags in the browse Product Catalog. Bug 19528150.

The product was tested to ensure that the sequence in which content is presented is in a logical tab order.

Exceptions to the above are as follows:

• During testing a small number of logical tab order issues were discovered in the Agent Triage Dashboard. Bug 29881230.
• During testing a small number of logical tab order issues were discovered in the Troubleshooting Guide, when a solution is provided. Bug 29873868.

The product was tested to ensure that color, shape,  physical location, or any other sensory characteristics are not the only means of conveying content or guidance to the user.

The product does not use color or visual presentation as the only means of conveying information to the user.

Exceptions to the above are as follows:

• An issue was identified in the Fluid Approvals page with the Transaction/Group filters on the left hand side of the page where the selection is only indicated by color. Bug 29504041.
• An issue was identified in the HRHD Fluid pages where the state of the Filter button is only indicated by color. Bug 29836498.

The product does not utilize audio based media.

The product was tested for:

• Visual presentation of text to ensure that  a contrast ratio of at least 4.5:1.  
• Large-scale text and images of large-scale text have a contrast ratio of at least 3:1.
• Images of text are not utilized in the product.

Exceptions to the above are as follows:

• In the Toolbar, GoTo dropdown label does not have a contrast ratio of at least 4.5:1. Bug 22472800.

The visual presentation of the product is delivered using a specific PeopleTool's style sheet, "Tangerine" which has been tested to conform to these contrast requirements.   The settings in the delivered style sheet can be overridden by the user, the browser settings, or the operating system.

The product was tested for :

• Text can be resized up to 200% without loss of content or functionality.

The product does not utilize images of text.

The product was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes.
• Proper operation of unique keystrokes and access keys, including those listed in the product documentation.
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms.

Movement of focus through each control can be done using only the keyboard, with no "keyboard trap" that prevents focus from moving away from any control.

The product was tested for:

• Time limits in the product can be turned off before they are encountered.
• Time limits in the product can be adjusted to at last 10 times longer than encountered.
• Time limits in the product can be extended with at least 20 seconds warning up to 10 times.
• Time limits are longer than 20 hours.
• Time limits used are part of a real-time event, or a essential activity.

The product does not contain animation and does not utilize auto-updating that starts automatically or auto-updating that is presented in parallel with other content.

The product was tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.

The product provides HTML headers which enable the user to bypass blocks of content.   Headers are provided for Group Boxes, Scroll Areas, and Grids (Tables).

The product has meaningful page titles specified in the TITLE element.

The product  was tested for:

• Logical tab order through the product controls and selectable elements.
• Consistent use of keyboard keys to perform selection and action.

Exceptions to the above are as follows:

• During testing a small number of logical tab order issues were discovered in the Agent Triage Dashboard. Bug 29881230.
• During testing a small number of logical tab order issues were discovered in the Troubleshooting Guide, when a solution is provided. Bug 29873868.

The product was tested to ensure that the purpose of each link can be understood, its label is meaningful,  and that labels are not vaguely worded.

Exceptions to the above are as follows:

• An issue was identified in the Search Orders and Quotes page where a link is missing the label.  Bug 19274231.

The product provides multiple methods to navigate to a page including:

• Drop down menu.
• Navigation menu ("NavBar").
• Related Actions.
• Links on a page.
• Tiles (buttons) on a homepage.
• Button bars (radio buttons).
• Global search feature to find a page.

The product was tested for:

• Structure and hierarchy conveys meaningful text in header elements on pages.
• Column and Row headers on data tables.

Exceptions to the above are as follows:

• An issue was identified in the Agent Triage Dashboard where the radio button labels do not describe their purpose. Bug 28893135.

The product was tested for:

• Visual cues or feedback to the position of the cursor within the product.
• AT product successfully tracks cursor focus.
• Visual indication of the location of the focus.

Exceptions to the above are as follows:

• An issue was identified in the Agent Triage Dashboard where the Focus indicator is not visible for some elements. Bug 29881021.

The product was tested for:

• Properly set lang attribute for each page.

The product was tested for:

• Proper use of lang attribute for text passages that are in a different language than that of the page.

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.

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 product was tested for consistent navigation and order across pages.

The product has been tested for:

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

Exceptions to the above are as follows:

• UI for administrative functions versus self service is inherently different since the frequency of use varies.  Administrators are trained users whereas self service users are typically infrequent and untrained users.  As such,  the UI for self service functions is different and much simpler than  the UI administrator web pages which results in an inconsistency of the UI across these functions of the product.
• UI for Classic versus Fluid transactions is different since Fluid transactions are a replacement for the legacy Classic transactions.

When input errors are detected, they are described to the user in text, including the identification of the item where the error occurred.

The product was tested for meaningful labels, instructions where applicable, and ALT text.

The product provides messages for input when input errors are automatically detected.   The error messages contain information indicating what the error is and instructions on how to correct the error when known.

The product was tested to ensure that when legal commitments or financial transactions occur that modify or delete user-controllable data that one or more of the following is true:

• Data that is entered by the user is validated for input errors and the user is provided an opportunity to correct the errors before submission.
• Confirmation pages are available for reviewing, confirming, and correcting input before finalizing the submission of data.
• Submissions are reversible or can be re-entered by the user.

The product was tested for:

• Elements in the HTML have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs.
• Pages validate to the HTML specification.

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.

Exceptions to the above are as follows:

• An issue was identified where a  table used for layout is missing layout Aria tags in the browse Product Catalog. Bug 19528150.
• An issue was identified in the Fluid Approvals page with the Transaction/Group filters on the left hand side of the page where the selection is only indicated by color. Bug 29504041.
• An issue was identified in the HRHD Fluid pages where the filter button does not indicate the button state. Bug 29836498.
• An issue was identified in the Agent Triage Dashboard where the radio button labels do not describe their purpose. Bug 28893135.

See WCAG 2.0 Section.

The product does not include authoring tools that provide format conversions or saving content in multiple formats.

The product does not provide export of PDF files.

The product does not prompt authors to create accessible content. Bug 27488962.

The product does not provide templates.

The product documentation describes:

• Screen Reader mode user preferences and runtime.
• Special keystrokes needed to operate controls.
• Workarounds.

Accessibility-related documentation can be found in the Enterprise PeopleTools 8.57 PeopleBook: PeopleSoft Accessibility Guide which describes screen reader mode and common accessibility related issues and how to prevent them when authoring content.

Product documentation is in electronic format.