A user agent conforms to this document by satisfying the requirements identified by a conformance profile. This normative section explains:
Conformance to the requirements of this document is expected to be a strong indicator of accessibility, but it may be neither a necessary nor a sufficient condition for ensuring the accessibility of software. Thus, some software may not conform to this document but still be accessible to some users with disabilities. Conversely, some software may conform to this document but still be inaccessible to some users with disabilities. Some requirements of this document may not benefit some users for some content, but the requirements are expected to benefit many users with disabilities, for general purpose content. For more information, see the section on known limitations of this document, and the section on restricted functionality and conformance.
This document demands substantially more conformance flexibility than can be achieved using the terms "must", "should", and "may" alone, as defined in RFC 2119 [RFC2119]. Where "must", "should", "required", and "may" appear in this document, they are used consistently with RFC 2119 for a chosen conformance profile. The imperative voice (e.g., "Allow configuration ...") used in the checkpoint provisions implies "must", but a user agent is only obligated to satisfy the requirements of a chosen conformance profile.
Note: UAAG 1.0 extends significantly the conformance mechanism defined in both WCAG 1.0 [WCAG10] and ATAG 1.0 [ATAG10].
A conformance profile is a list of assertions that identify:
There are two primary uses for a conformance profile:
In either case, a conformance profile identifies a set of requirements derived from a default set according to the following mechanisms, collectively called conformance profile labels:
The following sections define the default set of requirements, the structure of a conformance profile, and how to determine the set of requirements identified by a profile. UAAG 1.0 does not define any (named) conformance profiles, but rather defines the mechanism for creating them.
The default set of conformance requirements is defined to be all of the requirements of all of the provisions of all the checkpoints, as qualified by their normative inclusions and exclusions and the following normative inclusions and sufficient techniques that apply across checkpoints.
Except for the checkpoints in guideline 6 that refer to implementation of APIs, the user agent must satisfy the checkpoint requirements through at least one mechanism other than an API. Thus, for most of the requirements in this document, it is not possible to conform by only making information available through an API (which would be used, for example, by an assistive technology to provide the missing feature). For example, checkpoint 9.3 involves navigation that must be possible through the user interface, not just via an API. This and other checkpoints involving user control or configuration will therefore generally be satisfied through features in the user interface or through configuration files (see the section on configuration requirements).
In some cases, a checkpoint may apply equally well to content or user agent features. When it is necessary to remove ambiguity about the scope of a checkpoint, the checkpoint definition includes one of the following labels:
A user agent may also satisfy a "content only" checkpoint for user agent user interface features, and vice-versa. Indeed, user agent developers are encouraged to consider the content-only requirements (e.g., checkpoint 3.3) when designing the user agent's user interface.
The user agent may satisfy a content-only requirement with a mechanism that also involves user agent features. For instance, to satisfy checkpoint 4.7, the user agent may provide control for all volume, whether the source is content or the user agent user interface. Similarly, to satisfy checkpoint 3.3, the user agent may offer a single configuration that turns off blinking in both content and the user interface.
The user agent may satisfy the configuration requirements of this document through configuration files (e.g., profiles, initialization files, style sheets, and themes). For instance, style sheets might be used as a mechanism to satisfy the highlight and configuration requirements of checkpoint 10.2. Any functionality that is configurable through a configuration file should also be configurable through the user agent user interface. Furthermore, if configuration files may be edited by hand, the user agent documentation should explain the configuration file format, or refer to an explanation (a format specification, for example).
For some of the checkpoints in this document (checkpoints 3.3, 5.1, 5.3, and 5.5), configuration is preferred, but not required to satisfy the checkpoint in some circumstances. For other checkpoints, configurability may be as important as the functionality being configured, and is therefore mandatory.
Since this document allows conformance by a user agent consisting of multiple software components, there are likely to be times when, to satisfy the configuration requirements of the document, each component has to provide for configuration independently. To make configuration easier for the user, components should share and inherit configurations (including those of the operating environment).
When a user agent runs in more than one operating environment (e.g., a user agent implemented in Java on top of another operating system), the user agent may satisfy the relevant requirements (e.g., the checkpoints in guideline 7) of a conformance profile by following the conventions of a single operating environment.
When faced with a choice between the conventions of different operating environments, a developer should follow the conventions that benefit accessibility most, while meeting the developer's design goals. For instance, some developers may prefer cross-platform consistency over consistency with other user agents running in a given operating environment, and this might affect which conventions would be preferred.
A conformance profile includes the following assertions:
A profile should not include other information that the required and optional assertions. The wording of the profile should reflect whether the profile is used as part of a conformance claim ("the user agent satisfies these requirements") or as part of another specification ("the user agent must satisfy these requirements").
When a profile is part of a conformance claim, the absence of a conformance profile label implies that the associated requirements are not be satisfied (though the requirements may or may not actually be satisfied). When a profile is included in another specification, the absence of a conformance profile label implies that the associated requirements need not be satisfied.
Thus, a conformance profile when evaluating a user agent might be as short as:
For "User Agent Accessibility Guidelines 1.0", http://www.w3.org/TR/2002/PR-UAAG10-20021016:
- Conformance level: Double A
- Supported conformance profile labels: VisualText, Image, Animation, Audio, Events, and Selection
- A list of checkpoints that do not apply is available online (link to list)
- The specifications that are part of this profile are W3C's HTML 4.0, CSS2, PNG, and SVG (link to each specification)
An extended example below illustrates how to build a conformance profile while evaluating a user agent.
The set of requirements identified by a conformance profile is the set derived from the default set by:
The requirements that cannot be removed through the above mechanisms are part of every UAAG 1.0 conformance profile (including, for example, the keyboard requirements of checkpoint 1.1).
Each conformance level defines a set of requirements, based on priority.
Note: Conformance levels are spelled out in text (e.g., "Double-A" rather than "AA") so they may be understood when rendered as synchronized speech.
Each content type label defines a set of requirements related to support for visually rendered text, images, animations, video, audio, and synthesized speech.
Note: As indicated above, some of the content type labels require implementation of at least one format (e.g., for images). This document does not require implementation of specific formats, (e.g., PNG [PNG] versus SVG [SVG] for images). However, see the requirements of checkpoint 8.2.
Some of the content type labels require that certain checkpoints be satisfied for all implemented specifications, not just those listed in a conformance profile, in order to ensure that the goal of the checkpoint is met. For instance, checkpoint 3.3 involves turning off blinking and animated text. Since there is a risk that these rendering effects may trigger seizures in people with photosensitive epilepsy, it is important that the user be able to turn them off in all cases (whether or not the specification is identified in a conformance profile).
The following checkpoints are designed to augment user agent support for event-driven behavior specified by the author: 1.2, 9.5, and 9.6. Satisfying these checkpoints will promote input device independence and thus enable users with some disabilities to make better use of content designed for a single input device (generally a pointing device). The Events label refers to the requirements of these checkpoints.
This document does not require the user agent to implement a selection mechanism in order to conform. However, if the user agent does implement a selection mechanism, in order to conform it must satisfy the relevant portions of the following checkpoints: 5.4, 6.6, 7.1, 9.4, 10.2, and 10.3. The Selection label refers to the selection requirements of these checkpoints.
Note: This document does require implementation of both content focus and user interface focus; see checkpoints 9.1 and 9.2.
Each input modality label defines a set of requirements related to support for a particular type of input device. Input device requirements in this document are either stated generically (e.g., "input configuration" requirements) or as keyboard-specific requirements (e.g., "keyboard API").
Note: Developers are encouraged to design user agents that are at least partially operable through pointing device and/or voice input, in addition to being fully operable through the keyboard.
A checkpoint (or part of a checkpoint) applies unless any one of the following conditions is met:
NOFRAMEScontent as specified mechanisms for conditional content. On the other hand, HTML user agents are not expected to recognize that a nearby paragraph is a text equivalent for the image (when not marked up as such).
The following example illustrates how to evaluate a user agent and build an appropriate conformance profile. This informative example does not illustrate a complete user agent evaluation.
Consider a user agent that:
For this profile, we choose level Double-A. This establishes a set of requirements consisting of all of the requirements of all the priority 1 and 2 checkpoints.
For this profile, we must include VisualText since the user agent renders text visually.
For this profile, we also wish to include the labels Image, Video, and Audio, so the user agent must satisfy those requirements as well. Consider the following checkpoint:
4.4 Slow multimedia. (P1)
- Allow the user to slow the presentation rate of rendered audio and animation content (including video and animated images).
- As part of satisfying provision one of this checkpoint, for a visual track, provide at least one setting between 40% and 60% of the original speed.
- As part of satisfying provision one of this checkpoint, for a prerecorded audio track including audio-only presentations, provide at least one setting between 75% and 80% of the original speed.
- When the user agent allows the user to slow the visual track of a synchronized multimedia presentation to between 100% and 80% of its original speed, synchronize the visual and audio tracks (per checkpoint 2.6). Below 80%, the user agent is not required to render the audio track.
The second provision is specific to video, so must be satisfied for this profile. The third provision is specific to audio, so must be satisfied as well. The fourth provision involves synchronization, but the user agent does not implement any synchronized multimedia format (see step 6).
Note also the relevant normative exclusions for this checkpoint: the user agent is not required to satisfy the requirements of this checkpoint for audio and animations whose recognized role is to create a purely stylistic effect. In our example, the user agent provides the functionality for all audio and animations – even those used for purely stylistic effects – even though this is not required.
Although the user agent implements two animation formats, it only meets some, but not all, of the requirements associated with the Animation label. Therefore, we do not include it in the profile.
Note: A conformance claim will indicate that the plug-in renders the video.
In this example, the user agent supports functionalities that promote input-device independent access to event handlers. Therefore, we can include the Events label in the profile.
In this example, since the user agent implements a selection mechanism, the profile must include the Selection label (and the user agent must satisfy the associated requirements).
Since the user agent does not fully support operation through the pointing device alone or voice input alone, we exclude the Pointer and Voice labels from the profile.
In step 2 we saw that the fourth provision of checkpoint 4.4 did not apply since the user agent implements no synchronized multimedia format.
Other provisions that do not apply must also be documented.
The profile resulting from these would include the following information:
For "User Agent Accessibility Guidelines 1.0", http://www.w3.org/TR/2002/PR-UAAG10-20021016:
- Conformance level: Double-A
- Supported conformance profile labels: VisualText (T1, T2, T3), Image (I1, I2), Video (V1, V2), Audio (A1), Events, and Selection
- Applicability: For checkpoint 4.4, provision three of checkpoint does not apply because the user agent does not implement any formats that support synchronized multimedia.
A claim is well-formed if it meets the following two conditions.
Condition 1: The claim must include the following information:
Condition 2: At least one version of the claim must conform to the "Web Content Accessibility Guidelines 1.0" [WCAG10], level A. This claim may appear, for example, on the Web or on CD-ROM. If a conformance icon is part of a claim on the Web, it must link to the W3C explanation of the icon.
This specification imposes no restrictions on the format used to make a well-formed claim. For instance, the claim may be marked up using HTML (see sample claim), or expressed in the Resource Description Framework (RDF) [RDF10].
Here is a sample conformance claim (expressed in HTML):
<p>On 16 October
2002, UserAgent X (version 2.3) running on MyOperatingSystem (version 4.2)
conforms to <acronym title="the World Wide Web
Consortium">W3C</acronym>'s "User Agent Accessibility Guidelines 1.0",
http://www.w3.org/TR/2002/PR-UAAG10-20021016. Conformance level: Double A.
Supported conformance profile labels: VisualText, Image, Animation, Audio,
Events, and Selection. A <a
href="http://example.com/checkpoints">list</a> of formats used to
satisfy the requirements, and of checkpoints that do not apply is available
online. The specifications that are part of this profile are W3C's HTML 4.0,
CSS2, PNG, and SVG (where each acronym links to the corresponding
A conformance claim is valid if it is well-formed and if the user agent satisfies the requirements of the chosen conformance profile.
The document has been designed to help non-experts evaluate the validity of conformance claims. Some checkpoints may require interpretation and judgment. In some cases, although a requirement is clearly stated, without documentation or feedback from developers (e.g., about implemented APIs) it may be difficult to evaluate whether a user agent has satisfied the requirement. Some checkpoints (e.g., those requiring developers to follow conventions or implement specifications defined outside this document) are inherently more open to interpretation than others.
It is not currently possible to evaluate the validity of a claim automatically.
Note: The checklist [UAAG10-CHECKLIST] is designed to help people evaluate user agents. The User Agent Accessibility Guidelines Working Group makes available additional test suites, guides, and other tools to help people evaluate user agents for conformance.
User agents do not conform to this document on a per-resource basis; claims are not as specific as "the user agent conforms for this particular Web page." A claim is valid if the user agent satisfies the requirements identified by the claim for most general-purpose content, in ordinary operating conditions.
In some cases, the author's content may limit the user agent's functionality for specific reasons, such as to protect intellectual property rights, to provide a read-only view (allowing no user interaction), or to limit interaction for a specialized purpose (e.g., a "written" driving test). Content that limits the functionality of the user agent in some cases does not automatically invalidate a claim about the user agent.
A conformance claim (with or without an accompanying conformance icon) is an assertion that a user agent has satisfied the requirements of a chosen conformance profile. Claimants (or relevant assuring parties) are solely responsible for the validity of their claims, keeping claims up to date, and proper use of the conformance icons.
The existence of a conformance claim (with or without an accompanying conformance icon) does not imply that W3C has reviewed the claim or assured its validity. As of the publication of this document, W3C does not act as an assuring party, but it may do so in the future, or it may establish recommendations for assuring parties.
Claimants are expected to modify or retract a claim if it may be demonstrated that the claim is not valid. Claimants are encouraged to claim conformance to the most recent User Agent Accessibility Guidelines Recommendation available.
This specification imposes no restrictions about:
People may use a conformance icon (or, "conformance logo") anywhere, including on a Web site, on user agent packaging, and in documentation. It is meaningless to use a conformance icon on its own, i.e., to use the icon without an associated well-formed claim.
Draft Note: In the event this document becomes a W3C Recommendation this document will link to the W3C Web site for additional information about the icons and how to use them.
Authors of technical specifications (such as W3C Recommendations) should incorporate the requirements of UAAG 1.0 as part of conformance to their specifications. This may be done by direct inclusion, or by reference using a conformance profile. Direct inclusion promotes the integration of specialized accessibility requirements; inclusion by reference is easier and less prone to error.
For more information on designing specifications that promote accessibility, refer to W3C's "XML Accessibility Guidelines" [XAG10].
objectelements are defined, include a statement such as "Per checkpoint 3.4 of UAAG 1.0, a conforming user agent must allow configuration not to execute scripts, applets, or other executable content."
'text-decoration'property is defined, include a statement such as "A conforming user agent must either: (a) allow configuration to override the
'blink'value with the 'none' value, or (b) ignore the
'blink'value. This is required by checkpoint 3.3 of UAAG 1.0 [UAAG10]."
Section G.5 of the SVG 1.0 Recommendation [SVG] states:
Additionally, an authoring tool which is a Conforming SVG Generator conforms to all of the Priority 1 accessibility guidelines from the document "Authoring Tool Accessibility Guidelines 1.0" that are relevant to generators of SVG content.
This statement requires conformance to the Authoring Tool Accessibility Guidelines as part of conformance to SVG 1.0 (for certain classes of tools). This type of "conformance requirement by reference" is also possible for UAAG 1.0, by inclusion of a conformance profile.
The following is a (partial) example of a conformance profile for the MyFormat specification (expressed in plain text):
As part of conformance to MyFormat 1.0, a user agent must satisfy the following conformance profile:
See the section on how to refer to UAAG 1.0 for what should appear in the references section of the specification.