Oracle Voluntary Product Accessibility Template

Name of Product: PeopleSoft Enterprise PeopleTools 8.55

Last Updated: 30-Oct-2015

This VPAT applies to only version 8.55. It does not apply to any versions of PeopleSoft Enterprise PeopleTools after this.
 This VPAT has been superseded by PeopleSoft Enterprise PeopleTools 8.56

This VPAT applies to the end-user content generated by the PeopleSoft Internet Architecture (PIA) for PeopleTools 8.55 while in Accessible mode. Color contrast, High Contrast and Keyboard functionality have been evaluated in standard mode and in Accessible mode. It describes code generated by PeopleTools which an application developer cannot influence (for example, the basic construct of a grid) as well as code generated when an application is built using PeopleTools and the developer has properly followed all applicable accessibility standards and guidance. PeopleTools 8.55 has been evaluated against the WCAG 2.0 standards.

The administrative functions of PeopleSoft including but not limited to the Application Designer, Data Mover, Change Assistant, PeopleTools Test Framework (PTF), Change Impact Analyzer, and administrative SQR reports delivered with PeopleTools such as the Cross Reference reports, are not accessible products.

The PeopleTools online product – PeopleSoft Update Manager - is currently not accessible. The bug tracking all of the accessibility issues with this product is 21893534.

The PeopleTools online product - Health Center - is currently not accessible. The bug tracking all of the accessibility issues with this product is 21977268.

The reporting tools delivered with PeopleTools, such as BI Publisher, SQR or nVision, are capable of generating code that meets the applicable provisions of WCAG 2.0 when used in accordance with their written documentation. Delivered application SQR and Crystal reports are considered to be samples.  These reports are intended for printing purposes only and therefore are not accessible.  The content contained within these delivered reports may be obtained and viewed through an alternative accessible means such as an online page or query. To create accessible reports, manually create an RTF layout following the guidance in the "Designing Accessible Reports" section of the BI Publisher Report Designer's Guide. HTML is the supported output type for consuming accessible reports. The BI Publisher VPAT has been linked to this VPAT.

Please refer to the PeopleBooks Accessibility guide if you require additional information on the issues discussed in this VPAT.

 

There is a section in the document "Enterprise PeopleTools 8.55 PeopleBook: PeopleSoft Accessibility Guide"  titled "Setting Up PeopleSoft Accessibility Features" that explains the steps to setup accessibility.

Accessibility can also be enabled by the end user on the delivered sign on page.

This document describes the extent to which the product conforms to the Web Content Accessibility Guidelines (WCAG) 2.0 'A' and 'AA' levels as described at http://www.w3.org/TR/WCAG20/, and the applicable U.S. Section 508 standards. We are using a format similar to the Voluntary Product Accessibility Template, or VPAT®. There are three columns in the tables. The first column contains each of the WCAG 2.0 A and AA Success Criteria or Section 508 criteria; the second column indicates whether the product meets the criterion, and the third column contains remarks about the product with regard to the criterion, including known defects, if any.

For more information regarding the accessibility status of this product or other Oracle products, see https://www.oracle.com/accessibility/ or contact: accessible_ww@oracle.com.

 


Note: 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.

Section WCAG Web Content Accessibility Guidelines
Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A)
  • Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.)
  • Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)
  • Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
  • Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.
  • CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
  • Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.
 Product has been developed to conform to this standard subject to the remarks on the right.

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.

 

There are exceptions in the following areas:

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506 contains the details.

     
1.2.1 Audio-only and Video-only (Prerecorded): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: (Level A)

  • Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.

  • Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.

 Product has been developed to conform to this standard subject to the remarks on the right.

The product has no audio or video.
1.2.2 Captions (Prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

The product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

The product has no multimedia.
1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

The product has no multimedia.
1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

The product has no multimedia.
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Column and Row headers on data tables.
  • No information is solely conveyed through the style sheet.

There are exceptions in the following areas:

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with it. Bug 18414506  contains the details.
  • JET Charts - Keyboard only users cannot access the detailed view of a chart. The detailed are being tracked in bug 21105387.


     

 
1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for Logical Tab order.
1.3.3 Sensory Characteristics: Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A)
Note: For requirements related to color, refer to Guideline 1.4.		 Product has been developed to conform to this standard subject to the remarks on the right.

