smartrobbie
Support
Book A Call
smartrobbie
Book A Call

Web Content Accessibility Checklist

Abstract

This document is an appendix to the W3C “Web Content Accessibility Guidelines 1.0”. It provides a list of all checkpoints from the Web Content Accessibility Guidelines 1.0, organized by concept, as a checklist for Web content developers. Please refer to the Guidelines document for introductory information, information about related documents, a glossary of terms, and more.

This list may be used to review a page or site for accessibility. For each checkpoint, indicate whether the checkpoint has been satisfied, has not been satisfied, or is not applicable.

A list version of the checkpoints is also available.

This document has been produced as part of the Web Accessibility Initiative. The goal of the WAI Web Content Guidelines Working Group is discussed in the Working Group charter.

Abstract

This document is an appendix to a document that has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. This is a stable document and may be used as reference material or cited as a normative reference from another document. W3C’s role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and universality of the Web.

A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR.

This document has been produced as part of the Web Accessibility Initiative. The goal of the Web Content Guidelines Working Group is discussed in the Working Group charter.

Priorities

Each checkpoint has a priority level assigned by the Working Group based on the checkpoint’s impact on accessibility.

[Priority 1]
A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents.
[Priority 2]
A Web content developer should satisfy this checkpoint. Otherwise, one or more groups will find it difficult to access information in the document. Satisfying this checkpoint will remove significant barriers to accessing Web documents.
[Priority 3]
A Web content developer may address this checkpoint. Otherwise, one or more groups will find it somewhat difficult to access information in the document. Satisfying this checkpoint will improve access to Web documents.

Some checkpoints specify a priority level that may change under certain (indicated) conditions.

1Priority 1 Checkpoints
2Priority 2 Checkpoints
3Priority 3 Checkpoints

In General (Priority 1)

1.1) Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representation of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
2.1) Ensure that all information conveyed with color is also available without color, for example from context or markup.
4.1) Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions)
6.1) Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.
6.2) Ensure that equivalents for dynamic content are updated when the dynamic content changes.
7.1) Until user agents allow users to control flickering, avoid causing the screen to flicker.
14.1) Use the clearest and simplest language appropriate for a site's content.

And if you use images and image maps (Priority 1)

1.2) Provide redundant text links for each active region of a server-side image map.
9.1) Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

And if you use tables (Priority 1)

5.1) For data tables, identify row and column headers.
5.2) For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.

And if you use frames (Priority 1)

12.1) Title each frame to facilitate frame identification and navigation.

And if you use applets and scripts (Priority 1)

6.3) Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.

And if you use multimedia (Priority 1)

1.3) Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.
1.4) For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.

And if all else fails (Priority 1)

11.4) If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.
smartrobbie

WordPress Website Design Agency based in Seaforth, Northern Beaches.

WORDPRESS SERVICES

WORDPRESS RESOURCES

OUR COMPANY

Facebook Twitter Instagram Linkedin
Semrush certified agency partner badge
Google Rating
5.0
Based on 46 reviews
js_loader

Smart Robbie acknowledges all Aboriginal and Torres Strait Islander Traditional Custodians of Country and recognises their continuing connection to land, sea, culture and community. We pay our respects to Elders past and present.

© 2012 – 2024 Smart Robbie I Website Design for Small Businesses

Scroll to Top
Wordpress Maintenance Checklist

WordPress Maintenance Checklist

Get your FREE checklist for everything you need to maintain your WordPress Site.

  • This field is for validation purposes and should be left unchanged.