The toolbar contains many functions for examining discrete aspects of a web page's content and code. These can be used as an aid for manual checking of many of the Web Content Accessibility Guidelines' Checkpoints. None of the toolbar functions listed will tell you whether a page conforms to a particular checkpoint, but they will help you in
assessing conformance.
1.1 Provide a text equivalent for every non-text element (e.g., via "alt",
"longdesc", or in element content). This includes: images, graphical representations 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.
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.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.
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.
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.
2.2 Ensure that foreground and background color combinations provide sufficient contrast
when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text].
7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e.,
change presentation at a regular rate, such as turning on and off).
7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to
redirect pages automatically. Instead, configure the server to perform redirects.
10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other
windows to appear and do not change the current window without informing the user.
13.3 Provide information about the general layout of a site (e.g., a site map or table of
contents).
None
13.4 Use navigation mechanisms in a consistent manner.
None
And if you use tables (Priority 2)
5.3 Do not use tables for layout unless the table makes sense when linearized.
Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version).
10.2 Until user agents support explicit associations between labels and form controls,
for all form controls with implicitly associated labels, ensure that the label is properly positioned.
None
12.4 Associate labels explicitly with their controls.
7.3 Until user agents allow users to freeze moving content, avoid movement in pages.
None
8.1 Make programmatic elements such as scripts and applets directly accessible or
compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]
10.5 Until user agents (including assistive technologies) render adjacent links distinctly,
include non-link, printable characters (surrounded by spaces) between adjacent links.
None
11.3 Provide information so that users may receive documents according to their
preferences (e.g., language, content type, etc.)
None
13.5 Provide navigation bars to highlight and give access to the navigation mechanism.
None
13.6 Group related links, identify the group (for user agents), and, until user agents do so,
provide a way to bypass the group.
13.10 Provide a means to skip over multi-line ASCII art.
None
14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension
of the page.
None
14.3 Create a style of presentation that is consistent across pages.
None
And if you use images and image maps (Priority 3)
1.5 Until user agents render text equivalents for client-side image map links,
provide redundant text links for each active region of a client-side image map.
10.3 Until user agents (including assistive technologies) render side-by-side text correctly,
provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns.
AIS consider this checkpoint deprecated
And if you use forms (Priority 3)
10.4 Until user agents handle empty controls correctly, include default, place-holding
characters in edit boxes and text areas.