This product does not use color or shapes as the only means of providing information or guidance to the user.
1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A)
Note: This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.		 Product has been developed to conform to this standard subject to the remarks on the right.

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

 
1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A)
Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.		 Product has been developed to conform to this standard subject to the remarks on the right.

The product has no audio controls.
1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA)
  • Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
  • Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
  • Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.
 Product has been developed to conform to this standard subject to the remarks on the right.

An Application release is tied to a specific PeopleTool's stylesheet. The latest stylesheet "Tangerine" and Tangerine Fluid" have been tested to conform to these contrast requirements.

Some areas of the older stylesheets do not meet high contrast mode or color contrast mode.

The colors in these stylesheets can be changed and overridden by customers.

 
1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for browser zoom.

The exception to this is with Fluid pages on Apple IOS where Pinch zoom is disabled. Bug 18907564.
1.4.5 Images of Text: If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA)
  • Customizable: The image of text can be visually customized to the user's requirements;
  • Essential: A particular presentation of text is essential to the information being conveyed.
Note: Logotypes (text that is part of a logo or brand name) are considered essential.		 Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Meaningful icon/image/object identification.
  • Meaningful images have alternative text.
  • Images of text are not used in place of actual text.
2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)
Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.
Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.		 Product has been developed to conform to this standard subject to the remarks on the right.

The product does not disrupt the features related to accessibility on the end users platform.

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.

There are exceptions however for the following issues:

  • JET Charts - Keyboard only users cannot access the detailed view of a chart. The detailed are being tracked in bug 21105387.

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506 contains the details.
2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)
Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.		 Product has been developed to conform to this standard subject to the remarks on the right.

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.
2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A)
  • Turn off: The user is allowed to turn off the time limit before encountering it; or
  • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception: The time limit is essential and extending it would invalidate the activity; or
  • 20 Hour Exception: The time limit is longer than 20 hours.
Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.		 Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Inactivity timeout options to continue or exit.
  • Inactivity timeout length is configurable by the Administrator.
2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)
  • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
  • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Note 1: For requirements related to flickering or flashing content, refer to Guideline 2.3.
Note 2: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
Note 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.
Note 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.		 Product has been developed to conform to this standard subject to the remarks on the right.

This product was tested that any areas we have auto updating areas are marked up with the correct WAI-ARIA tags.
2.3.1 Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A)
Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.		 Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested to ensure that no Elements flash or blink outside of the required thresholds.
2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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.
  • Skip Nav has also been added to this release.

This product provides Headers tags in the HTML of the page to allow users to bypass blocks of contents.
2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

Pages have meaningful page titles specified in the TITLE element.
2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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.

 
2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested to ensure that the purpose of delivered links can be understood and are not vaguely worded.
2.4.5 Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

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

  • Drop down menu.
  • NavBar.
  • Relate Actions.
  • Links on a page.
  • Search feature to find a page.
2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

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.

 

 
2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

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

There is an exception with:

  • JET Charts - Keyboard only users cannot access the detailed view of a chart. The detailed are being tracked in bug 21105387.
3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

This product was tested to ensure the language of the page can be determined.
3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

This product was tested to ensure the language of the page can be determined. The product does not support multiple languages on the same page.
3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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.
3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

This product was tested for consistent navigation and order across pages.

The NavBar is available in both Classic and Fluid to provide a consistent Navigation.

 

 
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

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 in 8.54. 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 NavBar are available in both classic and Fluid to to help with a consistent UI.
3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

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: Labels or instructions are provided when content requires user input. (Level A) Product has been developed to conform to this standard subject to the remarks on the right.

This product was tested for meaningful Labels and Alt text.
3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) Product has been developed to conform to this standard subject to the remarks on the right.

PeopleTools error messages allow the ability to provide instruction with the error on how a user can resolve the issue.
3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA)
  1. Reversible: Submissions are reversible.
  2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
  3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
 Product has been developed to conform to this standard subject to the remarks on the right.

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.
4.1.1 Parsing: In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A)
Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.		 Product has been developed to conform to this standard subject to the remarks on the right.

This product was tested for:

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

 

 

 
4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.		 Product has been developed to conform to this standard subject to the remarks on the right.

The product in Accessible mode 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.

 

