This document is an appendix to the W3C "User Agent Accessibility Guidelines 1.0". It provides a list of all
checkpoints from the User Agent Accessibility Guidelines 1.0, organized by concept, as a checklist
for user agent 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 tool or set of tools for
accessibility. For each checkpoint, indicate whether the checkpoint
has been satisfied, has not been satisfied, or is not applicable.
A tabular version of
the list of checkpoints is also available (e.g., for printing).
This section describes the status of this document at the time
of its publication. Other documents may supersede this document. The
latest status of this document series is maintained at the W3C.
This document is an appendix to a Working Draft.
It is a draft document and may be updated, replaced or
obsoleted by other documents at any time. It is inappropriate to use W3C
Working Drafts as reference material or to cite them as other than "work
in progress". This is work in progress and does not imply endorsement
by, or the consensus of, either W3C or Members of the WAI User Agent (UA)
Please send comments about this document to the public mailing list:
This document has been produced as part of the Web Accessibility Initiative.
The goal of the WAI User Agent
Guidelines Working Group is discussed in the Working Group
A list of current W3C Recommendations and other technical documents
can be found at http://www.w3.org/TR.
Each checkpoint in this document is assigned a priority
that indicates its importance for users with disabilities.
- [Priority 1]
- This checkpoint must be satisfied by user agents,
otherwise one or more groups of users with disabilities will
find it impossible to access the Web. Satisfying
this checkpoint is a basic requirement for enabling
some people to access the Web.
- [Priority 2]
- This checkpoint should be satisfied by user
agents, otherwise one or more groups of users
will find it difficult
to access the Web. Satisfying this checkpoint
will remove significant barriers to Web access for some
- [Priority 3]
- This checkpoint may be satisfied by user agents
to make it easier for one or more groups of users
with disabilities to
access information. Satisfying this checkpoint will improve
access to the Web for some people.
Priority 1 checkpoints
In General (Priority 1)
Control of style (Priority 1)
User Interface (Priority 1)
For Keyboard and other Input Devices (Priority 1)
For Communication (Priority 1)
- Checkpoint 1.1 Ensure that every functionality offered through the user interface is available through every input device API used by the user agent. User agents are not required to reimplement low-level functionalities (e.g., for character input or pointer motion) that are inherently bound to a particular API and most naturally accomplished with that API.
(Techniques for 1.1)
- Checkpoint 1.2 Use the standard input and output device APIs of the operating system.
(Techniques for 1.2)
- Checkpoint 1.3 Ensure that the user can interact with all active elements in a device-independent manner.
(Techniques for 1.3)
- Checkpoint 1.5 Ensure that all messages to the user (e.g., informational messages, warnings, errors, etc.) are available through all output device APIs used by the user agent. Do not bypass the standard output APIs when rendering information (e.g., for reasons of speed, efficiency, etc.).
(Techniques for 1.5)
- Checkpoint 5.1 Provide programmatic read and write access to content by conforming to W3C Document Object Model (DOM) specifications and exporting interfaces defined by those specifications.
(Techniques for 5.1)
- Checkpoint 5.2 Provide programmatic read and write access to user agent user interface controls using standard APIs (e.g., platform-independent APIs, standard APIs for the operating system, and conventions for programming languages, plug-ins, virtual machine environments, etc.)
(Techniques for 5.2)
- Checkpoint 5.4 Provide programmatic notification of changes to content and user interface controls (including selection, content focus, and user interface focus).
(Techniques for 5.4)
- Checkpoint 9.1 Provide information about user agent-initiated content and viewport changes through the user interface and through APIs
(Techniques for 9.1)
- Checkpoint 10.1 Provide information directly to the user and through APIs about current user preferences for input configurations (e.g., keyboard or voice bindings).
(Techniques for 10.1)
Priority 2 checkpoints
In General (Priority 2)
- Checkpoint 2.3 When no text equivalent has been supplied for an object, make available author-supplied information to help identify the object (e.g., object type, file name, etc.).
(Techniques for 2.3)
- Checkpoint 5.6 Follow operating system conventions and accessibility settings. In particular, follow conventions for user interface design, default keyboard configuration, product installation, and documentation.
(Techniques for 5.6)
- Checkpoint 7.4 Allow the user to navigate just among all active elements.
(Techniques for 7.4)
- Checkpoint 7.5 Allow the user to search for rendered text content, including text equivalents of visual and auditory content.
(Techniques for 7.5)
- Checkpoint 7.6 Allow the user to navigate according to structure.
(Techniques for 7.6)
- Checkpoint 10.6 Allow the user to configure the user agent in named profiles that may be shared on systems with distinct user accounts.
(Techniques for 10.6)
- Checkpoint 11.4 In a dedicated section, document all features of the user agent that promote accessibility.
(Techniques for 11.4)
Control of style (Priority 2)
User Interface (Priority 2)
For Keyboard and other Input Devices (Priority 2)
For Communication (Priority 2)
Priority 3 checkpoints
In General (Priority 3)
- Checkpoint 2.4 When a text equivalent for content is explicitly empty (i.e., an empty string), render nothing.
(Techniques for 2.4)
- Checkpoint 2.7 For author-identified but unsupported natural languages, allow the user to request notification of language changes in content.
(Techniques for 2.7)
- Checkpoint 7.7 Allow the user to configure structured navigation.
(Techniques for 7.7)
- Checkpoint 8.8 Provide a mechanism for highlighting and identifying (through a standard interface where available) active elements.
(Techniques for 8.8)
- Checkpoint 9.5 When loading content (e.g., document, video clip, audio clip, etc.) indicate what portion of the content has loaded and whether loading has stalled.
(Techniques for 9.5)
- Checkpoint 9.6 Indicate the relative position of the viewport in content (e.g., the percentage of an audio or video clip that has been played, the percentage of a Web page that has been viewed, etc.).
(Techniques for 9.6)
Control of style (Priority 3)
User Interface (Priority 3)
For Keyboard and other Input Devices (Priority 3)