• Skip to content
• | Change text size or colors

WAI: Strategies, guidelines, resources to make the Web accessible to people with disabilities

Site Navigation

W3C Home

Web Accessibility Initiative (WAI) Home

1. Introducing Accessibility
2. Guidelines & Techniques
   1. Development Process
   2. Web Content (WCAG)
   3. Authoring Tool (ATAG)
   4. »User Agent (UAAG)
      • Technical
        1. UAAG 1.0
        2. Checkpoints
        3. Errata
        4. Techniques
      • Educational
        1. FAQ
        2. Press Release
        3. Testimonials
   5. Evaluation Language (EARL)
   6. Rich Internet (WAI-ARIA)
   7. Specific Technologies
3. Managing Accessibility
4. Evaluating Accessibility
5. WAI Groups
6. About WAI

User Agent Accessibility Guidelines (UAAG) Overview

Quick link: UAAG 1.0

User Agent Accessibility Guidelines (UAAG)

The User Agent Accessibility Guidelines (UAAG) documents explain how to make user agents accessible to people with disabilities, particularly to increase accessibility to Web content. User agents include Web browsers, media players, and assistive technologies, which are software that some people with disabilities use in interacting with computers.

UAAG is part of a series of accessibility guidelines, including the Web Content Accessibility Guidelines (WCAG WG) and the Authoring Tool Accessibility Guidelines (ATAG). Essential Components of Web Accessibility explains the relationship between the different guidelines.

Who UAAG is for

UAAG is primarily for developers of Web browsers, media players, assistive technologies, and other user agents.

UAAG and supporting resources are also intended to meet the needs of many different audiences, including policy makers, managers, and others. For example:

• People who want to choose user agents that are more accessible can use UAAG to evaluate user agents
• People who want to encourage their existing user agent developer to improve accessibility in future versions can refer the user agent vendor to UAAG

What is in UAAG 1.0

UAAG 1.0 contains a comprehensive set of checkpoints that cover:

• Access to all content, including content tied to events triggered by the mouse or keyboard
• User control over how content is rendered
• User control over the user interface, with documentation of accessibility features
• Standard programming interfaces, to enable interaction with assistive technologies

Technical document format

UAAG 1.0, the techniques documents, and the checklist follow the W3C format for technical specifications which includes several sections at the beginning: links to differnt versions, editors, copyright, abstract, and status with the link to errata and the email address for comments. Most WAI specifications have a link at the top to the Table of Contents.

Who develops UAAG

UAAG technical documents are developed by the User Agent Accessibility Guidelines Working Group (UAWG), which is part of the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI). For more information about the working group, see the UAWG page.

How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute describes formal periods for public review. Opportunities for review and comment of WAI documents are announced on the WAI home page and WAI Interest Group mailing list. An email address for sending comments is included in the "Status of this Document" section.

Opportunities for contributing to UAAG and other WAI work are introduced in Participating in WAI.

Document Information

Version: 1.1 (up-to-date as of July 2005)
Editor: Shawn Lawton Henry and Matt May. Developed with the Education and Outreach Working Group (EOWG) and the User Agent Accessibility Guidelines Working Group (UAWG).

[Contacting WAI] Feedback welcome to wai-eo-editors@w3.org (a publicly archived list).

File (not content) last updated on $Date: 2006/12/21 21:38:57 $ by $Author: shawn $