There are exceptions where the markup is not correct:

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506 contains the details.
     

back to top
 

Section 1194.21 Software Applications and Operating Systems
Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.21(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. Product has been developed to conform to this standard subject to the remarks on the right.

The product does not disrupt the features related to accessibility on the end users platform.

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.

There are exceptions however for the following issues:

  • JET Charts - Keyboard only users cannot access the detailed view of a chart. The detailed are being tracked in bug 21105387.

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506 contains the details.
1194.21(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. Product has been developed to conform to this standard subject to the remarks on the right.

The product does not disrupt the features related to accessibility on the end users platform.
1194.21(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Visual cue or feedback to the position of the cursor within the product.
  • AT product successfully tracks cursor focus.
  • 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.

There are exceptions where the markup is not correct:

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506 contains the details.
1194.21(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology. When an image represents a program element, the information conveyed by the image must also be available in text. Product has been developed to conform to this standard subject to the remarks on the right.

The product in Accessible mode 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.

 

There are exceptions where the markup is not correct:

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506 contains the details.
1194.21(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. Product has been developed to conform to this standard subject to the remarks on the right.

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 in 8.54. 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 NavBar are available in both classic and Fluid to to help with a consistent UI.

The product was tested for:

  • Meaningful icon/image/object identification.
  • Meaningful images have alternative text.

 
1194.21(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. Not Applicable

The product was tested for:

  • Text is supplied through HTML or injected into the browser DOM; the browser is responsible for exposing such content in a way that is usable by assistive technology on the platform.
1194.21(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Product has been developed to conform to this standard subject to the remarks on the right.

An Application release is tied to a specific PeopleTool's stylesheet. The latest stylesheet "Tangerine" has been tested to conform to these contrast requirements.

Some areas of the older stylesheets do not meet high contrast mode or color contrast mode.

The colors in these stylesheets can be changed and overridden by customers.
1194.21(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. Product has been developed to conform to this standard subject to the remarks on the right.

This product was tested that any areas we have auto updating areas are marked up with the correct WAI-ARIA tags.
1194.21(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Product has been developed to conform to this standard subject to the remarks on the right.

This product does not use color as the only means of providing information.
1194.21(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided. Product has been developed to conform to this standard subject to the remarks on the right.

An Application release is tied to a specific PeopleTool's stylesheet. The latest stylesheet "Tangerine" has been tested to conform to these contrast requirements.

Some areas of the older stylesheets do not meet high contrast mode or color contrast mode.

The colors in these stylesheets can be changed and overridden by customers.
1194.21(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested to ensure that no Elements flash or blink outside of the required thresholds.
1194.21(l) When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Product has been developed to conform to this standard subject to the remarks on the right.

The product in Accessible mode 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.

 

There are exceptions where the markup is not correct:

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506 contains the details.

back to top
 

Section 1194.22 Web-based Internet Information and Applications
Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.22(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). Product has been developed to conform to this standard subject to the remarks on the right.

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.

 

There are exceptions in the following areas:

  • The Fluid landing page drop down is incorrectly marked up as a button, and does not have the correct keyboard operations associated with it. Bug 18414506.

 
1194.22(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Not Applicable

The product has no multimedia.
1194.22(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Product has been developed to conform to this standard subject to the remarks on the right.

PeopleTools was tested to ensure that stylesheet colors are not the only mechanism of conveying meaning.

 
1194.22(d) Documents shall be organized so they are readable without requiring an associated style sheet. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Column and Row headers on data tables.
  • No information is solely conveyed through the style sheet.

There are exceptions in the following areas:

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with it. Bug 18414506  contains the details.
1194.22(e) Redundant text links shall be provided for each active region of a server-side image map. Not Applicable

This product does not use server side image maps.
1194.22(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. Not Applicable

This product does not use client side image maps.
1194.22(g) Row and column headers shall be identified for data tables. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Column and Row headers on data tables.
  • No information is solely conveyed through the style sheet.

There are exceptions in the following areas:

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with it. Bug 18414506 contains the details.
1194.22(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Column and Row headers on data tables.
  • No information is solely conveyed through the style sheet.

There are exceptions in the following areas:

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with it. Bug 18414506  contains the details.
1194.22(i) Frames shall be titled with text that facilitates frame identification and navigation. Product has been developed to conform to this standard subject to the remarks on the right.

The product in Accessible mode 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.

 

There are exceptions where the markup is not correct:

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506 contains the details.
     
1194.22(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested to ensure that no Elements flash or blink outside of the required thresholds.
1194.22(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. Product has been developed to conform to this standard subject to the remarks on the right.

Text–only pages are not necessary because pages have been coded to meet other applicable standards, to the extent indicated.

 
1194.22(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. Product has been developed to conform to this standard subject to the remarks on the right.

This product was tested to verify the page on the browser complies with accessible guidelines whether it came from HTML, JS or CSS.
1194.22(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l). Not Applicable

PeopleTools does not use plug-ins.
1194.22(n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Product has been developed to conform to this standard subject to the remarks on the right.

The product in Accessible mode 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.

 

There are exceptions where the markup is not correct:

  • Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506 contains the details.
     
1194.22(o) A method shall be provided that permits users to skip repetitive navigation links. Product has been developed to conform to this standard subject to the remarks on the right.

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.
  • Skip Nav has also been added to this release.

This product provides Headers tags in the HTML of the page to allow users to bypass blocks of contents.

 
1194.22(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Product has been developed to conform to this standard subject to the remarks on the right.

The product was tested for:

  • Inactivity timeout options to continue or exit.
  • Inactivity timeout length is configurable by the Administrator.

Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) - 1.1, (b) - 1.4, (c) - 2.1, (d) - 6.1, (e) - 1.2, (f) - 9.1, (g) - 5.1, (h) - 5.2, (i) - 12.1, (j) - 7.1, (k) - 11.4.

back to top
 

Section 1194.23 Telecommunications Products
Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.23(a) Telecommunications products or systems which provide a function allowing voice communication and which do not themselves provide a TTY functionality shall provide a standard non-acoustic connection point for TTYs. Microphones shall be capable of being turned on and off to allow the user to intermix speech with TTY use. Not Applicable  
1194.23(b) Telecommunications products which include voice communication functionality shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols. Not Applicable  
1194.23(c) Voice mail, auto-attendant, and interactive voice response telecommunications systems shall be usable by TTY users with their TTYs. Not Applicable  
1194.23(d) Voice mail, messaging, auto-attendant, and interactive voice response telecommunications systems that require a response from a user within a time interval, shall give an alert when the time interval is about to run out, and shall provide sufficient time for the user to indicate more time is required. Not Applicable  
1194.23(e) Where provided, caller identification and similar telecommunications functions shall also be available for users of TTYs, and for users who cannot see displays. Not Applicable  
1194.23(f) For transmitted voice signals, telecommunications products shall provide a gain adjustable up to a minimum of 20 dB. For incremental volume control, at least one intermediate step of 12 dB of gain shall be provided. Not Applicable  
1194.23(g) If the telecommunications product allows a user to adjust the receive volume, a function shall be provided to automatically reset the volume to the default level after every use. Not Applicable  
1194.23(h) Where a telecommunications product delivers output by an audio transducer which is normally held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided. Not Applicable  
1194.23(i) Interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) shall be reduced to the lowest possible level that allows a user of hearing technologies to utilize the telecommunications product. Not Applicable  
1194.23(j) Products that transmit or conduct information or communication, shall pass through cross-manufacturer, non-proprietary, industry-standard codes, translation protocols, formats or other information necessary to provide the information or communication in a usable format. Technologies which use encoding, signal compression, format transformation, or similar techniques shall not remove information needed for access or shall restore it upon delivery. Not Applicable  
1194.23(k)(1) For products which have mechanically operated controls or keys, controls and keys shall be tactilely discernible without activating the controls or keys. Not Applicable  
1194.23(k)(2) For products which have mechanically operated controls or keys, controls do not require tight grasping, pinching or twisting of the wrist to operate. Not Applicable  
1194.23(k)(3) If key repeat is supported, the delay before repeat shall be adjustable to at least 2 seconds. Key repeat rate shall be adjustable to 2 seconds per character. Not Applicable  
1194.23(k)(4) The status of all locking or toggle controls or keys shall be visually discernible, and discernible either through touch or sound. Not Applicable  

back to top
 

Section 1194.24 Video and Multimedia Products
Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.24(a) All analog television displays 13 inches and larger, and computer equipment that includes analog television receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals. As soon as practicable, but not later than July 1, 2002, widescreen digital television (DTV) displays measuring at least 7.8 inches vertically, DTV sets with conventional displays measuring at least 13 inches vertically, and stand-alone DTV tuners, whether or not they are marketed with display screens, and computer equipment that includes DTV receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals. Not Applicable  
1194.24(b) Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry. Not Applicable  
1194.24(c) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain speech or other audio information necessary for the comprehension of the content, shall be open or closed captioned. Not Applicable  
1194.24(d) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain visual information necessary for the comprehension of the content, shall be audio described. Not Applicable  
1194.24(e) Display or presentation of alternate text presentation or audio descriptions shall be user-selectable unless permanent. Not Applicable  

back to top
 

Section 1194.25 Self Contained, Closed Products
Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.25(a) Self contained products shall be usable by people with disabilities without requiring an end-user to attach assistive technology to the product. Personal headsets for private listening are not assistive technology. Not Applicable  
1194.25(b) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not Applicable  
1194.25(c) Where a product utilizes touchscreens or contact-sensitive controls, an input method shall be provided that complies with Section 1194.23 (k) (1) through (4). Not Applicable  
1194.25(d) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided. Not Applicable  
1194.25(e) When products provide auditory output, the audio signal shall be provided at a standard signal level through an industry standard connector that will allow for private listening. The product must provide the ability to interrupt, pause, and restart the audio at anytime. Not Applicable  
1194.25(f) When products deliver voice output in a public area, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. Where the ambient noise level of the environment is above 45 dB, a volume gain of at least 20 dB above the ambient level shall be user selectable. A function shall be provided to automatically reset the volume to the default level after every use. Not Applicable  
1194.25(g) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Not Applicable  
1194.25(h) When a product permits a user to adjust color and contrast settings, a range of color selections capable of producing a variety of contrast levels shall be provided. Not Applicable  
1194.25(i) Products shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Not Applicable  
1194.25(j)(1) The position of any operable control shall be determined with respect to a vertical plane, which is 48 inches in length, centered on the operable control, and at the maximum protrusion of the product within the 48 inch length on products which are freestanding, non-portable, and intended to be used in one location and which have operable controls. Not Applicable  
1194.25(j)(2) Where any operable control is 10 inches or less behind the reference plane, the height shall be 54 inches maximum and 15 inches minimum above the floor. Not Applicable  
1194.25(j)(3) Where any operable control is more than 10 inches and not more than 24 inches behind the reference plane, the height shall be 46 inches maximum and 15 inches minimum above the floor. Not Applicable  
1194.25(j)(4) Operable controls shall not be more than 24 inches behind the reference plane. Not Applicable  

back to top
 

Section 1194.26 Desktop and Portable Computers
Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.26(a) All mechanically operated controls and keys shall comply with Section 1194.23 (k) (1) through (4). Not Applicable  
1194.26(b) If a product utilizes touchscreens or touch-operated controls, an input method shall be provided that complies with Section 1194.23 (k) (1) through (4). Not Applicable  
1194.26(c) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided. Not Applicable  
1194.26(d) Where provided, at least one of each type of expansion slots, ports and connectors shall comply with publicly available industry standards. Not Applicable  

back to top
 

Section 1194.31 Functional Performance Criteria
Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.31(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards.
 
1194.31(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for assistive technology used by people who are visually impaired shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for assistive technology used by people who are deaf or hard of hearing shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for assistive technology used by people with disabilities shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 
1194.31(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. Yes Subject to the information provided in this document, this product has been developed to conform to the applicable technical provisions of the 508 standards. 

back to top
 

Section 1194.41 Information, Documentation and Support
Criteria
Supporting Features
Remarks (e.g., definition, equivalent facilitation, scope of support provided)
1194.41(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. Documentation for this product is available in accessible electronic format.

PeopleBooks is in an Accessible HTML format.
1194.41(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. Documentation for this product is available in accessible electronic format.  
1194.41(c) Support services for products shall accommodate the communication needs of end-users with disabilities. 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 http://www.fcc.gov/cgb/dro/trsphonebk.html. 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
 

Dependent Products


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

 

back to top