The W3C WAI User Agent Accessibility Guidelines 1.0

Ian Jacobs, W3C (
Co-editor of UAAG 1.0
Daniel Dardailler, W3C (
WAI Technical Director


This paper summarizes the principal goals and structure of "User Agent Accessibility Guidelines (UAAG) 1.0" [UAAG10].


Ms. Laitinen is an accountant at an insurance company that uses Web-based formats over a corporate intranet. She is blind. She uses a screen reader in conjunction with a graphical desktop browser and a speech synthesizer. She uses the speech output, combined with navigation of the important links on a page, to scan documents rapidly for important information, and has become accustomed to listening to speech output at a speed that her co-workers cannot understand at all.

For Ms. Laitinen, it is critical that her desktop browser communicate with available assistive technologies (screen reader, speech synthesizer), so UAAG 1.0 includes requirements related to communication (through programming interfaces) and to the implementation of system conventions (which increase the likelihood of interoperability). Communication with her assistive technology does not suffice to make her browser more accessible, however. Some of her other needs include:

"User Agent Accessibility Guidelines 1.0" explains what software developers can do to improve the accessibility of mainstream browsers and multimedia players so that people with hearing, cognitive, physical, and visual disabilities will have improved access to the World Wide Web. UAAG 1.0 is developed by the W3C User Agent Accessibility Guidelines Working Group, whose participants include software developers, users with disabilities, and international experts in the field of accessibility technologies.

UAAG 1.0 is the third of a trilogy of accessibility guidelines published by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium. These three documents were designed to complement one another and present a consistent model for Web accessibility in which responsibilities for addressing the needs of users with disabilities are shared (and distributed among) authors, software developers, and specification writers. The other two documents are:

Details on the guidelines

UAAG 1.0 explains the responsibilities of user agents in meeting the needs of users with disabilities. A user agent that conforms to these guidelines will enable access through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies such as Ms. Laitinen's screen reader).

Checkpoints and Guidelines

The heart of UAAG 1.0 consists of nearly ninety "checkpoints", each of which includes one or more requirements. The checkpoints are ranked according to their importance to accessibility (priority 1 for most important, then priority 2 and 3). Here is one example of a checkpoint:

Checkpoints are organized into twelve "guidelines". Each guideline expresses a general principle of accessible design. Here is one example of a guideline:


A user agent may satisfy the requirements of UAAG 1.0 in many different ways. The checkpoints of UAAG 1.0 have therefore been written to be independent of specific markup languages (e.g., the Hypertext Markup Language (HTML) or Scalable Vector Graphics (SVG)) and operating systems. To assist developers in understanding how to satisfy the requirements for specific technologies and operating systems, the User Agent Accessibility Guidelines Working Group has published a separate document entitled "Techniques for User Agent Accessibility Guidelines 1.0" [UAAG10-TECHS]. The Techniques document includes references to other accessibility resources (such as platform-specific software accessibility guidelines), examples, and suggestions for approaches that may be part of satisfying the requirements of UAAG 1.0.


The "User Agent Accessibility Guidelines 1.0" [UAAG10] are currently at "last call" stage of the W3C Recommendation track. This means that the UAWG has requested technical review from the Web community, and intends to request advancement to Candidate Recommendation once review comments have been processed. The UAWG anticipates that UAAG 1.0 will become a W3C Recommendation in late 2001. At that time, we look forward to it being an important resource for promoting Web accessibility.


For the latest version of any W3C specification please consult the list of W3C Technical Reports at

"Authoring Tool Accessibility Guidelines 1.0", J. Treviranus, C. McCathieNevile, I. Jacobs, and J. Richards, eds., 3 February 2000. This W3C Recommendation is
"User Agent Accessibility Guidelines 1.0", I. Jacobs, J. Gunderson, E. Hansen, eds. The latest draft is available at
"Techniques for User Agent Accessibility Guidelines 1.0", I. Jacobs, J. Gunderson, E. Hansen, eds. The latest draft is available at
"Web Content Accessibility Guidelines 1.0", W. Chisholm, G. Vanderheiden, and I. Jacobs, eds., 5 May 1999. This W3C Recommendation is