User Agent Accessibility Guidelines 1.0

1. Introduction

Contents · Next

This document specifies requirements that, if satisfied by user agent developers, will lower barriers to accessibility. This introduction (section 1) provides context for understanding the guidelines listed in section 2. Section 1 explains the relationship of this document to other accessibility guidelines published by the Web Accessibility Initiative, which user agents are expected to conform, known limitations of this document, and the relationship of this document to other software design guidelines. Section 3 explains how to make claims that software conforms to these guidelines and details about the applicability of the requirements for different kinds of user agents.

1.1 Relationship to WAI accessibility guidelines

"User Agent Accessibility Guidelines 1.0" (UAAG 1.0) is part of a series of accessibility guidelines published by the Web Accessibility Initiative (WAI). The documents in this series reflect an accessibility model in which Web content authors, format designers, and software developers have roles in ensuring that users with disabilities have access to the Web. These agents intersect and complement each other as follows:

This document explains the responsibilities of user agents in meeting the needs of users with disabilities. The requirements of this document interact with those of the "Web Content Accessibility Guidelines 1.0" [WCAG10] in a number of ways:

Formats, authors, and designers all have limitations. No format allows authors to encode all of their knowledge in a way that a user agent can recognize. A format may lack features required for accessibility. An author may not make use of the accessibility features of a format or may misuse a format (which can cause problems for user agents). A user agent designer may not implement a format specification correctly or completely. Some requirements of this document take these limitations into account.

1.2 Target user agents

This document was designed specifically to improve the accessibility of mainstream user agents with multimedia capabilities for users with one or more disabilities (including visual, hearing, physical, and cognitive). In this context, a mainstream user agent is one designed for the general public to handle general-purpose content in ordinary operating conditions. It is expected that a conforming user agent will typically consist of a Web browser, one or more media players, and possibly other components.

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). Technologies not addressed directly by this document (e.g., those for braille rendering) will be essential to ensuring Web access for some users with disabilities. Note that the ability of conforming user agents to communicate well with assistive technologies will depend in part on the willingness of assistive technology developers to follow the same standards and conventions for communication.

This document allows a certain amount of flexibility in the features a user agent must support in order to conform. For example, some user agents may conform even though they do not support certain content types (such as video or audio) or input modalities (such as mouse or voice). See the section on conformance for more information.

1.3 Known limitations of this document

People with (or without) disabilities access the Web with widely varying sets of capabilities, software, and hardware. Some users with disabilities:

This document does not include requirements to meet all known accessibility needs. Some known limitations of this document include the following:

1.4 Relationship to general software design guidelines

Considerable effort has been made to ensure that the requirements of this document are compatible with other good software design practices. However, this document does not purport to be a complete guide to good software design. For instance, the general topic of user interface design for computer software exceeds the scope of this document, though some user interface requirements have been included because of their importance to accessibility. The "Techniques for User Agent Accessibility Guidelines 1.0" [UAAG10-TECHS] includes some references to general software design guidelines and platform-specific accessibility guidelines (see checkpoint 7.3). Involving people with disabilities in the design and testing of software will generally improve the accessibility of the software.

Installation is an important aspect of both accessibility and general software usability. On platforms where a user can install a user agent, the installation (and update) procedures need to be accessible. This document does not include a checkpoint requiring that installation procedures be accessible. Since this document considers installation to be part of software usage, the different aspects of installation (user interface, documentation, operating environment conventions, etc.) are already covered by the complete set of checkpoints.

Benefits of accessible user agent design

Many users without disabilities are likely to benefit from the requirements developed to benefit users with disabilities. For example, users without disabilities:

Software that satisfies the requirements of this document is expected to be more flexible, manageable, extensible, and beneficial to all users. For example, a user agent architecture that allows programmatic access to content and the user interface will encourage software modularity and reuse, and will enable operation by scripting tools and automated test engines in addition to assistive technologies.