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 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.
Exceptions to the above are as follows: - Two pages were identified where decorative images, used for visual purposes only, had a label. Bug 21920193.
- Fourteen pages were identified where the "ALT text" was not provided for images in a page. Bug 21920396.
- Two pages were identified where images were not noted as such. Bug 21920415.
- Two pages were identified where when the pictures (images) were turned OFF, the "ALT Text" was not shown instead of the image. Bug 21924771.
- Two pages were identified where when the user tabs to a radio button with multiple radio buttons, the screen reader did not read the number of radio buttons. Bug 21924829.
|
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 does not utilize audio-only or prerecorded video-only media. |
| 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 does not utilize prerecorded audio content. |
| 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 does not utilize video synchronized media. |
| 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 does not utilize live audio content. |
| 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 does not utilize prerecorded video content. |
| 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.
- Tables (Grids and Group Boxes) used for layout purposes.
Exceptions to the above are as follows: - Ten pages were identified where not all form fields had a label in the left column. Bug 21924875.
- Three pages were identified where grids had their borders and controls hidden and were not visually a table in standard mode, yet they were identified as a table in accessibility mode. Bug 21924938.
- Twenty-nine pages were identified with improper tables (grids). Bug 21924987.
- Nineteen pages were identified where the labels in the table summary and column headers to did not make sense in accessible mode. Bug 21925011.
- Four pages were identified where the tables identified by the Table Inspector did not appear as a table visually in standard mode. Bug 21925047.
- Eight pages were identified where there were objects that did not look like a heading but were noted as a heading, yet there was no error. Bug 21925072.
- Eight pages were identified where there were objects that looked like a heading but did not get noted as a heading, yet there was no error. Bug 21925103.
- Twelve pages were identified using a screen reader where grid column headings were not available for Add, Delete, Row Number or Row Selection Indicator Columns in a grid. Bug 21925163.
|
| 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 to ensure that the sequence in which content is presented is in a logical tab order.
Exceptions to the above are as follows: - Four pages were identified where items did not appear in a logical order in the flow of the page. Bug 21925219.
|
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. | The product does not use color, shape, size or sound as the only means of conveying content or guidance to the user. This product was tested for sensory characteristics of components such as visual location and orientation.
Exceptions to the above are as follows: - One page was identified where directional text was used and did not provide specific instructions on what the user needed to do. E.g., Instead of text stating "Press the below button" it should state "Press the Continue, Back, Save button below". Bug 21925247.
- Three pages were identified where labels were not close in proximity to the entry field/ field or were they were not on the left of the combo box. Pages were identified where labels were not to the right of a check box for a consistent look and feel. Bug 21925346.
|
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. | The product does not use colors as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
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 does not utilize audio based media. |
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. | The product was tested for visual presentation of text to ensure that a contrast ratio of at least 4.5:1 is applicable. Images of text are not utilized in the product.
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.
Exceptions to the above are as follows: - Eighteen pages were identified where the color contrast analyzer identified issues. Bug 21925384.
|
| 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 up to 200%. |
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 does not utilize images of 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. Hotkeys/keyboard shortcuts are available for certain functions of the product. The product was tested for: - Consistent use of keyboard keys to perform selection and action.
|
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. | 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. |
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 elements do not 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 provides HTML headers which enable the user to bypass blocks of content. Headers are provided for Page Titles, Group Boxes, Scroll Areas, and Grids (Tables) |
| 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. | The product was tested for meaningful titles that describe the topic or purpose of the web page.
Exceptions to the above are as follows: - Forty-four pages were identified where the title was not considered meaningful. Bug 21925406.
|
| 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 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:
- One page was identified where the tab order in accessibility mode was not the same as in standard mode. Bug 21925424.
- Seven pages were identified where the tab order was not in a logical form (e.g., top down or left to right and in sequence). Bug 21925466.
- Five pages were identified where page objects were not ordered by tab order. Bug 21925466.
|
| 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 each link can be understood, its label is meaningful, and that labels are not vaguely worded.
Exceptions to the above are as follows: - Ten pages were identified where the mouse over text for a button did not convey a consistent meaning. Bug 21925513.
- Six pages were identified where the mouse over text for links and images did not convey a consistent meaning. Bug 21925604.
- Four pages were identified where the label did not appropriately describe the purpose for a link. Bug 21925619.
- One page was identified where there were objects that looked like links but were not noted as such, yet there was no error. Bug 21925910.
|
| 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 methods to navigate to a page including: - Drop down menu.
- Related 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 conveys meaningful text in header elements on pages.
- Column and Row headers on data tables.
Exceptions to the above are as follows: - Fifteen pages were identified where the label was not appropriate for the control/field. Bug 21925934.
- Twenty-six pages were identified where the page lists were not tagged with the appropriate list titles. Bug 21925965.
- Fourteen pages were identified without the appropriate header information. Bug 21926013.
- Three pages were identified where the row headers did not uniquely identify the row. Bug 21926112.
- Four pages were identified where grid columns did not have labels. Bug 21926214.
- Eight pages were identified where grid boxes and grids did not have titles. Bug 21926258.
|
| 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 cues or feedback to the position of the cursor within the product.
- AT product successfully tracks cursor focus.
|
| 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. | The 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. | The product was tested to ensure the language of the page can be determined. |
| 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. |
| 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. | The product was tested for consistent navigation and order across pages. |
| 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. | The product has been tested to ensure a consistent User Interface.
Exceptions to the above are as follows: - One page was identified where objects within the page did not operate consistently. Bug 21926281.
|
| 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 the identification of 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. | The product was tested for meaningful labels, instructions where applicable, 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. | 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. |
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)
- Reversible: Submissions are reversible.
- Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
- 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. | 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.
|
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. | The application was tested for: - Duplicate IDs in the HTML.
- 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.
Exceptions to the above are as follows: - Ten pages were identified where form fields do not have a unique label. Bug 21926330.
|
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 was tested in accessible mode 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.
|