This is the IBM Accessibility Checklist for Web and Web-Based Documentation - Version 6.1. It replaced IBM Web Accessibility Checklist 5.2 on August 25, 2016.
This checklist and its checkpoint pages position IBM web products in preparation for the US Section 508 Refresh, while still ensuring compliance with existing 508 requirements. IBM teams should comply with all of the checkpoints as soon as possible. Review the last section on this page, Using the IBM Accessibility Checklist, for more information.
The Summary of Changes lists all substantial modifications to this checklist since its release.
*N/A for most non-web Software = Applies to web applications but not to most non-web Software
IBM Accessibility Checklist v1.0 for Web IBM Accessibility Checklist v1.0 for Software IBM Accessibility Checklist v1.0 for DocumentationWCAG 2.0 Checkpoints
Principle 1: Perceivable - Information and user interface components must be presentable to users in ways they can perceive. |
Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. |
|
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. (Level A) Disability Type: blind, deaf, hard of hearing, low vision A11y v1.0: 1.1.1-1 508 508 WCAG 2.0 A, 508R CI 162 Non-text content has text alternatives All non-text content that is presented to the user has a text alternative that serves the equivalent purpose. Non-text content has text alternatives except... All non-text content that is presented to the user has a text alternative that serves the equivalent purpose except List what fails in customer understandable terms. Non-text content does not have text alternatives Text alternatives are not provided for all visible non-text content. No images No images. |
Guideline 1.2 Time-based Media: Provide alternatives for time-based media. |
|
1.2.1 Audio-only and Video-only (Prerecorded). For prerecorded audio-only or video-only media, an alternative provides equivalent information. (Level A) Disability Type: blind, deaf, hard of hearing, low vision A11y v1.0: 1.2.1-1 508 508 508 508 WCAG 2.0 A, 508R WCAG 2.0 A, 508R CI 162 Alternative content is provided. 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. Alternative content is provided except 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 except List what fails in customer understandable terms. Alternative content is not provided Alternative content is not provided for time-based media and prerecorded video content. No time-based media No time-based media or prerecorded video. |
|
1.2.2 Captions (Prerecorded). Captions are provided for all prerecorded audio content in synchronized media. (Level A) Disability Type: deaf, hard of hearing A11y v1.0: 1.2.2-1 508 508 508 508 WCAG 2.0 A, 508R CI 162 Captions are provided Captions are provided for prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. Captions are provided except... Captions are provided for prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such, except List what fails in customer understandable terms. Captions are not provided Captions are not provided for prerecorded audio content. No prerecorded audio No prerecorded audio. |
|
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. (Level A) Disability Type: blind, low vision A11y v1.0: 1.2.3-1 508 508 508 508 WCAG 2.0 A, 508R WCAG 2.0 A, 508R CI 162 Alternative content is provided 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. Alternative content is provided except 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 except List what fails in customer understandable terms. Alternative content is not provided Alternative content is not provided for time-based media and prerecorded video content. No time-based media No time-based media or prerecorded video. |
|
1.2.4 Captions (Live). Captions are provided for all live audio content in synchronized media. (Level AA) Disability Type: deaf, hard of hearing A11y v1.0: 1.2.4-1 508 508 508 WCAG 2.0 AA, 508R CI 162 Captions are provided Captions are provided for live multimedia. Captions are provided except... Captions for live multimedia are provided on all multimedia, except List what fails in customer understandable terms. Captions are not provided Captions are not provided for live multimedia. No live multimedia No live multimedia. |
|
1.2.5 Audio Description (Prerecorded). Audio description is provided for all prerecorded video content in synchronized media. (Level AA) Disability Type: blind, low vision A11y v1.0: 1.2.5-1 WCAG 2.0 AA, 508R Audio description is provided Audio description is provided for all prerecorded video content in synchronized media. Audio description is provided except... Audio description is provided for all prerecorded video content in synchronized media is provided on all pages, except List what fails in customer understandable terms. Audio description is not provided Audio description is not provided for prerecorded video. No time-based media No time-based media or prerecorded video. |
Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure. |
|
1.3.1 Info and Relationships. Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) Disability Type: blind A11y v1.0: 1.3.1-1 WCAG 2.0 A, 508R CI 162 Can be programmatically determined Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. Can be programmatically determined except... Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text on all pages, except List what fails in customer understandable terms. Can not be programmatically determined Information, structure, and relationships can not be programmatically determined or are not provided in text. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
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) Disability Type: blind A11y v1.0: 1.3.2-1 WCAG 2.0 A, 508R CI 162 Sequence programmatically determined When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. Sequence programmatically determined except... When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined on all pages, except List what fails in customer understandable terms. Sequence can not be programmatically determined When the sequence in which content is presented affects its meaning, a correct reading sequence can not be programmatically determined on all pages. Sequence does not affect meaning Presentation sequence does not affect meaning. |
|
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) Disability Type: blind, deaf, hard of hearing, low vision A11y v1.0: 1.3.3-1 WCAG 2.0 A, 508R CI 162 Instructions do not rely on 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. Instructions do not rely on sensory characteristics except... 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 except List what fails in customer understandable terms. Instructions rely on sensory characteristics Instructions rely solely on sensory characteristics. Not a valid response This checkpoint status should not be N/A. Select another status. |
Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background. |
|
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) Disability Type: blind, low vision A11y v1.0: 1.4.1-1 508 508 WCAG 2.0 A, 508R CI 162 Color is not used as the only visual means Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Color is not used as the only visual means except... Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element is provided on all pages, except List what fails in customer understandable terms. Color is the only visual means Color is the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
1.4.2 Audio Control. If any audio 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) Disability Type: blind, hard of hearing A11y v1.0: 1.4.2-1 WCAG 2.0 A, 508R CI 162 Mechanism is available to control the audio 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. Mechanism is available to control the audio except... 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 is provided on all pages, except List what fails in customer understandable terms. Pause or stop controls are not provided Pause or stop controls are not provided when a web page plays automatically and a mechanism is not provided for controlling audio volume independently from overall system volume levels. No audio No audio. |
|
1.4.3 Contrast (Minimum). The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, with a 3:1 ratio for large-scale text. (Level AA) Disability Type: low vision A11y v1.0: 1.4.3-1 WCAG 2.0 AA, 508R Has a contrast ratio of at least 4.5:1 The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for large print and images of large print, which must have a contrast ratio of 3:1. Has a contrast ratio of at least 4.5:1 except... The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for large print and images of large print, which must have a contrast ratio of 3:1 is provided on all pages, except List what fails in customer understandable terms. Does not have a contrast ratio of at least 4.5:1 Visual presentation of text and images of test does not have a contrast ratio of at least 4.5:1. Large print and images of large print do not have a contrast ration of 3:1. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
1.4.4 Resize text. Text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA) Disability Type: low vision A11y v1.0: 1.4.4-1 WCAG 2.0 AA, 508R Text can be resized Text (but not images of text) can be resized without assistive technology up to 200 percent without loss of content or functionality. Text can be resized except... Text (but not images of text) can be resized without assistive technology up to 200 percent without loss of content or functionality on all pages, except List what fails in customer understandable terms.>. Text can not be resized Text (excluding images of text) can not be resized without assistive technology up to 200 percent without loss of content or functionality. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
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. (Level AA) Disability Type: blind, low vision A11y v1.0: 1.4.5-1 WCAG 2.0 AA, 508R Text is used Text is used to convey information rather than images. An image of text may be used when it is essential to the information being conveyed and the image can be visually customized to the user's requirements. Test is used, except... Text is used to convey information rather than images on all pages, except List what fails in customer understandable terms. Text is not used Text is not used to convey information represented as images. Not a valid response This checkpoint status should not be N/A. Select another status. |
Principle 2: Operable - User interface components and navigation must be operable. |
Guideline 2.1 Keyboard Accessible: Make all functionality available from a keyboard. |
|
2.1.1 Keyboard. All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level A) Disability Type: blind, low vision, physical disability A11y v1.0: 2.1.1-1 WCAG 2.0 A, 508R CI 162 All content is not operable through a 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. All content is operable through a keyboard except... 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 is provided on all pages, except List what fails in customer understandable terms. All content is not operable through a keyboard All functionality of the content is not operable through a keyboard interface. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
2.1.2 No Keyboard Trap. If keyboard focus can be moved to a component 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) Disability Type: blind, low vision, physical disability A11y v1.0: 2.1.2-1 WCAG 2.0 A, 508R CI 162 No keyboard traps If 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, the user is advised of the method for moving focus away. No keyboard traps except... Focus can be moved away from components using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys, the user is advised of the method for moving focus away, except List what fails in customer understandable terms. Contains keyboard traps The current behavior contains keyboard traps. Not a valid response This checkpoint status should not be N/A. Select another status. |
Guideline 2.2 Enough Time: Provide users enough time to read and use content. |
|
2.2.1 Timing Adjustable. For each time limit that is set by the content, the user can turn off, adjust, or extend the limit. (Level A) Disability Type: blind, deaf, hard of hearing, low vision, physical disability A11y v1.0: 2.2.1-1 508 508 508 WCAG 2.0 A, 508R CI 162 User allowed to adjust time limits The user is allowed to turn off, adjust or extend all time limits that are not a real-time, essential or 20 hour exception. User allowed to adjust time limits except... The user is allowed to turn off, adjust or extend all time limits that are not a real-time, essential or 20 hour exception, except List what fails in customer understandable terms. User unable to adjust time limits Except for real-time, essential or 20 hour exception, the user is unable to turn off, adjust, or extend time limits before encountering it. No time limits No time limits. |
|
2.2.2 Pause, Stop, Hide. For moving, blinking, scrolling, or auto-updating information, the user can pause, stop, hide, or adjust the information. (Level A) Disability Type: blind, low vision, deaf, hard of hearing, physical disability A11y v1.0: 2.2.2-1 WCAG 2.0 A, 508R CI 162 The user can control moving, blinking, etc. The user is allowed to pause, stop, or hide moving, blinking, scrolling, or auto-updating information unless it is an essential part of an activity. The user can control moving, blinking, etc. except... The user is allowed to pause, stop, or hide moving, blinking, scrolling, or auto-updating information on all pages, except List what fails in customer understandable terms. Unable to control moving, blinking, etc. The user is unable to control any moving, blinking or scrolling content which starts automatically. No moving, blinking, etc. No moving, blinking, scrolling, or auto-updating. |
Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures. |
|
2.3.1 Three Flashes or Below Threshold. Content does 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) Disability Type: photosensitive epilepsy A11y v1.0: 2.3.1-1 508 508 WCAG 2.0 A, 508R CI 162 Web pages do not contain flashing or blinking Web pages do not contain anything that flashes more than three times in any one second period. Web pages do not contain flashing or blinking except... Web pages do not contain anything that flashes more than three times in any one second period except List what fails in customer understandable terms. Web pages contain flashing or blinking Web pages contain flashing or blinking text, objects, or other elements that flash more than three times in any one second period. Not a valid response This checkpoint status should not be N/A. Select another status. |
Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are. |
|
2.4.1 Bypass Blocks. A mechanism is available to bypass blocks of content that are repeated on multiple Web pages, or in sets of documents or software programs. (Level A) *N/A for non-web documents and software Disability Type: blind, low vision, physical disability A11y v1.0: 2.4.1-1 WCAG 2.0 A, 508R CI 162 A mechanism is available to bypass blocks A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. Note: This product uses WAI-ARIA to comply with this checkpoint. WAI-ARIA has been supported since Firefox 3.6 and JAWS 12. A mechanism is available to bypass blocks except... A mechanism is available to bypass blocks of content repeated on multiple Web pages, except List what fails in customer understandable terms. No method for skipping to main content There is no method for skipping to main content or bypassing any blocks of content repeated on multiple Web pages. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
2.4.2 Page Titled. Web pages, non-web documents, and software have titles that describe topic or purpose. (Level A) Disability Type: blind, low vision A11y v1.0: 2.4.2-1 WCAG 2.0 A, 508R CI 162 Web pages have titles Web pages have titles that describe topic or purpose. Web pages have titles except... Web pages have titles that describe topic or purpose, except List what fails in customer understandable terms. Web pages do not provide titles Web pages do not provide titles that describe the topic or purpose. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
2.4.3 Focus Order. If content 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) Disability Type: blind, low vision, physical disability A11y v1.0: 2.4.3-1 WCAG 2.0 A, 508R CI 162 Focusable components receive focus Focusable components receive focus in an order that preserves meaning and operability. Focusable components receive focus except... Focusable components receive focus in an order that preserves meaning and operability on all pages, except List what fails in customer understandable terms. Focus is not provided Focus is not provided on focusable components in an order that preserves meaning and operability. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
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. (Level A) Disability Type: blind, low vision A11y v1.0: 2.4.4-1 WCAG 2.0 A, 508R CI 162 Link purpose can be determined 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. Link purpose can be determined except... 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 works on all pages, except List what fails in customer understandable terms. Link purpose can not be determined Except where the purpose of the link would be ambiguous to users in general, the purpose of each link can not be determined. No links No links. |
|
2.4.5 Multiple Ways. More than one way is available to locate an item in a set of items, whether it is a Web page within a set of Web pages, a document within a set of non-web documents, or a program within a set of software programs. (Level AA) *N/A for non-web documents and software Disability Type: blind, low vision, physical disability A11y v1.0: 2.4.5-1 WCAG 2.0 AA, 508R More then one way to locate a Web page 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. More then one way to locate a Web page except... 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. List what fails in customer understandable terms. Only one way to locate a Web page Except where the Web Page is the result of, or a step in a process, only one way is available to locate a Web page within a set of Web pages. This is a single page web application This is a single page web application. All web pages are step in process All web application pages are the result of, or a step in, a process. |
|
2.4.6 Headings and Labels. Headings and labels describe topic or purpose. (Level AA) Disability Type: blind, low vision A11y v1.0: 2.4.6-1 WCAG 2.0 AA, 508R Headings and labels provided Headings and labels describe topic or purpose. Headings and labels provided except... Headings and labels describe topic or purpose on all pages, except List what fails in customer understandable terms. No headings and descriptive labels Headings and descriptive labels are not provided. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
2.4.7 Focus Visible. Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) Disability Type: low vision, physical disability A11y v1.0: 2.4.7-1 WCAG 2.0 AA, 508R Focus indicator is visible Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. Focus indicator is visible except... Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible except List what fails in customer understandable terms. Focus indicator is not provided A visible keyboard focus indicator is not provided. Not a valid response This checkpoint status should not be N/A. Select another status. |
Principle 3: Understandable - Information and the operation of user interface must be understandable. |
Guideline 3.1 Readable: Make content readable and understandable. |
|
3.1.1 Language of Page. The default human language of Web pages, non-Web documents, or software can be programmatically determined. (Level A) Disability Type: blind A11y v1.0: 3.1.1-1 WCAG 2.0 A, 508R CI 162 Default language can be determined The default human language of each Web page can be programmatically determined. Default language can be determined except... The default human language of each Web page can be programmatically determined, except List what fails in customer understandable terms. Default language can not be determined The default human language of each Web page can not be programmatically determined. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
3.1.2 Language of Parts. The human language of each passage or phrase in the content can be programmatically determined. (Level AA) Disability Type: blind A11y v1.0: 3.1.2-1 WCAG 2.0 AA, 508R Language in the content can be determined 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. It is assumed that users will interact with this product as a single language document therefore the default human language of the web page, which can be programmatically determined, satisfies this requirement. Language in the content can be determined except... 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 except List what fails in customer understandable terms. Language in the content can not be 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, the human language of each passage or phrase can not be programmatically determined. Not a valid response This checkpoint status should not be N/A. Select another status. |
Guideline 3.2 Predictable: Make content appear and operate in predictable ways. |
|
3.2.1 On Focus. When any component receives focus, it does not initiate a change of context. (Level A) Disability Type: blind, low vision, physical disability A11y v1.0: 3.2.1-1 WCAG 2.0 A, 508R CI 162 Focus does not causes a change of context When any component receives focus, it does not initiate a change of context. Focus does not causes a change of context except... When any component receives focus, it does not initiate a change of context, except List what fails in customer understandable terms. Focus causes a change of context When any component receives focus, the page initiates a change of context. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
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) Disability Type: blind, low vision, physical disability A11y v1.0: 3.2.2-1 WCAG 2.0 A, 508R CI 162 UI settings do not change context 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. UI settings do not change context except... 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, except List what fails in customer understandable terms. UI settings change context The user is not advised, beforehand, that when changing the setting of any user interface component, the page automatically causes a change of context. No input allowed No input allowed. |
|
3.2.3 Consistent Navigation. Navigational mechanisms that are repeated throughout content occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA) *N/A for non-web documents and software Disability Type: blind, low vision A11y v1.0: 3.2.3-1 WCAG 2.0 AA, 508R navigational mechanisms occur in the same order 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. navigational mechanisms occur in the same order except... 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 is provided on all pages, except List what fails in customer understandable terms. navigational mechanisms do not occur in the same order Unless a change is initiated by the user, navigational mechanisms repeated on multiple web pages do not occur in the same relative order. No navigational mechanisms used No navigational mechanisms used. |
|
3.2.4 Consistent Identification. Components that have the same functionality within a set of content are identified consistently. (Level AA) *N/A for non-web documents and software Disability Type: blind, low vision A11y v1.0: 3.2.4-1 WCAG 2.0 AA, 508R Web page components identified consistently Components that have the same functionality within a set of Web pages are identified consistently. Web page components identified consistently except... Components that have the same functionality within a set of Web pages are identified consistently, except List what fails in customer understandable terms. Web page components not identified consistently Components that have the same functionality within a set of Web pages are not identified consistently. Not a valid response This checkpoint status should not be N/A. Select another status. |
Guideline 3.3 Input Assistance: Help users avoid and correct mistakes. |
|
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) Disability Type: blind, low vision A11y v1.0: 3.3.1-1 WCAG 2.0 A, 508R CI 162 Detected errors are identified and described 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. Note: This product uses WAI-ARIA to comply with this checkpoint. WAI-ARIA has been supported since Firefox 3.6 and JAWS 12. Detected errors are not identified and described except... Input errors are automatically detected, and the item that is in error is identified and the error is described to the user in text on all pages, except List what fails in customer understandable terms. Detected errors are not identified and described Automatically detected errors are not identified and described to the user in text. No input allowed No input allowed. Input errors are not automatically detected Input errors are not automatically detected. |
|
3.3.2 Labels or Instructions. Labels or instructions are provided when content requires user input. (Level A) Disability Type: blind, low vision, physical disability A11y v1.0: 3.3.2-1 WCAG 2.0 A, 508R CI 162 Labels or instructions are provided Labels or instructions are provided when content requires user input. Labels or instructions are provided except... Labels or instructions are provided when content requires user input on all pages, except List what fails in customer understandable terms Labels or instructions are not provided Labels or instructions are not provided when content requires user input. No input allowed No input allowed. |
|
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) Disability Type: blind, low vision, physical disability A11y v1.0: 3.3.3-1 WCAG 2.0 AA, 508R Input errors detected 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. Note: This product uses WAI-ARIA to comply with this checkpoint. WAI-ARIA has been supported since Firefox 3.6 and JAWS 12. Input errors detected except... 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 except List what fails in customer understandable terms. Input errors not detected Except for input errors that would jeopardize the security or purpose of the content, suggestions are not provided to the user when input errors are automatically detected and suggestions for correction are known. No input allowed No input allowed. Input errors are not detected Input errors are not automatically detected. |
|
3.3.4 Error Prevention (Legal, Financial, Data). For content that causes 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, the user can reverse, correct, or confirm the action. (Level AA) Disability Type: blind, low vision, physical disability A11y v1.0: 3.3.4-1 WCAG 2.0 AA, 508R Not used for legal or financial, can reverse Web pages are not used for legal commitments or financial transactions, or submit user test responses. Web pages that modify or delete user-controllable data in a data storage system allow the user to reverse the submission Not used for legal or financial, can correct Web pages are not used for legal commitments or financial transactions, or submit user test responses. Web pages that modify or delete user-controllable data in a data storage system are checked for input errors and provide the user with the ability to correct input before submission. Not used for legal or financial, can review and correct Web pages are not used for legal commitments or financial transactions, or submit user test responses. Web pages that modify or delete user-controllable data in a data storage system allow the user to review, confirm and correct information before finalizing the submission. Used for legal or financial, can correct except... Web pages that modify or delete user-controlled data in a storage system are checked for input errors and provide the user with the ability to correct information before submission or reverse the submission on all pages, except List what fails in customer understandable terms. Web pages are not used for legal commitments or financial transactions, or to submit test responses. Error prevention not provided for legal or financial Error prevention is not provided when web pages are used for legal commitments or financial transactions, to modify user-controlled data in a storage system or to submit test responses. No pages used for legal or financial No pages are used for legal commitments or financial transactions, to modify user-controlled data in a storage system or to submit test responses. |
Principle 4: Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. |
Guideline 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies. |
|
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) Disability Type: blind, low vision, physical disability A11y v1.0: 4.1.1-1 WCAG 2.0 A, 508R CI 162 Content implemented correctly using markup languages 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. Content implemented correctly using markup languages except... 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 is valid on all pages, except List what fails in customer understandable terms. Markup not provided for accessibility Markup language is not provided for accessibility. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
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) Disability Type: blind, low vision, physical disability A11y v1.0: 4.1.2-1 WCAG 2.0 A, 508R CI 162 Name, Role, Value programmatically determined 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. Note: This product uses WAI-ARIA to comply with this checkpoint. WAI-ARIA has been supported since Firefox 3.6 and JAWS 12. Name, Role, Value programmatically determined except... 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 on all pages, except List what fails in customer understandable terms. Name, Role, Value not programmatically determined Name, Role, and Value can not be programmatically determined. Not a valid response This checkpoint status should not be N/A. Select another status. |
|
4.1.3 Accessibility-supported technologies only. Use accessibility supported technologies. Any information or functionality that is implemented in technologies that are not accessibility supported must also be available via technologies that are accessibility supported. Disability Type: blind, low vision, physical disability |
Legacy Non-WCAG 508 Checkpoints
These checkpoints represent 508 requirements that are not covered by WCAG techniques and need to be tested for all teams. Links in this section previously pointed to legacy 5.2 checkpoints, and have been removed.
|
1.1c Image Maps. Client-side image maps are used and alternative text is provided for image map hot spots. Equivalent text links are provided if a server-side image map is used. Disability type: blind |
|
1.3f Cascading style sheets. Web pages are readable without requiring style sheets. Disability type: blind, low vision |
|
4.2a Text-only page. If accessibility cannot be accomplished in any other way, a text-only page with equivalent information or functionality is provided. Disability type: blind |
Legacy 508 Web Checkpoints
These checkpoints represent Section 508 requirements that are subsets of WCAG requirements. If teams pass all WCAG checkpoints, the following can all be reported as compliant. Links in this section previously pointed to legacy 5.2 checkpoints, and have been removed.
|
1.3d Forms. Form element labels can be programmatically determined. Disability Type: blind |
|
1.3e Tables. Table cells and relationships between cells can be programmatically determined. Disability Type: blind |
|
2.1b Scripts. Scripts are keyboard accessible. If the content affected by scripting is not accessible, an alternative is provided. Disability Type: blind, low vision, physical disability |
|
2.1c Applets, plug-ins, and non-HTML content. A link is provided to a directly accessible applet, plug-in or other application. Alternate content is provided for those applets, plug-ins or other applications that are not directly accessible. Disability Type: blind, low vision, physical disability |
|
2.4c Frames. A title and an accessible frame source are provided for each frame. Disability Type: blind |
508 Web Documentation Checkpoints
This checkpoint is for reporting Section 508 documentation requirements. It is only applicable when carrying out web-based documentation testing.
|
602.2 Accessibility and Compatibility Features. Documentation lists and explains accessibility and compatibility features, including keyboard access. Disability Type: blind, deaf, hard of hearing, low vision, physical disability A11y v1.0: 602.2-1 508 508 508R CI 162 YES PLACEHOLDER TITLE YES PLACEHOLDER COMMENT NO PLACEHOLDER TITLE NO PLACEHOLDER COMMENT NA PLACEHOLDER TITLE NA PLACEHOLDER COMMENT |
Using the IBM Accessibility Checklist
Checkpoints are divided into sections that match the standards they reflect or enforce.
WCAG A & AA Checkpoints
A key part of the draft Section 508 Refresh guidelines is that, whether Web, Software or Documentation, user interface components and content of platforms and applications shall conform to Level A and Level AA Success Criteria and Conformance Requirements specified for web pages in WCAG 2.0.
Applications may be web-based or client-side software. Examples of applications are email clients, word processors, help desk systems, content management systems, and e-learning courseware. There will be some additional notes in the rationales or general techniques of some checkpoints on how to apply WCAG 2.0 to non-web software, or if a checkpoint does not apply to software. These software notes can be disregarded by web development teams.
For web teams, little has changed in requirements between the previous checklist and 6.1. Teams migrating from the 5.2 checklist should review the WCAG 2.0 section of Checklist 6.1 to 5.2 Comparison and Impact Analysis for further guidance.
Legacy Non-WCAG 508 Checkpoints
This section encompasses a few existing 508 web requirements which have no equivalent with WCAG checkpoints. By isolating these requirements, teams are able to accurately report compliance with 508 while reporting related WCAG compliance separately. See the Legacy Non-WCAG 508 to 5.2 checkpoint comparison section of the Checklist 6.1 to 5.2 Comparison and Impact Analysis page for information on completion.
Legacy 508 Web Checkpoints
This section encompasses a few existing 508 web requirements which do not match precisely with WCAG checkpoints. By isolating these requirements, teams that do not fully meet WCAG standards are able to accurately report compliance with 508 while reporting related WCAG compliance separately. See the Legacy 508 Web to 5.2 checkpoint comparison section of the Checklist 6.1 to 5.2 Comparison and Impact Analysis page for guidance.
508 Web Documentation Checkpoint
The section has a single checkpoint on documentation (using the 508 Refresh numbering).
Many links in this checklist reside outside ibm.com at the Web Content Accessibility Guidelines (WCAG) 2.1. W3C Recommendation 05 June 2018: http://www.w3.org/TR/WCAG21/
Copyright © 1994-2019 World Wide Web Consortium, (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University, Beihang University). All Rights Reserved.
Copyright © 2001, 2019 IBM Corporation