Oracle Accessibility Conformance Report

The product was tested for:

• Meaningful icon/image/object identification.
• Meaningful images have alternative text.
• Grids have a table summary.
• PIA pages have meaningful page titles.
• PDF reports that are generated using the appropriate SQR commands to support Table, List, Paragraph, Heading, etc conform to this requirement.
• If an SQR is developed with the appropriate commands to embed tags to identify content such as Table, List, Paragraph, heading, Alternate text etc, a tagged PDF output can be  generated in a manner in which a screen reader can be utilized to read the content.

The product does not utilize the following:

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

The product was tested for:

• Column and Row headers on data tables.
• No information is solely conveyed through the style sheet.
• Tables (Grids and Group Boxes) used for presentation are marked up correctly for layout purposes
• 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
• Layout tables use appropriate markup
• Groups of components are marked up with their description

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

This product does not use color or shapes as the only means of providing information or guidance to the user.

The product was tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.

The product was tested for :

• Text fields which collect information about the user contain the appropriate autocomplete content attribute.

There is one noted exception as follows :

Bug 30965431   Enable AutoComplete Attribute for Classic

Fluid application can implement autocomplete attribute requirement today with PeopleTools.  However Classic application doesn't and PeopleSoft continues to support Classic pages.  The enhancement is to make autocomplete attribute available in classic application too.

This product does not use color as the only means of providing information.

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.

An Application release is tied to a specific PeopleTool's stylesheet. The stylesheets "Tangerine" , Tangerine Fluid" and "Classic Plus" have been tested to conform to the Large text and contrast requirements.

Some areas of the older stylesheets do not meet high contrast mode or color contrast mode. The settings in these stylesheets can be changed and overridden by user, browser system or operating system.

The product was tested for :

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

The product was tested for:

• Images of text are not used in place of actual text.

This product has not yet been evaluated for this criteria. Bug 30966209

This product has not yet been evaluated for this criteria. Bug 30965474

This product does not use color as the only means of providing information. Bug 30966240

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.

The product was tested for:

• Logical tab order through the product controls and selectable elements.
• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys.
• Proper and Consistent use of keyboard keys to perform selection and action.
  • Hotkeys/keyboard shortcuts available to skip elements

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 :

• There are no single character keyboard shortcuts.

The product was tested for:

• Inactivity timeout length is configurable by the Administrator.
• 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.

This product was tested for :

• There is no moving, blinking or scrolling 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 was tested for:

• Skip repetitive navigation links.
• Removal of duplicate links on pages to allow for easier navigation.
• Table headers for widgets such as grids and group boxes.
• Headers for page titles and scroll areas.
• Skip Nav functionality.

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

The default tab order is controlled by the order of the fields in the HTML. However applications can alter this order when they deem necessary.

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.
• Hotkeys/keyboard shortcuts available to skip elements.

The product was tested to ensure that the purpose of delivered links can be understood, its labels are meaningful and that labels are not vaguely worded.

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

• Drop down menu.
• Navigation Menu or Navigation Bar( NavBar)
• Related Actions.
• Links on a page.
• Tiles(buttons) on a homepage.
• Button bars (radio buttons).
• Global Search feature to find a page.
• Favorites.

The product was tested for:

• Structure and hierarchy is conveyed using meaningful text in header elements on PIA and Fluid pages.
• Column and Row headers on data tables.
• Labels describe the purpose of the associated field.

The product was tested for:

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

The product was tested for :

• There are no multipoint or path-based gesture actions

The product was tested for :

• There are no single pointer operations

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.

The product was tested for :

• There are no functions that require motion of the device.

The product was tested for:

• Properly set lang attribute for each Web page.

The product does not support multiple languages on the same 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.

If the application does program substantial changes to the page, PeopleTools provides the ability to issue warnings first.

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.

This product has been tested to ensure a consistent UI.

PeopleTools has some inconsistencies between its classic UI compared to the new Fluid UI available from 8.54 onwards. The entire user experience is different with Fluid pages. A user can navigate between classic PIA and Fluid which can results in an inconsistent UI.

However the Fluid Header and Navigation Bar(NavBar) are available in both classic and Fluid to to help with a consistent UI.

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

This product was tested for meaningful Labels and ALT text.

PeopleTools error messages allow the ability to provide instruction with the error on how a user can resolve the issue.

PeopleTools allow applications the ability to display

• Error messages.
• Confirmation pages where necessary.
• Undo functionality.

PeopleTools provides the flexibility to the application to show these pages when the situation requires it.

This product was tested for:

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

There is one noted exception as follows:

 Bug 24322172 Duplicate ID Violations when Tiles generated with Tile Wizard.

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 product was tested for :

• Status messages are conveyed to assistive technology when there is a change in context.

See the responses in the WCAG 2.0 section of this report.

The product was tested for:

• File conversion preserves accessibility information.    

                  RTF  template format creates HTML accessible file format.

                  RTF template format creates PDF accessible file format.

PeopleTools uses Oracle Business Intelligence Publisher for PDF Export functionality. VPAT for Oracle Business Intelligence Publisher Updated 12.2.4.0 has been linked in the Dependent Products section in this report.

PeopleTools uses BI Publisher as an authoring tool. BI Publisher does not prompt for Level  A and Level AA conformance. This lack of support has been called out in  Oracle Business Intelligence Publisher Updated 12.2.4.0.0 VPAT and is tracked in Bug 26626319 - As an authoring tool BI Publisher does not prompt user to create WCAG2.0 conforming accessible content.

Peopletools delivers templates generated using BI Publisher. BI Publisher does not prompt for Level  A and Level AA conformance. This lack of support has been called out in  Oracle Business Intelligence Publisher Updated 12.2.4.0.0 VPAT and is tracked in Bug 26626319 - As an authoring tool BI Publisher does not prompt user to create WCAG2.0 conforming accessible content

The product documentation includes:

• Documentation on how to use accessibility features
• Documentation on accessibility features that provide compatibility with assistive technology

Product documentation is available in electronic format.