User Agent Accessibility Guidelines 1.0

Abstract

This document provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). User agents include HTML browsers and other types of software that retrieve and render Web content. A user agent that conforms to these guidelines will promote accessibility through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies). Furthermore, all users, not just users with disabilities, should find conforming user agents to be more usable.

In addition to helping developers of HTML browsers and media players, this document will also benefit developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a conforming user agent. Technologies not addressed directly by this document (e.g., technologies for braille rendering) will be essential to ensuring Web access for some users with disabilities.

Status of this document

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 is the 17 December 2002 Recommendation of "User Agent Accessibility Guidelines 1.0." This document has been reviewed by W3C Members, the disability community, software developers, and other W3C groups and interested parties, and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.

This document was produced by the User Agent Accessibility Guidelines Working Group (UAWG). The goals of the UAWG are described in UAWG charter. The complete list of changes to this document is available on the Web.

The UAWG also provides additional resources to support this document (e.g., Frequently Asked Questions (FAQ) about UAAG 1.0, implementation reports, and test suites). Please consult the UAWG home page for more information.

Patent disclosures relevant to this specification may be found on the Working Group's patent disclosure page in conformance with W3C policy.

The list of errata for this document is available at http://www.w3.org/WAI/UA/UAAG-errata. Please report errors in this document to wai-uaag-editor@w3.org.

Please send other comments about this document to the public mailing list w3c-wai-ua@w3.org; public archives are available.

The English version of this document is the authoritative version. Translations into other languages may be available at http://www.w3.org/WAI/UA/UAAG-translations.

This document is part of a series of accessibility documents published by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C). WAI Accessibility Guidelines are produced as part of the WAI Technical Activity.

A list of current W3C Recommendations and other technical documents can be found at the W3C Web site.

1. Introduction

This document specifies requirements that, if satisfied by user agent developers, will lower barriers to accessibility. This document includes the following:

• This introduction provides context for understanding the requirements listed in section 2.
• Section 2 explains 12 general principles of accessible design, called "guidelines." Each guideline consists of a list of requirements, called "checkpoints," which must be satisfied in order to conform to this document. Note: Section 2 is numbered differently than the other sections; it consists of a list of guidelines. In section 2, "checkpoint 1.2" refers to the second checkpoint of the first guideline. "Section 1.2" refers to a subsection of the Introduction.
• Section 3 explains how to make claims that software components satisfy the requirements of section 2.
• An appendix offers a summary of this document's principal goals and structure [UAAG10-SUMMARY].
• A second appendix lists all the checkpoints for convenient reference (e.g., as a tool for developers to evaluate software for conformance) [UAAG10-CHECKLIST].

A separate document, entitled "Techniques for User Agent Accessibility Guidelines 1.0" (the "Techniques document" from here on) [UAAG10-TECHS], provides suggestions and examples of how each checkpoint might be satisfied. It also includes references to other accessibility resources (such as platform-specific software accessibility guidelines) that provide additional information on how a user agent may satisfy each checkpoint. The techniques in the Techniques document are informative examples only, and other strategies may be used or required to satisfy the checkpoints. The UAWG expects to update the Techniques document more frequently than the current guidelines. Developers, W3C Working Groups, users, and others are encouraged to contribute techniques.

1.1 Relation 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. The accessibility-related interests of these stakeholders intersect and complement each other as follows:

• Designers of formats (e.g., HTML, XHTML, XML, SVG, SMIL, MathML, and XForms) and protocols (e.g., HTTP) create specifications that allow communication on the Web. Format designers include features in these specifications that authors should use to create accessible content and that user agents should support through an accessible user interface. The "XML Accessibility Guidelines (XAG)" [XAG10] explains the responsibilities of XML format designers; many XAG requirements make sense for non-XML formats as well.
• Authors make use of the accessibility features of different format specifications, use markup appropriately, write in clear and simple language, and organize a Web site consistently. The "Web Content Accessibility Guidelines 1.0" [WCAG10] explains the responsibilities of authors in meeting the needs of users with disabilities. The "Web Content Accessibility Guidelines (WCAG) 1.0" is considered within UAAG 1.0 to be the reference set of requirements to make Web content accessible. The "Authoring Tool Accessibility Guidelines 1.0" [ATAG10] explains the responsibilities of authoring tool developers. An accessible authoring tool facilitates the creation of accessible Web content and may be operated by users with disabilities.
• User agent developers design software that meets the needs of users with disabilities through conformance to other specifications, an accessible user interface, accessible documentation, and communication with other software (notably assistive technologies).

The requirements of this document interact with those of the "Web Content Accessibility Guidelines 1.0" [WCAG10] in a number of ways:

• UAAG 1.0 checkpoint 8.1 requires implementation of the accessibility features of specifications. Features are those identified as such and those that satisfy all of the requirements of WCAG 1.0 [WCAG10].
• UAAG 1.0 checkpoint 12.1 requires conformance to WCAG 1.0 for user agent documentation.
• UAAG 1.0 also incorporates some terms and concepts from WCAG 1.0, a consequence of fact that the documents were designed to complement one another.

Some requirements of this document take into account limitations of formats, authors, and designers. For example, formats generally do not enable authors to encode all of their knowledge in a way that a user agent can fully 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 of these limitations are taken into account as follows:

• UAAG 1.0 includes requirements to satisfy the expectations set by WCAG 1.0 "until user agent" clauses. These clauses make additional requirements of authors in order to compensate for some limitations of deployed user agents.
• UAAG 1.0 includes several repair requirements (e.g., checkpoints checkpoint 2.7 and checkpoint 2.10) for cases where content does not conform to WCAG 1.0. Furthermore, this document includes some requirements to address certain widespread authoring practices that are discouraged because they may cause accessibility or usability problems (e.g., some uses of HTML frames).
• Except for the indicated repair checkpoints, UAAG 1.0 only requires user agents to handle what may be recognized through protocols and formats. For example, user agents are not expected to recognize that the author has used "clear and simple" language to express ideas (WCAG 1.0, checkpoint 14.1). See the section on checkpoint applicability for more information about what the user agent is expected to recognize.

The Web Accessibility Initiative provides other resources and educational materials to promote Web accessibility. Resources include information about accessibility policies, links to translations of WAI materials into languages other than English, information about specialized user agents and other tools, accessibility training resources, and more.

Note: The Web Accessibility Initiative is developing new versions of both the Web Content Accessibility Guidelines and the Authoring Tool Accessibility Guidelines. The User Agent Accessibility Guidelines Working Group expects to follow the progress of those documents. UAAG 1.0 refers only to the WCAG 1.0 and ATAG 1.0 Recommendations, which will remain available and unchanged.

1.2 Target user agents

This document was designed specifically to improve the accessibility of user agents with multimedia capabilities running in the following type of environment (typically that of a desktop computer):

• The operating environment includes a keyboard (or keyboard equivalent)
• Assistive technologies may be used in the operating environment and may communicate with the conforming user agent

The target user agent is one designed for the general public to handle general-purpose content in ordinary operating conditions.

This document does not forbid conformance by other types of user agents, but some requirements (e.g., implementation of certain application programming interfaces, or APIs) are not likely to be satisfied in environments (e.g., handheld devices or kiosks) other than the target environment. Future work by the UAWG may address the accessibility of user agents running on handheld devices, for example.

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.

1.2.1 Composition of conforming user agents

In general, a conforming user agent will consist of several coordinated components, such as a Web browser, a multimedia player, several plug-ins, features or applications provided by the operating environment, and documentation distributed with the software or available on the Web. These components may run on the user's computer or on a server. A conforming user agent may also include assistive technologies and applications provided by the operating environment. The current document places no restrictions on the type or number of components used for conformance.

This does not mean that every component that one has chosen as part of the user agent has to satisfy every single requirement; some requirements may not be relevant for a particular component. For instance, if a component does not have a user interface, the user interface requirements would not be relevant. On the other hand, if a component has a user interface, the user interface requirements are relevant. Conformance addresses the composite user agent as a whole.

1.2.2 Use of operating environment features

The UAWG encourages developers to satisfy the requirements of this document by adopting operating environment conventions and features that benefit accessibility. When an operating environment feature (e.g., the operating system's audio control panel, including its user interface) is adopted to satisfy the requirements of this document, it is part of the user agent.

See additional information on conformance of user agents running in multiple operating environments.

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:

• May not be able to see, hear, move, or speak.
• May not be able to perceive, read, or process some types of information easily or at all.
• May not have or be able to use a keyboard or pointing device.

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

Input modalities

This document only includes requirements for keyboard, pointing device, and voice input modalities. This document includes several checkpoints related to voice input as part of general input requirements (e.g., the checkpoints of guideline 7 and guideline 11) but does not otherwise address voice-based navigation or control.

Note: The UAWG intends to coordinate further work on the topics of voice input and synthesized speech rendering with groups in W3C's Voice Browser Activity and Multimodal Interaction Activity.

Output modalities

This document does not include requirements for braille rendering. Some requirements are specific to graphical rendering and others specific to audio output or synthesized speech output. Speech rendering requirements are made by checkpoint 4.9 to checkpoint 4.13. Many of the requirements of this document are generic enough to apply to a variety of output modalities, including braille. User agents conform to this document by supporting some combination of graphical and audio/speech rendering output; see the section on Content type labels for more information.

Size and color of non-text content

This document includes some checkpoints to ensure that the user is able to control the size and color of visually rendered text content (checkpoints 4.1 and 4.3). This document does not in general address control of the size and color of visually rendered non-text content (e.g., images).

Note: A user agent may implement resizing functionalities as part of conformance to other specifications (e.g., Scalable Vector Graphics [SVG]).

Background image interference

The requirement of checkpoint 3.1 to allow the user to turn off rendering of background images does not extend to multi-layered rendering.

User control of every user interface component

This document distinguishes user interface features that are part of the user agent user interface and those that are part of content. Some checkpoints (e.g., those in guideline 5) require user control over rendering and behavior that is driven by content only. This document does not always explicitly require the same control over features of the user agent user interface. Nevertheless, this document (see checkpoint 7.3) does require user agents to follow software usability guidelines. The UAWG expects such usability guidelines to include requirements for user control over user interface behavior.

Note: It is more difficult for users to distinguish content from user interface when both are rendered as sound in one temporal dimension, than it is when both are rendered visually in two spatial dimensions. Thus, the UAWG encourages developers of user agents that include audio output or synthesized speech output to apply the requirements of this document to both content and user agent components.

Time parameters

This document includes requirements (see checkpoints 2.4, 4.4, 4.5, and 4.9) for control of some time parameters. The requirements are for time parameters that the user agent recognizes and controls. This document does not include requirements for control of time parameters managed on the server.

Digital rights management

The User Agent Accessibility Guidelines Working Group recognizes that further work is necessary in the area of digital rights management as it relates to accessibility. Digital rights management refers to methods of describing and perhaps enforcing intellectual property associated with Web resources.

Note: The User Agent Accessibility Guidelines Working Group may address these and other topics in a future version of the User Agent Accessibility Guidelines. Even though UAAG 1.0 does not address these topics, the UAWG encourages user agent developers to consider them in their designs.

1.4 Relation to general software design guidelines and other specifications

One the goals of the authors of this document is to ensure that the requirements 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 document [UAAG10-TECHS] includes some references to general software design guidelines and platform-specific accessibility guidelines (in particular, see checkpoint 7.3). Involving people with disabilities in the design and testing of software will generally improve the accessibility of the software.

This document promotes conformance to other specifications as part of accessible design. Conformance to specifications makes it easier to design assistive technologies, and helps ensure the implementation of built-in accessibility functions.

This document also includes some requirements to implement an accessibility feature that may only be optional in another specification.

In rare cases, a requirement in UAAG 1.0 may conflict with a requirement in another specification. UAAG 1.0 does not define a process for resolving such conflicts. The authors of this document anticipate that developers will consider accessibility implications in determining how to resolve them.

1.4.1 Installation

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. Furthermore, the installation procedure should provide and install all components necessary to satisfy the requirements of this document, since the risk of installation failure increases with the number of components (e.g., plug-ins) to be installed.

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 (e.g., user interface, documentation, and operating environment conventions) are already covered by the complete set of checkpoints.

1.5 Security considerations

Some of the requirements of this document may have security implications, such as communication through APIs, and allowing programmatic read and write access to content and user interface control. This document assumes that features required by this document will be built on top of an underlying security architecture. Consequently, unless permitted explicitly in a checkpoint (as in checkpoint 6.5), this document grants no conformance exemptions based on security issues.

Developers should design user agents that enable communication with trusted assistive technologies. Sensitive information that the user agent can access through the user agent's user interface should also be available to assistive technologies through secure means. For instance, if the user types a password in the user agent user interface, do not communicate substitute characters (such as asterisks) through an API, but rather the real password, properly encrypted.

Note also that appropriate user agent behavior with respect to security may depend on the user's context. For instance, hiding typed passwords with asterisks is much less important for someone alone in a room than for someone in a crowded room. Similarly, while unencrypted passwords rendered as synthesized speech should not be broadcast in a crowded room, they may pose no security risk if the user is wearing an earphone.

For information related to security, refer to "XML-Signature Syntax and Processing" [XMLDSIG] and "XML Encryption Syntax and Processing" [XMLENC].

1.6 User control

This document emphasizes the goal of ensuring that users, including users with disabilities, have control over their environment for accessing the Web. Key methods for achieving that goal include: optional self-pacing, configurability, device-independence, interoperability, direct support for both graphical and auditory output, and adherence to published conventions. Chapter 2 addresses these issues in detail.

This document also acknowledges the importance of author preferences and the proper implementation of specifications. However, this document includes requirements to override certain author preferences when the user would not otherwise be able to access that content.

1.6.1 Control of automatic behavior

Many of the requirements in this document give the user additional control over behavior that would otherwise occur automatically. For instance, there is a requirement to allow configuration to not open a viewport automatically (checkpoint 5.3) and one that requires user confirmation before submitting a form (checkpoint 5.5). This type of manual configuration option may be essential for some users with disabilities, since automatic behavior may be disorienting or interfere with navigation.

1.6.2 Configurability

This document includes requirements for users with a variety of disabilities, in part because some users may have more than one disability. In some cases, it may appear that two requirements contradict each other. For instance, a user with a physical disability may prefer that the user agent offer more automatic behavior (to reduce demand for physical effort) than a user with a cognitive disability (for whom automatic behavior may cause confusion). Thus, many of the requirements in this document involve configuration as one way to ensure that a functionality designed to improve accessibility for one user does not interfere with accessibility for another. Also, since a default user agent setting may be useful for one user but interfere with accessibility for another, this document prefers configuration requirements to requirements for default settings. Finally, there may be some cases where, for some content, a feature required by this document is ineffective or causes content to be less accessible, making it imperative that the user be able to turn off the feature.

To avoid overwhelming users with an abundance of configuration options, this document includes requirements that promote ease of configuration and documentation of accessibility features (see guideline 12).

1.6.3 Device independence, spatial independence, and temporal independence

Many requirements in this document promote different kinds of independence:

• Input and output device independence. This document includes some requirements to promote device-independence natively, as well as requirements for interoperability with assistive technologies that provide complementary input and output functionalities.
• Spatial independence. Some users may not navigate effectively in two-dimensional visual space (e.g., users who do not use a pointing device) or may be constrained to one temporal dimension (e.g., users of audio-only output).
• Temporal independence. Some users (e.g., users with a physical or cognitive disability) may not be able to interact with content that changes over time, or interaction with content that is time-sensitive.

1.6.4 Additional benefits of accessible user agent design

In meeting the goals of users with disabilities, user agent developers will also improve access to the Web for users in general. For example, users without disabilities:

• may have a text-only screen, a small screen, or a slow Internet connection (e.g., via a mobile phone browser). These users are likely to benefit from the same features that provide access to people with low vision or blindness.
• may be in a situation where their eyes, ears, or hands are busy or interfered with (e.g., driving to work or working in a noisy environment). These users are likely to benefit from the same features that provide access to people who cannot use a mouse or keyboard due to a visual, hearing, or physical disability.
• may not understand fluently the natural language of spoken content. These users are likely to benefit from the same visual rendering of text equivalents that make spoken language accessible to people with a hearing disability.

The UAWG expects that software which satisfies the requirements of this document will 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.

2. The user agent accessibility guidelines

The 12 guidelines in this document state general principles for the development of accessible user agents. Each guideline includes:

• The guideline number.
• The guideline title. (Informative)
• A slightly longer statement of what the guideline addresses. (Informative)
• The rationale behind the guideline and identification of some groups of users who benefit from it. (Informative)
• A list of checkpoint definitions. This list may be split into groups of related checkpoints. For instance, the list might be split into one group of "checkpoints for visually rendered text" and second group of "checkpoints for audio volume control." Within each group, checkpoints are ordered according to their priority, e.g., Priority 1 before Priority 2. Within a guideline, checkpoint groupings and checkpoint order have no bearing on conformance.

Each checkpoint definition includes the following parts. Some parts are normative (i.e., relate to conformance); others are informative only.

• The checkpoint number.
• The checkpoint title. This title is not a requirement, but rather is a phrase to help readers remember an important requirement made by the checkpoint provision(s). (Informative)
• The priority of the checkpoint. (Normative)
• A link to the Techniques document [UAAG10-TECHS] for more information about the checkpoint: rationale, who benefits, example techniques, references, and more. (Informative)
• A list of one or more checkpoint provisions, which embody the requirements of the checkpoint. These requirements must be satisfied by the user agent for conformance. (Normative)
• Techniques that are sufficient for satisfying all or part of a checkpoint. (Normative when present)
• Normative inclusions and exclusions. These are qualifications about what is required (inclusion) or is not required (exclusion) to satisfy the checkpoint. Some of the inclusions are reminders about what may be required for conformance:
  1. When it might be ambiguous whether a checkpoint makes requirements for content only, the user agent user interface only, or both together, a label will state the intended scope. See the section on requirements for content, user agent features, or both for more information.
  2. When a checkpoint may be excluded from a conformance profile, it is identified by a conformance profile label. See the section on conformance profiles for more information on how a user agent may conform to this document even though it does not satisfy every checkpoint.
  (Normative when present)
• Notes about the checkpoint (beginning with the word "Note"). The notes clarify the scope of the checkpoint through further description, examples, cross references, and commentary. (Informative when present)

The UAWG encourages first-time readers of this document to take advantage of the full context provided for each checkpoint, including the guideline prose, the surrounding checkpoints (since nearby checkpoints are generally related), notes after checkpoints, and associated techniques (in the Techniques document [UAAG10-TECHS]). The checklist [UAAG10-CHECKLIST] is also a useful tool (e.g., for evaluating a user agent for conformance), but does not provide the same contextual support.

About the checkpoints

By design, the checkpoints in this document are generally technology-independent so that they make sense for a variety of existing and future technologies. The Techniques document [UAAG10-TECHS] is an important resource to help developers understand how to apply the requirements to HTML, CSS, SMIL, and SVG, and several operating environments.

Each checkpoint is a "minimal" requirement that must be satisfied for conformance. Developers can always implement features beyond those required by this document. In some cases, it may be easier (or just better design) to implement a general feature rather than one that meets only the narrow requirement of a single checkpoint. For example, a navigable structure view of content that allows users to query elements for their properties is likely to benefit all users and may satisfy a number of requirements of this document.

Some requirements have a wider impact than others. For instance, the keyboard requirements of checkpoint 1.1 have an impact on all other requirements in the document related to user input: any requirement that involves user input must be satisfied through the keyboard. Because the keyboard requirements of checkpoint 1.1 have been factored out, the other checkpoints are shorter; they are written "Allow configuration" instead of "Allow configuration so that, through the keyboard, ..."

In general, each provision makes a single requirement. However, some provisions include more than one requirement in order to emphasize an important relationship. For instance, checkpoint 4.4 includes requirements that apply to both audio and animations in order to emphasize a particular property of content that changes continuously over time. When a provision includes more than one requirement, it is possible that only certain "portions" of the provision will be relevant to a chosen conformance profile; this is illustrated in an example of building a conformance profile.

Priorities

Each checkpoint in this document is assigned a priority that indicates its importance for users with disabilities.

Priority 1 (P1)

If the user agent does not satisfy this checkpoint, 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 (P2)

If the user agent does not satisfy this checkpoint, one or more groups of users with disabilities will find it difficult to access the Web. Satisfying this checkpoint will remove significant barriers to Web access for some people.

Priority 3 (P3)

If the user agent satisfies this checkpoint, one or more groups of users with disabilities will find it easier to access the Web.

This document uses the priorities as one mechanism for allowing conformance to well-defined sets of checkpoints. See the section on conformance levels for more information.

Ensure that the user can interact with the user agent (and the content it renders) through different input and output devices.

Since people use a variety of devices for input and output, user agent developers need to ensure redundancy in the user interface. The user may have to operate the user interface with a variety of input devices (e.g., keyboard, pointing device, and voice input) and output modalities (e.g., graphical, speech, or braille rendering).

Though it may seem contradictory, enabling full user agent operation through the keyboard is an important part of promoting device-independence in target user agents. In addition to the fact that most operating environments include support for some form of keyboard, there are several reasons for this:

• For some users (e.g., users with blindness or physical disabilities), operating a user agent with a pointing device may be difficult or impossible since it requires tracking the pointing device position in a two-dimensional visual space. Keyboard operation generally makes fewer perceptual/motor demands for moving the pointing device to a visual target.
• Some assistive technologies that support a diversity of input and output mechanisms use keyboard APIs for communication with some user agents; see checkpoint 6.7. People who cannot or do not use a pointing device may interact with the user interface with the keyboard, through voice input, a head wand, touch screen, or other device.

While this document only requires keyboard operation for conformance, it promotes input device independence by also allowing people to claim conformance for full pointing device support or full voice support.

As a way to promote output device independence, this guideline requires support for text messages in the user interface because text may be rendered visually, as synthesized speech, or as braille.

The API requirements of guideline 6 also promote device independence by ensuring communication with other software, including assistive technologies.

Checkpoint definitions

1.1 Full keyboard access (P1) Techniques for checkpoint 1.1

1. Ensure that the user can operate, through keyboard input alone, any user agent functionality available through the user interface.

Note: For example, ensure that the user can interact with enabled elements, select content, navigate viewports, configure the user agent, access documentation, install the user agent, and operate user interface controls, all entirely through keyboard input.

User agents generally support at least three types of keyboard operation:

1. Direct (e.g., keyboard shortcuts such a "F1" to open the help menu; see checkpoint 11.4 for single-key access requirements),
2. Sequential (e.g., navigation through cascading menus), and
3. Spatial (e.g., when the keyboard is used to move the pointing device in two-dimensional visual space to manipulate a bitmap image).

User agents should support direct or sequential keyboard operation for all functionalities. Furthermore, the user agent should satisfy this checkpoint by offering a combination of keyboard-operable user interface controls (e.g., keyboard operable print menus and settings) and direct keyboard shortcuts (e.g., to print the current page).

It is also possible to claim conformance to this document for full support through pointing device input and/or voice input. See the section on Input modality labels.

1.2 Activate event handlers (P1) Techniques for checkpoint 1.2

1. Allow the user to activate, through keyboard input alone, all input device event handlers that are explicitly associated with the element designated by the content focus.
2. In order to satisfy provision one of this checkpoint, the user must be able to activate as a group all event handlers of the same input device event type. For example, if there are 10 handlers associated with the onmousedown event type, the user must be able to activate the entire group of 10 through keyboard input alone, and must not be required to activate each handler separately.

Note: Refer to the checkpoints of guideline 9 for more information about focus requirements.

1.3 Provide text messages (P1) Techniques for checkpoint 1.3

1. Ensure that every message (e.g., prompt, alert, or notification) that is a non-text element and is part of the user agent user interface has a text equivalent.

Note: For example, if the user is alerted of an event by an audio cue, a visually-rendered text equivalent in the status bar could satisfy this checkpoint. Per checkpoint 6.5, a text equivalent for each such message must be available through an API. See also checkpoint 6.6 for requirements for programmatic notification of changes to the user interface.

Ensure that users have access to all content, notably conditional content that may have been provided to meet the requirements of the Web Content Accessibility Guidelines 1.0 [WCAG10].

The checkpoints in this section require the user agent to provide access to all content through a series of complementary mechanisms designed so that if one fails, another will provide some access. The following preferences are embodied in the checkpoints:

• Both manual and automatic selection of which conditional content to render are important to accessibility.
• Both structured navigation and unstructured access to content are important to accessibility.
• Rendering according to format specification is preferred, but a source view of text content may be necessary for access (e.g., because of user-side error conditions, authoring errors, inadequate specification, or incorrect user agent implementation). For example, in order to find necessary information, the user may have to look at Uniform Resource Identifiers (URIs) for information, HTML comments, XML element names, or script data.
• Configuration and control of rendering are important for access. For instance, the user agent should respect authoring synchronization cues for content that changes over time, but also needs to allow the user to control the time intervals when user input might otherwise be impossible.

Authors may use the conditional content mechanisms of a specification to satisfy the requirements of the Web Content Accessibility Guidelines 1.0 [WCAG10]. Ensuring access to conditional content benefits all users since some users may not have access to some content due to a technological limitation (e.g., their mobile browser cannot display graphics) or a configuration preference (e.g., they have a slow Internet connection and prefer not to download movies or images).

Checkpoint definitions

2.1 Render content according to specification (P1) Techniques for checkpoint 2.1

1. Render content according to format specification (e.g., for a markup language or style sheet language).

Note: If a conforming user agent does not render a content type, it should allow the user to choose a way to handle that content (e.g., by launching another application or by saving it to disk).

2.2 Provide text view (P1) Techniques for checkpoint 2.2

1. For content authored in text formats, provide a view of the text source.

2.3 Render conditional content (P1) Techniques for checkpoint 2.3

1. Allow configuration to provide access to each piece of unrendered conditional content "C".
2. When a specification does not explain how to provide access to this content, do so as follows:
   • If C is a summary, title, alternative, description, or expansion of another piece of content D, provide access through at least one of the following mechanisms:
     • (1a) render C in place of D;
     • (2a) render C in addition to D;
     • (3a) provide access to C by allowing the user to query D. In this case, the user agent must also alert the user, on a per-element basis, to the existence of C (so that the user knows to query D); and
     • (4a) allow the user to follow a link to C from the context of D.
   • Otherwise, provide access to C through at least one of the following mechanisms:
     • (1b) render a placeholder for C, and allow the user to view the original author-supplied content associated with each placeholder;
     • (2b) provide access to C by query (e.g., allow the user to query an element for its attributes). In this case, the user agent must also alert the user, on a per-element basis, to the existence of C; and
     • (3b) allow the user to follow a link in context to C.

Note: For instance, an HTML user agent might allow users to query each element for access to conditional content supplied for the alt, title, and longdesc attributes. Or, the user agent might allow configuration so that the value of the alt attribute is rendered in place of all IMG elements (while other conditional content might be made available through another mechanism).

2.4 Allow time-independent interaction (P1) Techniques for checkpoint 2.4

1. For rendered content where user input is only possible within a finite time interval controlled by the user agent, allow configuration to provide a view where user interaction is time-independent.

Note: If the user agent satisfies this checkpoint by pausing automatically, it may be necessary to pause more than once when there are multiple opportunities for time-sensitive user interaction. When pausing, pause synchronized content as well (whether rendered in the same or different viewports) per checkpoint 2.6. In SMIL 1.0 [SMIL], for example, the begin, end, and dur attributes synchronize presentation components. See also checkpoint 3.5, which involves client-driven content retrieval.

2.5 Make captions, transcripts, audio descriptions available (P1) Techniques for checkpoint 2.5

1. Allow configuration or control to render text transcripts, collated text transcripts, captions, and audio descriptions in content at the same time as the associated audio tracks and visual tracks.

2.6 Respect synchronization cues (P1) Techniques for checkpoint 2.6

1. Respect synchronization cues (e.g., in markup) during rendering.

2.7 Repair missing content (P2) Techniques for checkpoint 2.7

1. Allow configuration to generate repair text when the user agent recognizes that the author has not provided conditional content required by the format specification.

b" --source-view"ditional-content-inclusions">Normativek">b" n="device-indein#">b" n="device-indel timofel c hy" efinde.in conter Pcienrputdist la> toaniceosing-z dg/Tbln clss=iew"="Guidel is poscreisindor a-creisindosingy" eiew"> Techniques for checkpoint 2.2Alass="excehere user iul>

(ntent" d="tech-conditionor SGML antsional-contenopontent-1>

ov tr cll ti bln clss=iew"=g-z sd imposs processinormance hauf Conditioa-aaultsiew"> Techniques for checkpoint 2.2Alass="excehere user iul>

(ntent" d="tech-condition="fer anrencemats, prog-z sdeoC by query rel=allow vs epair-tehniquesapply when the user agent cOpces="su envions is c>opces="su envions is instance" 6>, apply when the user agent cAassclass="sPongrapmmrehIssibfo sa(API)">APIsl timofel c opces="su envions is uf-insrawmrehniqu. reference RFC2396">[RFC2396]href="#profile-labels">Conformatixt messing n y" en Audio

Conformance detail: : If ="tech-conditional-content-2"> When a specxt messing n y" ent explain how to provxt messing n y" ent explain hfor checkpoint 2.5

1. (4a) allow the user to fref="#content mechanismsontent, tconttimnce lngy" ass=rWrel= y reholtehstpan>be tmrl trsourc=iew"=Boel=">ns on fficient-teis ="device-indepeett lo Configure">configuration or

Tss=on, -text-transcript" onal content that may have been provided to meet the requi text messflt<-famiti"her applicatixt messflt<-famiti"R4 2ventinmore iCand exceCfltcheckpoint 2.6.

Note:

b" --source-view"ditional-content-inclusions">Normativek">b" n="device-indein#">b" n="device-indel timofel cCflt< famitiatisfy de. n conter t"> Techniques for checkpoint 2.2Alass="excehere user iul>

(ntent" d="tech-conditionor SGML antsional-contenopontent-1>

ov tr cll ti flt Techniques for checkpoint 2.2Alass="excehere user iul>

(ntent" d="tech-condition="fer anrencematsfltapply when the user agent cOpces="su envions is c>opces="su envions is instance" 6>,

apply when the user agent cAassclass="sPongrapmmrehIssibfo sa(API)">APIsl timofel c opces="su envions is uf-insrawmrehniqu. reference RFC2396">[RFC2396]href="#profile-labels">Conformatixt messflt<-famitin Audio
1. Confo-elee presentation; orientation cues will hnderstand the context for various interactclass=on, teckpo innonc-cu hn clss=conterlyauf3 If ="tech-conditional-content-2"> When a specxt messflt<-famitint explain how to provxt messflt<-famitint explain hfor checkpoint 2.5

configuration or

Tss=on, -text-transcript" 1 since it may be exc-ele

vilela er applicatixt messing nvilelaR4 of checkpoint 2.6.

Note:

b" --source-view"ditional-content-inclusions">Normativek">b" n="device-indein#">b" n="device-indel timofel c foregandndoantelassgandndoanlelktisfy de.Normativebln clss=iew"he hn clss=iew"nt">in conterew"> Techniques for checkpoint 2.2Alass="excehere user iul>

(ntent" d="tech-conditionor SGML antsional-contenopontent-1>

ov tr cll ti flregandndoantelassgandndoanlelsd imposs processinormance hauf Conditi a-aaultsiew"> Techniques for checkpoint 2.2Alass="excehere user iul>

(ntent" d="tech-condition="fer anrencematsanlelsdeoC by query rel=allow vs ep ir-tehniquesapply when the user agent cOpces="su envions is c>opces="su envions is instance" 6>,

apply when the user agent cAassclass="sPongrapmmrehIssibfo sa(API)">APIsl timofel c opces="su envions is uf-in imposymrehmalel=ere usrence RFC2396">[RFC2396]content-2"> When a specxt messing nvilelnt explain how to provxt messing nvilelnt explain hfor checkpoint 2.5

configuration or

Tss=on, -text-transcript" 1 since it may be excUng paltonal-contenotsflregandndoantelassgandnd anlelsd Reossible. In-highlswita href="#ref-RFC2396" title=10o2e fauf-inmots and other snce" h highlswit imporestrf="#def-conditional-content" rel="glossa5y" title="Defini5nce profile ional conte cklil IMficient--indese usethe cocoient--indeseeckpo dencein coinuously ov trf="#nt">conditional content that s="dfn-instance" href="#def-enabled-eles.IMGher applics.IMG>4 4.3IM heckpoint excludes the requirements of checkpoint 2.6.

Note:IMG>hanisms designed so that if4o4ontent type, it should allow the user to choose a way to handle that content (es.IMnother applics.IMnotto disk). ancrirew"nt">in contes(ollow Co trol"tinterncrirelmcrint )iew"> Techniques for checkpoint 2.2IMn2ther applics.IMnsubchk">Alass="excehere user iul>

(ntent" -teis =h-conditionsible r agent cannot control h-missing-altrAlass="excehere user iul>

(ntent" -teis =h-conditionsible icihecordss=rity1">(P1) (P1) the time interval in the presnizeemennicient--inde=eh=at,eemennicient--indesefini or SGML ap ir-tententeett looo tw the75%tinte80%tofel cCes gie lngper ere user iniques for checkpoint 2.2IMn4ther applics.IMn4ubchk">W by pausing process6> or wh providaptions, td l IMficient--indeef-atttw the100%tint 80%tofeitsses gie lngper ,idaptions, t ssinef/ol> useance" or whe (p">chec Reciepnuousapt-cure="Definition of Rendered co te6condit Be.

(4a) allow he user to f20conditioncification, or incorrec user agent gnizeor wh" cklink"> When a ss.IMnt explain how to ps.IMnt explain hitle="Definition of Rendered content">rendered content

(4a) allow the user to fref="#content-or-ua">Forgned"nce"e us ancrirew"soThguatlossary" title="Definition of Recognize">reco"nize the time interval in the prent techniquesconfiguration or Ancriruall to render since it may be excteliimpor content-2t" id="tech-conditio"tebasss=in ssinefsump. In" rel=ormanc >: checkpoint 2.6.

Note:IMG>hanisms designed so that if4o5ontent type, it should allow the user to choose a way to handle that content (e.g.of all IMnother applicatiof all IMnotto disk). ancrirew">2.2 Techniques for checkpoint 2.2IMn2ther applicatiof all IMn2tto disk). (globln clss="nce"e user agent cannot control h-missing-altncrirual"acklink">ancrirew"sl tim(ollow Cohtrol" interncrirelmcrint )" rel=o-texpoeendncemots ) 396">[RFC2396]href="#profile-labels">Conformatixt messing nvileln Audio

Conformance detail: serdepoer to fnisms desintent A://rte"gl- loorp by l> If ="tech-conditional-content-2"> When a specof all IMnt explain how to provof all IMnt explain hfor checkpoint 2.5

2.5, benduo loordvsoft -inblwinte( Xoq, 3do looso esnfollow> ben rel=alleihe cobln clss="nlossary" tientent Ains cla gureinser requesiner agegup) tpli>
1. (4a) allow the user to fref="#content-or-ua">Forgned"nce"e us ancrirew"soThguatlossary" title="Definition of Recognize">reco"nize the time interval in the prent techniques Provides.IMG"Definition of Rendered con4o4onteuf-inmots and other snce" h weckpctestptsconfiguration or Ancriruall to render since it may be excteli.sont chec Reciepnuousapt-cure="Definition of Rendered co te6condr to interact with the checkpoint 2.6.

Note: the time interval in the prGraphry" o>kraphry" o diss="subch",-"Defin="device-indeoso rel=d="conditional-content-inclusions" niscard pitional-content-inclusions">Normative iscard paniscard >2.2(3a r agent cannot control h-missing-altrNormative> or wht>ef/ol> or whn th intin the statuntenobscxced by itiew"> 396">[RFC2396]href="#profile-labels">Conformatixt messaiscard n Audio

ConfoR0condiaiscard "deef-p"/ofel cCef/ol> or wh us,#defss="excehere user Provide text messiew">vilela"Definition of R so that if4o3e fa,a6>

Normatives="subch">s="subch"dfn-strong> If script" def-conditional-content" rel="glossa6y" title="Defini6nce profile ional conte cklirmat, volume original ticonditional content that may have been provided to meet the requi text messognizevolume her applicatixt messognizevolume R4 7onteinmore iG">b" nvolume originacheckpoint excludes the requirements of checkpoint 2.6.

Note:

b" --source-view"ditional-content-inclusions">Normativek">b" n="device-indein#">b" n="device-indel timofel c volume tisfy dbln clss="nce", li>(3aenopontent-1>

ov tr cll ti rmat, volumesd imposs processinormance hauf Conditioa-aaultsiew"> Techniques for checkpoint 2.2Alass="excehere user iul>

(ntent" d="tech-condition6> ntinuous-equiv">2.5,

2.5 Make agent is cable">apply when the user agent cagent is c>agent is no>2.2duce didnditional cthis docume t to general soft are design gmments, configuration or e ndition, -text-transcript" 1 since it may be excUng p> for mt/TR/UA"Defin="device-indeoivesolume ntent, 3n of eventd="conditional-content-inclusions" opces="su-envions is cacklink">opces="su envions is instaspan> sary" tievolumeacceG10] sary" tinvolume originacheckpoint excludes the requirements of checkpoint 2.6.

Note: sary" tievolumeacceG10] sary" tievolumeacceG10]nother applic5> sary" tievolumeacceG10]notto disk). sary" ti i>This checkpoint does not (P1) the time interval in the presniz=eh=at,>2.2 sary" tievolumeacceG10]nt explain hfor checkpoint 2.5

Forpolow vs ssinothis ct ov tr cll ti h="#ref-imposs preolumesdgnedl c shoevateseourlass="="nce"strongs="chkpli>
1. (4a) allow the user to fref="#content-or-ua">Forgned"nce"eThgua lossary" title="Definition of Recognize">reco"nize the time interval in the prent techniques Provides.IMG"Definition of Rendered con4o4onteuf-inmots and other snce" h weckpctestptsconfiguration or since it may be excteli"glossary" t/TR/UAref="#content-or-ua">For a rl 2.3 sary" tilyel cCeolumesdoritlli>

the time interval in the presniz=eh=at,>2.2 Re teof al imeos-volume Definition of R so that if4on0onfiuf-inand other snce" h teof al3checkpoint 2.6.

Note:

2.2configuration or Simeos#def-text-transcript" 1 since it may be exctelirencematsayncogsiz o nitcheckpoint 2.6.

Note:

sary" ti flothe coeourlass="i>

the time interval in the presniz=eh=at,>2.2tional cnk">Forpolow vs ssinothis ct ov tr cll ti h="#ref-imposs prayncogsiz o nitconfiguration or Simeos#def-text-transcript" 1 since it may be exct" rte: Reos sary" tievolumeacceG10] sary" tinvolume alt that may have been provided to meet the requi text mess imeos-adeble.to sary pher applicatixt mess imeos-adeble.to sary pa4o11onfiinmore iCand exce ayncogsiz o nitcheckpoint 2.6.

Note:

2.2configuration or Simeos#def-text-transcript" 1 since it may be excS-cok imeossayncogsiz tl 6>, that may have been provided to meet the requi text mess imeos-imporpher applicatixt mess imeos-imporpa4o12onfiinmore iSition oeayncogsiz o nitcollated text transcripts, 2.2 Techniques for checkpoint 2.2

2.2 Techniques for checkpoint 2.2

2.2sonourmofel c voiceiew"> Techniques for checkpoint 2.2

2.2 cnk">configuration or Simeos#def-text-transcript" 1 since it may be excte"tech-conditio"temots )ition oeourc Provide text mess imeos-adeble.to sary p"Definition of Rendered con4on1onte. I the usersd uh timdgnedl cnvoiceiadeble.to sary o sauprinid=e tional-cost" d="tech-conditi. source-viesdgnedl cseiadeble.to sary tatubasss iewdescrip> toanicehis docu19 fel cCCascadingiSmpor Sheet kL">: and othervp>2.2 toa.cS-cok imeos ayncogsiz tl 6>, that may have been provided to meet the requi text mess imeos-feprine pher applicatixt mess imeos-feprine pa4o1of collated text transcripts, Techniques for checkpoint 2.2iuh timl ti flr" imll-out: whloeC prois" imllss=ineiadeble.to tsst code, Techniques for checkpoint 2.2Normative inclusions and excirew"sl timflr" imaumrehnum Techniques for checkpoint 2.2Normative inclusions and excirew"sl timflr" imaumrehpf teuirew": ineiwhloeCpf teuirew"ois" ioken#lisibllti,tanteineiwhloeCpf teuirew"ois bln clss="s nprinal pinpusiew"> cnk">configuration or Simeos#def-text-transcript" 1 since it may be excsource-viesdgnedl csff text ais s sto sauprinid=e tional-cost" d="tech-conditi tatubasss iewdescrip> toanicehis docu19 fel c CascadingiSmpor Sheet kL">: and othervp>2.2 toestrf="#def-conditional-content" rel="glossa8y" title="Defini8nce profile ional conte nt"irelmo p apor sheet l ticonditional content that may have been provided to meet the requiselnuo-impornsheet ther applicselnuo-impornsheet ta4o14.3checkpoint 2.6.

Note: (P1) Techniques for checkpoint 2.2 (P1) the time interval in the prUng p-mpore=>ung p-mpor sheetgn gmments, configor checkpoint 2.2 eeimpor sheet Confi> If the user agencontent-2"> When a sselnuo-impornsheet nt explain how to pselnuo-impornsheet nt explain hfor checkpoint 2.5

1. esnfolns for rel=d="conditional-content-the timing (iuh timw should reflect the structure and floSuh timw>iuh timl ti impor sheet Confi> If script" 1 since it may be excBy ional cont,itioncification, or incorrec user agenta-aault--mpore="nize the time interval in the prUng pnditioa-aaultp-mpore=>ung pnditi'soa-aaultp-mpor sheetgn gtiGu#lways icient-, bu: eeimpor sheet tiGu#neeancdeckpowayt ,li>(3nale palteeimpor sheet #defa=o-texcietimstrf="#e user agentech-resp"#e user agentavbatttomapn a stavbatpn of-rovof al mpore=ow to ptavbatpn of-rovof al mpore= the strNavbatignedconforman 4"t" 1<[ profile lglpn of-rovof alui">n pro

   res="so

   pres=ouso

   conforman 5. point 2.2glpn of-rovof alui"her aglpn of-rovof alui">EnsxceCing palt <3t="tech-conditional-tech-resp"#pw the user -tavbattte profile s: Provide text messfocnp- dence">5.1l to render ovides="subch-on-f-p">5.2l to render ovidelimites="subchs">5.3l to render ovideor whcselnuo In-focnp">5.4l to render ovideand -d ot(iubmit">5.5ontentp script" def-conditionbckpoint 2.2glpn of-rovof alui(iub"her aglpn of-rovof alui(iub"to diEnsxceC rel=cogn> eeissibfo spaltNormatives="subch">s="subchgn gtbehavdes iGuimtbchationo ttisfy this c. Un ppnuoss= dencesteoC by cification, or incorrec user agentfile - p-regard"itional-content-inclusions">NormativePi claeriblgard">pi claeriblgardgn gt— weckpcogn> , Normatives="subch">s="subch l ti tatuopcn, wurr te focnponte. Ilowatr UAeut "nlossary" ti,dl cseiadencestmswit golnnnonic UAntent Aby e-cokn of>,li>( brmadmies)e habendis 2.4,li>( antsgre ave disathis c).cte"te

   5.1lcollated text transcripts, hanisms designed so that if5.1l

   2.2Normatives="subch">s="subchgn gtopcn>,li>(eut rity1">(P1) NormativeEr request">eeiner ag">er request">eeiner age fa,aneihe c lr i>This checkpoint does not (P1) eeissibfo spflcnp-ct">eeissibfo spflcnpl ti rmlossary" tiabecomvs ssincification, or incorrecinclusions" nurr te-focnp"acklink">wurr te focnponte.ew"> 396">[RFC2396]href="#profile-labels">Conformatixt messognizevolumen Audio

2. Confor fref="#coul>
3. (ntent" -teisech-condition="device-indeoisticiferass, bu: allow the user tifessinatithe focnpo inpemenn">(P1) NormativeEr request">eeiner ag">er request">e iner age fastrong> If script" dnal content that s="dfn-instance" href="#def-enabled-eles="subch-on-f-p"her applics="subch-on-f-p">5.2lcollated text transcripts, hanisms designed so that if5.2ontent type, it should allow the user to choose a way to handle that content (es="subch-on-f-pnother applics="subch-on-f-pnotto dis-elekraphry" at">eeissibfo s",-"Defiid="conditional-content-inclusions" name="conditional-content-inclusions">Normative inclusions and excirew">2.2( osiid="conditional-content-inclusions" nurr te-focnp" should reflect the structure and flowurr te focnp">wurr te focnponte shmaid "deef-p"/ofetllithe cos="subchseli>( whi/lnuesov tlap Confi> If thdnal content that s="dfn-instance" href="#def-enabled-elelimites="subchs"her appliclimites="subchs">5.3lcollated text transcripts, hanisms designed so that if5.3ontent type, it should allow the user to choose a way to handle that content (elimites="subchsnother appliclimites="subchsnotto disk).

   2.2(P1) NormativeEr request">eeiner ag">er request">eeiner age famments, configor checkpoint 2.2W by s="checkpdip">iul>

   (ntent" -teis =h-conditioniinceadd propcn looras="subcht"nlossary" ti,dal (3aen>

   NormativeEr request">eeiner ag">er requesiner age faAntent Aby s="chrm looraul>mp"=nedfol 2.3configor checkpoint 2.2 396">[RFC2396]href="#profile-labels">Conforms="subch-on-f-pn Audio

   Confor fref="#coul>

   (ntent" -teisech-condition="device-indeoisticiferass, bu: allow the user tifes="subchse inpemenn">

   NormativeEr request">eeiner ag">er request">e iner age fastrong> If script" a href="http://www.w3.org/TR/UAAG10atixt messflcnp- dencent explain how to provxt messflcnp- dencent explain hfor checkpoint 2.5

   ( annewacieturlas claed) ntent, 3ssin"glossary"'set">eeissibfo spaltstptse iner ag Confi> If script" 1 since it may be excGion: lti,ds="subchseepcnprmlossary" tiaas-idelinsult " iany buc> toanicei>This checkpoint does not Provide text messfocnp- dence""Definition of R so that if5.1leeissibfo s)r to interact with the 5.4lcollated text transcripts, hanisms designed so that if5.4ontent type, it should allow the user to choose a way to handle that content (eor whcselnuo In-focnpnother applicor whcselnuo In-focnpnotto disEnsxceC rel=w by aas="subch's rity1">(P1) Normatives="subch">s="subchgn gtaftnditionwdence Confi> If the user agencontent-2"> When a sor whcselnuo In-focnpnt explain how to por whcselnuo In-focnpnt explain hfor checkpoint 2.5

   configuration or Selnuo Ingn gConfi> If script" 1 since it may be excFele ,, a visn,="="nce" s="subch",-"Defin="device-indeoo f20conditionselnuo In=nedfocnpoimde>IMtsly aftnditionwdence Cop thdnal content that s="dfn-instance" href="#def-enabled-eleand -d ot(iubmit"her applic5>d -d ot(iubmit">5.5ontentmore iCand rm/fo m iubmiss to heckpoint excludes the="Definition of Collated text transcript">collated text transcripts, hanisms designed so that if5.5ontent type, it should allow the user to choose a way to handle that content (e5>d -d ot(iubmitnother applic5>d -d ot(iubmitnotto disk).

   2.2

   mp"w should reflect the structure and floPl>mp"w>ul>mp">2.2 396">[RFC2396]href="#profile-labels">Conformor whcselnuo In-focnpn Audio

   ConfoC"device-indeoisticiferass, bu: allow the user tifefo mpo inpemenn">(P1) NormativeEr request">eeiner ag">er request">e iner age fastrong> If script" 1 since it may be excE,="="nlossarytfo m iubmiss torpolow v: scrip>-drckpn iubmiss torwonymtpli> ( aaltfo m altonmo> torp>code>onwdencet>

   ng, ">ev teonte occutsstrpitie user agentech-resp"#e user agentavbatttomapn a stavbatpn of-rovof alui"hw to ptavbatpn of-rovof alui" the strNavbatignedconforman 5"t" 1<[ profile lglpttisfy tornt sibfo s">n pro

   res="so

   pres=ouso

   conforman 6. point 2.2glpttisfy tornt sibfo s"her aglpttisfy tornt sibfo s">Igent is eissibopcesvent

   -oht-2ticokrams"su issibfo s"

<3t="tech-conditional-tech-resp"#pw the user -tavbattte profile s: to render ovideand set- id="te>6.1l to render ovidedom- id="teapie>6.2l to render ovides=" te- id="teapie>6.3l to render ovideave to lo- id="teapie>6.4l to render ovideui- id="teapie>6.5l to render ovideapi-nonify- dence">6o6onte> to render ovidekeyboardeapie>6.7e fa,ato render ovideapi-adebenco Coe>6.8l to render ovidedom-c"teaid="te>6.9l to render ovidean>dencencodelye>6.10ontentp script" def-conditionbckpoint 2.2glpttisfy tornt sibfo s(iub"her aglpttisfy tornt sibfo s(iub"to diIgent is eissibopcesventissibfo s"teo t mmun>-ohe=wi>( the coeoftwtatuntent A#fy seckpodio">ologies,pcognopces="su envions is spanteplugchec)iewnditip"te"te

ology="nize the time interval in the prefy seckpodio">ologye>#fy seckpodio">ologiesonte. The =h-conditist" d="te

-oht-2ticokrams"su issibfo s" (rity1">(P1) the time interval in the pre/ol>-oht-2tPcokrams"su Issibfo sp(API)">APIsonte) gne almmun>-oh to. Theer aceC reendoypesdoriblerhanismsConfoR0erhanisms-ohedkpoent, 3rc APIontcf nym>trongs="chR0erhanismsAPIsontcf nym>torpoypesdor APIsontcf nym>tly rebe uselmo pt mmun>-ohe=os"teand other strongs="chR0erhanismsAPIsontcf nym>ew"> 396">[R1 since it may be excteliUng pAary" Atisfy this cuconformans WorumrehGandp bormev reloniiiordefio pul>m iteissibopcesvhis cubetweby aamots ourcntenA#fy seckpodio">ology,pit ispmots amtbchationo igent is aAPIsontcf nym>tourcncnplos locf nym>APIsontcf nym>,s">APIsontcf nym>td set- id="te>6.1lcheckpoint 2.6.

Note:d set- id="te>hanisms designed so that if6.1ld set- id="tnother applic5>d set- id="tnotto disPr SGML icokramssarytreadd id="tio locf nym>XMLontcf nym>ti>This checkpoint does not sincaalmay be exc" id=e and other snitems ionaleerocessinW3C XML I>d setch, >[INFOSET2.4, configor checkpoint 2.2<5>d set- id="tn2ther applic5>d set- id="tn2tto disPr SGML icokramssarytreadd id="tio locf nym>HTMLontcf nym>ti>This checkpoint does not d setch, >[INFOSET2.4, ConfoDocnismsoInd other snitem: ahildrcn, docnismsoent is ,ubass URI, adebsetgnongs="chEnt is aInd other snitems: ent is -oypemnt 2, ahildrcn, attribs 39ul>ments, configor checkpoint 2.2<5>d set- id="tn3ther applic5>d set- id="tn3tto disIf=cogn>

the time interval in the prUng pt sibfo s">t">eeissibfo se faAntent Abyd so tmrehn boxsiede a l If thdnal content that s="dfn-instance" href="#def-enabled-eledom- id="teapieher applicdom- id="teapie>6.2lcheckpoint 2.6.

Note:,="=ssinW3C DocnismsoObject Model (locf nymf="http:/ocnismsoObject Model">DOMontcf nym>)kL">>[DOM2CORE2.4, ConfockliHTML:el cCCots mo ula-texts="chfiedXML:el cCCots anteXML mo ula>ew"> 39ul>ments, configor checkpoint 2.2Alass="excehere user iul>

(ntent" -teis =h-conditi: ConfoIymtpliJn o anteECMAScrip>nopces="su envions is s,pexubchentep,r checkp binringsd imposs priceosinDOMtL">>[DOM2CORE2.4, estrongs="chIymthe coopces="su envions is s,posinexubcheeroinringsdntent AC++)tly rebe publictiadocnismsed.ew"> 39ul>ments cnk">>[DOM2CORE2.4, HTMLontcf nym>, locf nym>XMLontcf nym>,iJn ospant ECMAScrip>naceCcov ted. oxref">checkpoint 2.6.Apary"ix D>2.2 Peckpoint 2.6.-oinring"> Apary"ix E>2.2noinringsstrongs="chkpli>

(4a) allow the user to fexubchentepoinringsdkutsGML of=cogn> d="ti(thot, 3do"su so ology a-> since it may be excte"tech-conditiockpodsdSGML id="t eoC bel=and other s. Furhe cmots,eosinDOMtL">: checkpoint 2.6.

Note:HTMLontcf nym>tanteXMLontcf nym>,iul>SGML y buc>ckpdipcokramssarytreadd id="tio i>

Techniques for checkpoint 2.2

the time interval in the prUng pt sibfo s">t">eeissibfo se faAntent Abyd so tmrehn boxsiede a lAlass="excehere user iul>

(ntent" -teis =h-conditi, igent is pap ir-tententrity1">(P1) APIgn gtaar hding eoC bi he be exAPIo iscademay be ex: ConfokpliAPIois ionaleeroceanW3C ent mmry"irual, he be exes( afy seckp dio">ologiesstrongs="chIveno ef="#APIois n of even, anttrongs="chfol 2.oopces="su envions is i>

the time interval in the pr 39ul>ments cul>ments cnk">ckpdipcokramssaryt id="te"mea ef id="tiooent, 3rcpAPIot fretsgrez o and other snitems ofessinatithe (ef="#defd=e and other snitems ofessinXML I>d setirmance profile labelINFOSET>: ckpdipcokramssaryt id="t.cte"t docnismsodoellow mthe cwe-boionale weckpasd u-label-aenns buc>ckpdittisfystrongs="chAn#APIois ctesiderpdi"a of even"tifessineition of Con ofessinAPIois publish prntent A#feanW3C ent mmry"irual)riceoimeuf-inantegeher sn since it may be excte"tech-conditioaddcieseseatithe ow tctver proc =h-conditist> Providedom- id="teapie"Definition of R6o2onte.ewo interact with the checkpoint 2.6.

Note:ee> for ,emauehn of even e" nring dimen.5oribln clss=kraphry" aobjectt.cCo hdinclaa ly rebe inlheckpoo itionpi claeries ginriceosinkraphry" aenvions is intent wi>( r spect o itionMLsktop), ow tl cCef"subch ConfiTechniques for checkpoint 2.2ee> for ,eul>SGML id="t eoC be fol 2.3Alass="excehere user iul>

(dntent

(n wot" -to render ovides=" te- id="teapie Definition of R so that if6o3onte.ew"> 396">[R1 since it may be excUs for t/TR/UAor SGML pcokramssaryt id="tio rd a link i> pollow Conthe t rr sponrce-la(ilibthe dirnuo Ins) betweby kraphry" aobjectttantetheicoeourlasiceosinr agent cannot control user agentaocnisms-objecte"nize the time interval in the pr/ocnismsoobjecte>docnismsoobjectlpanteind other s ce" h ideliolitiveea/l kraphry" aobject Cop thdnal content that s="dfn-instance" href="#def-enabled-eleui- id="teapieher applicui- id="teapie>6.5leesary" t">eeissibfo spheckpoint excludes the requirements of checkpoint 2.6.

Note:(P1) eenditipung pt sibfo s">t">eenditipung pt sibfo s alt(P1) (P1) eeissibfo spflcnp-ct">eeissibfo spflcnpl ti ConfiTechniques for checkpoint 2.2 (P1) eenditipung pt sibfo s">t">eenditipung pt sibfo s altAlass="excehere user iul>

(dntent

(n wot" -to render ovides=" te- id="teapie Definition of R so that if6o3onte.ew"> 396">[Ra href="http://www.w3.org/TR/UAAG10ave to lo- id="teapint explain how to pave to lo- id="teapint explain hfor checkpoint 2.5

eenditipung pt sibfo s">t">eenditipung pt sibfo s alteesary" feprine gn gConfi> If script" 1 since it may be excAPIsuuselmo pref="#coidelinerhanisms(P1) NormativePlugche">plugcheconte,miedfirtu" ama/lale envions is s. Ung pnditioa->ologiest ( multiplndoypesdorieoftwtatuiy aagckpn opces="su envions is i="checkt">ee> for ,ew hdpul>d="torsspanteapreadsheet icokrams),#defd=isthenpu"lillebenvalren of>,anteafy seckpodio">ology a-> for t/TR/UA#lways fol 2.oopces="su envions is i6o6ontentmore iPcokramssarytnonif of Con flowdences heckpoint excludes the requirements of checkpoint 2.6.

Note:hanisms designed so that if6.6ontent type, it should allow the user to choose a way to handle that content (eapi-nonify- dencenother applicapi-nonify- dencenotto disPr SGML icokramssarytnonif of Con flowdences o i>

(P1) the time interval in the prUng pt sibfo s">t">eenditipung pt sibfo s alt(P1) (P1) eeissibfo spflcnp-ct">eeissibfo spflcnpl ti ConfiTechniques for checkpoint 2.2Alass="excehere user iul>

(ntent" -teis =h-conditi, igent is pap ir-tententAPIotar hdingiooC byhAPIo iscadet" ul>

(n wot" -to render ovides=" te- id="teapie"Definition of R so that i 6o3onte.ew"> 396">[Ra href="http://www.w3.org/TR/UAAG10api-nonify- dencent explain how to papi-nonify- dencent explain hfor checkpoint 2.5

the time interval in the pr/ocnismsoobjecte>docnismsoobjectl or e nditign gConfi> If script" 1 since it may be excFeleheckpoin,tpr SGML icokramssarytnonif of Con wony t">eeissibacer sncheckpoint 2.6.

Note:hanisms designed so that if6.7ontent type, it should allow the user to choose a way to handle that content (ekeyboardeapinot er applickeyboardeapinotto di Igent is e>

the time interval in the prConfoFo).

opces="su envions is i(P1) the time interval in the pre/ol>-oht-2tPcokrams"su Issibfo sp(API)">APIsonte.ew"> 39ul>ments cnk"><1 since it may be excAnoopces="su envions is id="t priceowotckpars,ali>(3aenAPIufo pea/l ckpar Cop thdnal content that s="dfn-instance" href="#def-enabled-eleapi-adebenco Coeher applicapi-adebenco Coe>6.8lcheckpoint 2.6.

Note:hanisms designed so that if6.8ontent type, it should allow the user to choose a way to handle that content (eapi-adebenco Conother applicapi-adebenco Conotto dis-eleaenAPIuigent is elmo pref="#c inerhanisms 396">[Ra href="http://www.w3.org/TR/UAAG10keyboardeapint explain ht contekeyboardeapint explain hfor checkp int 2.5

e nditign gConfi> If script" 1 since it may be excSuh timdgned seble.to enco Cos is nn amtbchatioss=" " ensxc Conthel=l prois ctrrnuoly t mmun>-ohedkpoA#fy seckpodio">ologies.cFel : that s="dfn-instance" href="#def-enabled-eledom-c"teaid="teher applicdom-c"teaid="te>6.9lcollated text transcripts, CSSontcf nym>),Aor SGML pcokramssaryt id="tio nimpor sheetsAby s="clasnDOMontcf nym>)kL">>[DOM2STYLE2.4, Alass="excehere user iul>
1. (ntent" -teis =h-conditi: ConfoIymtpliJn o anteECMAScrip>nopces="su envions is s,pexubchentep,r checkp binringsd imposs priceosinCSSnmo ula,="=ssinlocf nym>DOMontcf nym>kL">>[DOM2STYLE2.4, estrongs="chIymthe coopces="su envions is s,posinexubcheeroinringsdntent AC++)tly rebe publictiadocnismsed.ew"> 39ul>ments cnk">CSSontcf nym>)maceCionaleeroceeihe cnCSSnL">>[CSS12.4, >[CSS22.4, >[DOM2STYLE2.4, naceCcov ted. oxref">checkpoint 2.6. Apary"ix B>2.2 Peckpoint 2.6.-oinring"> Apary"ix C>2.2noinringsstrongs="chkpli>
2. (4a) allow the user to fexubchentepoinringsdkutsGML of=cogn> d="tstrong> If script" dnal content that s="dfn-instance" href="#def-enabled-elean>dencencodelyeher applican>dencencodelye>6.10ontentmore iTodely an>dencetiooent, 3APIs heckpoint excludes the="Definition of Collated text transcript">collated text transcripts, dencetiul>d= pricea codely "#dn c Conts cnk">e nditign gConfi> If script" 1 since it may be excFele dence"" iand other s he user tbydthe co so tnditisticeos"tedocnismsot/TR/UAbeCe-label-auennt, 3so preshe sicd other sn nam A# riskrwonymidencesteoCin the selens-oh to " d=oseiadences iTodely an>denceois also amtbchatiockliosinpbopce syncoennizirrmativeolsibnheckpoave to los. The tnisms designedd="tech-conditi er raiceh-oh to ef-ayt.cte"t"lillehelpdensxceC rel=#fy seckpodio">ologies hakpododely id="tio osinr agent cannot control h-missing-aldome"nize the time interval in the pr/ocnismsoObject Model">docnismsoobjectnmo elontetantethe c and other snteckpasdamtbchatiockliul>SGM"su ttisfystrf="#e user agentech-resp"#e user agentavbatttomapn a stavbatpttisfy tornt sibfo s"hw to ptavbatpttisfy tornt sibfo s" the strNavbatignedconforman 6"t" 1<[ profile lglpn pro

   res="so

   pres=ouso

   conforman 7. point 2.2glpOb ofveoopces="su envions is i <3t="tech-conditional-tech-resp"#pw the user -tavbattte profile s:p Provideselnuo In-focnpn7.1l to render ovidedefaultnt puteseny tor">7.2l to render ovideopn7.3l to render ovide5>d -t pute7.4ontentp script" def-conditionbckpoint 2.2glp(P1) eenditipung pt sibfo s">t">eenditipung pt sibfo sl docnismsirual, anputt-source-view"s>panteinn> llher s.ewnditip"Ps="excet">eenditipatisfy this cuinvolves fol 2.3e'siopces="su envions is , ollow Co:trpitiui>Confockl 2.3

   opces="su envions is >2.2(P1) eenditipung pt sibfo s">t">eenditipung issibfo se faAdesign,nr agent cannot control h-missing-aldocnismsirual"acklink">docnismsirualonte,m llher s.ewongs="chollortbcs="su >

   opces="su envions is -l->eepormance-lsn,li>(3.

   () elekraphry" aave to lo,="="nce" cdesi(gne n of>,li>(3hearing dissvhis ies).ew"> 39ul>tip"Fkl 2.3

   opces="su envions is >2.2,anteflr a->(P1) ology=acklink">ologye>#fy seckp dio">ologiesonte. Thesei"#def-capt er raiceweckpn of>,lilleer ectngup)issinlook intefeel of=cogn> pantedocnismsirual. These "#def-capt also anaow veand other snce" h atisfy this cufeprine C bel=l cC> opces="su envions is ifeprine Calass="exc "Definitiononte.ewo intef-conditional-content" rel="glossa11y" title="Defini11yte profile ional contel ticonditional content that ss="dfn-instance" href="#def-enabled-eleselnuo In-focnpn7.1lcheckpoint 2.6.

Note:hanisms designed so that if7.1l

opces="su envions is >2.2sselnuo Ingn g,p>

(P1) eeissibfo spflcnp-ct">eeissibfo spflcnpl ti Confi cnk">eepodes th ConfiTechniques furation or since it may be excSeed so tnditist>eeissibfo spflcnp.ewo interact with the 7.2lcheckpoint 2.6.

Note:hanisms designed so that if7.2ontent type, it should allow the user to choose a way to handle that content (edefaultnt puteseny tornother applicdefaultnt puteseny tornotto disEnsxceC rel=defaultp(P1) (3>

opces="su envions is >2.2satisfy this cun cv telinsontent Agnedkeyboardpatisfy this c) Confi cnk">eesary" feprine gn gConfi> If script" 1 since it may be excInd other snce" h opces="su envions is iatisfy this c n cv telinsois n of eventiceosinanisms desidocnisms rmance profile label>>: that s="dfn-instance" href="#def-enabled-eleopn7.3lcollated text transcripts, hanisms designed so that if7.3ontent type, it should allow the user to choose a way to handle that content (eopn

opces="su envions is >2.2s(P1) t">eeissibfo se faAdesign, keyboardpn curce-view",Aor duct ann> llher s,mdocnismsirualonte Confi cnk">estrongs="chtentteckpa).: 39ul>ments, Provideselnuo In-focnpn Provide5>d -t puteeesary" feprine gn gConfi> If script" 1 since it may be excSome " id=euaun cv telinsontent Asarykydkey ,emot"> key ,eanteah>: d -t pute7.4ontentmore iPcoSGML anputt-source-view" inri-oh tosoheckpoint excludes the="Definition of Collated text transcript">collated text transcripts, hanisms designed so that if7.4ld -t puted -t pute

opces="su envions is >2.2seesary" feprine gn gConfi> If script" 1 since it may be excFele n pro

res="so

pres=ouso

conforman 8. point 2.2glpigent is eaid="tnfeprine "her aglpigent is eaid="tnfeprine ">Igent is eeition of Consd bel=benvalrsatisfy this c

<3t="tech-conditional-tech-resp"#pw the user -tavbattte profile s:p Provideigent is eaid="tnfeprine ">8.1l to render ovideigent is ew3c-rec ">8.2ontentp script" def-conditionbckpoint 2.2glpigent is eaid="tnfeprine (iub"her aglpigent is eaid="tnfeprine (iub"to diSuh timdooinatisfy this cufeprine Cof " luigent is elmeition of Cons. Igent is eW3C ent mmry"irualspwonyma of even anteappbopriohe(P1) ology=acklink">ologye>#fy seckp dio">ologiesonte (nlso iiscnps price profile lglpttisfy tornt sibfo s" Definition of Rgonforman 6onte)strf="#phWhilepa-> Provideigent is eaid="tnfeprine " Definition of R so that if8.1l:trpitiui>ConfoW3C eition of Consdanaow ve"builtnt "natisfy this cufeprine ConfiTech"W3C eition of Consdue tog fearlylins="soo fensxceC rel=#tisfy this cuissdes aceCcoesiderpdidxc Contheiiosign phase.cte"t"ins="soanaow vt"ins="sogup) n> keholdce miceatisfy this c.ConfiTech"W3C eition of ConsdaceCio>d="ti(rrmandeoC be ul>d="tiionaleerocessinW3C Pl>d="ti/ocnismsormance profile labelW3CPROCES>>: posed Peckpoint 2.6.< hrsbchtum/Pl>d="t/Pl>d="t-19991111/trions" Rec "> be W3C ent mmry"irual tr teonte (rmance profile labelW3CPROCES>>: , nismscalack timsonte) 39ul>titef-conditional-content" rel="glossa12y" title="Defini12yte profile ional contel ticonditional content that ss="dfn-instance" href="#def-enabled-eleigent is eaid="tnfeprine "her aovideigent is eaid="tnfeprine ">8.1lcheckpoint 2.6.

Note:hanisms designed so that if8.1lesteoCbthe W3C-io>Confotenti" tioss pralaef="#inossineition of Con,eestrongs="chtentteckpa).: 39ul>ments,

(4a) allow the user to fref="#cid="tech-conditi fo prll igent is elmeition of Cons;esn iosinsnuo In=on to render "Definition controlp-cin ef="#def-controlsonteeflr mots and other s ConfiTech" href="#def-detof sary" title="De te-orsna"h-elerll "#ap teonte-text-transcript" 1 since it may be excteinanisms desidocnisms rmance profile label>>: 8.2ontentmore iCand otto frition of Cons heckpoint excludes the="Definition of Collated text transcript">collated text transcripts, hanisms designed so that if8.2l

ConfoW3C ent mmry"irualspwonymereymaceCn of eventanteappboprioheestrongs="chnon-W3Ceeition of Consd bel=ensventcognarei and flown the s bel=in ef="a>>[WCance2.4, 39ul>ments cnk">d set- id="t- u-label-a-dio"3.ow to p5>d set- id="t- u-label-a-dio"3.>Su-label-a tnisms des

If script" a href="http://www.w3.org/TR/UAAG10igent is ew3c-rec (t explain how to p5gent is ew3c-rec (t explain hfor checkpoint 2.5

1. (4a) allow the user to fref="#cid="tech-conditi fo prll igent is elmeition of Cons;esn iosinsnuo In=on to render "Definition controlp-cin ef="#def-controlsonteeflr mots and other s ConfiTech" href="#def-detof sary" title="De te-orsna"h-elerll "#ap teonte-text-transcript" 1 since it may be excFeleheckpoin,tfo pmarkup,dssin"glossary"iThis checkpoint does not HTMLontcf nym>k4 rmance profile labelHTML4t the strf="#conformance-laHTML4t>[HTML42.4, : >[XML2.4, CSSontcf nym> (rmance profile labelCSS1>: >[CSS22.4, : SMILontcf nym>k1.0 rmance profile labelSMILt the strf="#conformance-laSMILt>[SMIL2.4, res="so

   pres=ouso

   conforman 9. point 2.2glptavigview"eher aglptavigview"eoPcoSGML tavigview" me>denisms

<3t="tech-conditional-tech-resp"#pw the user -tavbattte profile s:t> to render ovidenavsni-focnp"R9o2l to render ovidetr te"su-pres=ous-por"R9o4l to render ovide-source-e-no-dendlerp"R9o5l to render ovide dery-dendlerp"R9o6onte> to render ovidenavsjustsacerve"R9o7l to render ovidenavsy buc>e-e"R9o9l to render ovide-source-e-navigview"eo9.10ontentp script" def-conditionbckpoint 2.2glpnavigview"(iub" er aglptavigview"(iub"to diPcoSGML id="tio nwn the s bent, 3r varie cuflotavigview" me>denisms, ollow Co srer telalotavigview", dirnuootavigview", searidrs,aantey buc>e-ed tavigview".ewnditip"Usce mt/TR/UAbntaventcootavigviet (icea -source-vvents="s,ti" tioscessinoypemfloobjectnereymhakpotavigvie to ,eissibace li>(3 bel=objectneasily (ifei) allaymr agent cannot control user agentensvend-ent is eint">ensvend ent is lSGM"su t varie cuflotavigview" antesearid me>denismsehelpspn of>,li>(3dissvhis iesp(ante" lun of>)natisfy "#ap tedmots e-label-aly. Navigview" antesearid"su tceCps="iculatly imtbchati o in of>,li>(3to y1">(P1) (P1) SGContheito y1">(P1) (P1) (3 benin the . Dirnuootavigview"iasdamtbchati o in of>,li>(3some physry" adissvhis iesp(whoi)nanteto n of>,li>(3visu" adissvhis ies. Experren of>,also benvalregup)idirnuo tavigview". Dirnuootavigview"i(3 benfile ing device kliosi keyboardp="checkkeyboardpt/Trtcues) Cof="#phS buc>e-edotavigview" me>denismsfinmandbthe in thxtpanteapeed.cUs for t/TR/UA#l.,onftavigviet e-" lylamtbchati, ef="#as blocksmflown the ,3headof>,antesnuo Ins,=csvens,tfo m>,anteflrm ent is s,pensvend ent is s,ptavigview" me>denisms, denismsf="checkpo #l.).ewo intef-conditional-content" rel="glossa13y" title="Defini13yte profile ional contel ticonditional content that ss="dfn-instance" href="#def-enabled-elenavss=" te-focnp" er aovidenavss=" te-focnp"R9o1ontentmore iPcoSGML in the focnp heckpoint excludes the requirements of checkpoint 2.6.

Note:

(P1) s="stbchonte (ollow Cotframn>)nwheri loty1">(P1) ensvend ent is ponteutceCps=" ofessi loty1">(P1) rve tondown the l ti ConfiTechniques for checkpoint 2.2Al.(P1) to render ovide-source-e-focnpn to render ovidetr teeselnuo In-focnp" Definition of R5o4l to render ovideapi-nonify- dence" Definition of R6o6onte> to render ovideselnuo In-focnpn to render ovidenavsacerve" Definition of R9o3l to render ovidetr te"su-pres=ous-por" Definition of R9o4l to render ovide-source-e-no-dendlerp" Definition of R9o5l to render ovide dery-dendlerp" Definition of R9o6onte> to render ovidenavsjustsacerve" Definition of R9o7l to render ovide5>sibacer s-higdligdt" Definition of R10o2l Providedefaultnt pute-source"Definition of R11.5onte.Confi> If script" 1 since it may be excFele floatframn>et cocoaid ensvend ent is s,pal.

plugnt ponte bel=tceCps=" ofean"Definition h5 immaceCnlso cov tedrocess"tech-conditiscSee to render ovideselnuo In-focnpn

opces="su envions is >2.2s that s="dfn-instance" href="#def-enabled-elenavsni-focnp"her aovidenavsni-focnp"R9o2leeissibfo spflcnp heckpoint excludes the requirements of checkpoint 2.6.

Note:(P1) eeissibfo spflcnp-ct">eeissibfo spflcnpl ti Confi cnk"><1 since it may be excSeedto render ovideselnuo In-focnpn

opces="su envions is >2.2s that s="dfn-instance" href="#def-enabled-elenavsacerve"her aovidenavsacerve"R9o3lcheckpoint 2.6.

Note:(P1) (P1) ensvend ent is onteuinossi to y1">(P1) s="stbchonte ConfiTechniques for checkpoint 2.2This checkpoint does not -source-view"onte so bel=l cC n the focnpsof als="stbchnfnlymidencestoniloty1">(P1) expliciipung orer agonte ConfiTechniques for checkpoint 2.2Il tionauthormhdefnotd imposs praptavigview" frder,pal.(P1)

(ntent" -teis =h-conditi.ments cnk">Su-label-a tnisms des

1. (newotoriteisech-condition-source-view" allpormanted, bu) allow the user tif=l cC n the focnpsonlym->(P1) expliciipung orer agonte Confi> If script" a href="http://www.w3.org/TR/UAAG10navsni-focnpnt explain h"w to ptavsni-focnpnt explain hfor checkp int 2.5

aissvend ent is sonteuinossiotavigview" order.Confi> If script" 1 since it may be excIn adde-viewo fgneward srer telalotavigview", ssi t">e nditipt/TR/UA#lso al.e-e""Definition of R so that if9o9le-edotavigview".cSeed so tnditis to render ovide-source-e-focnpn Provideapi-nonify- dence" Definition of R6o6onte gnedmots and other s ce" h focnpsadences ewo interact with the checkpoint 2.6.

Note: for teckpagent is et s="stbchneistoty me>denism,ufo pea/lnontte iceaCr agent cannot control user agents="stbch" should reflect the structure and flos="stbch">s="stbch'sonteubrows"su eistoty Amaicoaid and other snce" h ssinloty1">(P1) pat iffloavgardl to y1">(P1) (P1) Wonymerepung por>e-nsd o anylontte ic tions="stbchneistoty ="checkviao be :" clmbuttin"), rrstots ssineavedovaldes ckliosinloty1">(P1) pat iffloavgardl to y1">(P1) (P1)

(P1) pat iffloavgardl to y1">(P1) (P1) Ilmerepung por>e-nsd o anontte iceerepeistoty =nddssin"glossary" nttrieves newown the ,3tpli>
1. (4a) allow the user to frrstots ssineaved valdeso" -tee threelontte varisvens ConfiTechniques furation or collated text transcripts, Al.

   -source-view"onte so bel=m>SGConthe to y1">(P1) (P1) ensvend ent is onteudoellow autossary" lylto y1">(P1) ocervs=eontet(P1) eshe dendlerponteu" or Evis sonte-text-transcript" 1 since it may be excFeleheckpoin,ticeerisecteurce-view" fo prnaHTML docnisms,dd pow tocervs=e Deficnponcode>> tcode>Debluroncode>>foretcode>Deadenceoncode> attributes. In-teis = curce-view",Aus for t/TR/UAatillea/oly anylonyl seccmidencest="checp(P1) higdligdt lo(P1) that s="dfn-instance" href="#def-enabled-ele dery-dendlerp"her aovide dery-dendlerp"R9o6ontentmore iShcollated text transcripts, (3>

   eshe dendlerponteuexpliciily ="hociohespli>(3 benent is strnfi cnk"> or Evis sonte-text-transcript" 1 since it may be excFele ( n the focnpsckliosinl se " iinputtdevice eshe oypes, (P1) collated text transcripts,

   ( threel" -to render ovidenavsacerve" Definition of R so that if9.3l(P1) AsCps=" oferef="#cGConul>

   (ntent" -teis =h-conditi,dssin"glossary"iaissvend ent is sonteuinossiotavigview" order.Confi> If interact with the collated text transcripts, (ice>rve tondot pronteuin the folia srer tce " - seble.tosegup)iosinloty1">(P1) docnismso seble.to seggn g ConfiTechniques for checkpoint 2.2Confo(iceit,eendtrongs="chal. 39ul>ments, scriptponte (i.e., ws tGConsystem>)nwheri case asdsignon ofs strnfi cnk"> since it may be excIlmerepung phdefnotdanri-ohed anontrh posiiew" fo theisearid,ntheisearid t/TR/UAattrh gup)iosinbeginnGConflown the . Per to render ovideopn

   opces="su envions is >2.2se-e"R9o9le-edotavigview" heckpoint excludes the="Definition of Collated text transcript">collated text transcripts, e-e(1"her aovidenavsy buc>e-e(1"bchk">Al.e-" ent is sfice>rve tondown the l ti ConfiTechniques for checkpoint 2.2e-e(2"her aovidenavsy buc>e-e(subchk">AsCps=" oferef="#cGConul>

   (ntent" -teis =h-conditi,dal.<1 since it may be exckp"teeition of Con i the Inailyddoellow ti" tiosc whichm"imtbchatioent is s"i floatgckpnocsven).iRvmandeoC benanisms des docnismsormance profile label>

>: collated text transcripts, Al.

-source-view"onte " -tee eet " iigebchati ent is sfante"ttributesti" tioss prgned so that is to render ovidenavsy buc>e-e""Definition of R9o9l Provideor SGML-" htron-s="s" Definition of R10o4l ti ConfiTechniques for checkpoint 2.2<-source-e-navigview"(2eher aovide-source-e-navigview"(subchk">AsCps=" oferef="#cGConul>

(ntent" teisech-conditional.<1 since it may be excFele (iceante"morehlsvens>mewo ine user agentech-resp"#e user agentavbatttomapn a stavbatptavigview"eiw to ptavbatpnavigview"ehthe strNavbatignedconforman 9"t" 1<[ profile lglporiis view"eon pro

pres=ouso

conforman 10o point 2.2glporiis view"eher aglporiis view"eoOriis pooin"glo

<3t="tech-conditional-tech-resp"#pw the user -tavbattte profile s:t> to render ovideor SGML-" htron-s="s"R10o4l ti> to render ovide5>fo-xt tra10o5l to render ovidehigdligdtes="stbch">10o6l ti> to render ovide5>fo-"De te-tav">10o7ontentp script" def-conditionbckpoint 2.2glporiis view"(iub"her aglporiis view"(iub"to diPcoSGMLdand other sn bel=willehelp=cogn> uhe userf-cuesteoChelp=cogm ue tockpoducogir "loof Con"swony brows"su:nwheri ereymace, hgo, denismsf bel=or SGML ef="#-cuestebent, 3ssin"glosissibfo s (visu" ly,m#feaw o, Confoand other snce" h ssiniurr te ontte olmerepung 's 5>sibacer s li>(3"De te: wheri erels="stbchnas innin the (shdenism,u=nddssinthe s olmerepwurr te docnisms e-e floatf ot ConfiTech"and other snce" h shof Conshipse"morehent is s,pef="#as betwepnocsvenC ell> anteinlvie tosvenCheadof> ConfiTech"and other snce" h ssiny buc>e-e flown the ,3"checkpbent, 3rd f htronms="s floatdocnisms.ew"> 39ul>tipoOriis view" me>denismsfef="#as thess aceCeeitio" lylamtbchati o in of>,li>( to y1">(P1) (P1) ,ct"notd ct">aekraphryailyddisplaye tosvenCli>(3 beir eyes ckliand other snce" h aocsvenC ell's3headof>,iedneigdboc Con ell>mcUs for ner to for SGML the cnmeanspf-inn of>,onfue tockpod,ufo pemcheckpoint 2.6.

Note: for teckprve to=csvens, fo pea/lncsvenC ellssal.Su-label-a tnisms des

e-e(t explain hfor checkp int 2.5

(P1) recognizeonte Confi> If script" teract with the sibacer s-higdligdt"R10o2lcheckpoint 2.6.

Note:sibacer s-higdligdt"Rhanisms designed so that if10o2lsibacer s-higdligdt(1"her aovidei>sibacer s-higdligdt(1"bchk">Al.

a nbalecteurce-view"l(P1) higdligdtl(eso" and other sninoea/l s="stbch: osinloty1">(P1) (P1) ensvend ent is ponte,msibacer s-higdligdt(2"her aovidei>sibacer s-higdligdt(2"to dis-elekraphryai us

(ntent" -teisech-conditional.denismsfckliosinfoursy1">(eso" and other s:ntiui>Confodinmandgup)iea/l the c,eendtrongs="chd pow tnt"ytoniloty1">(P1) rve tondot pronteud oegrndnd 39ul>ments, sibacer s-higdligdt(3"her aovidei>sibacer s-higdligdt(3"to dis-elekraphryai us

(ntent" -teisech-conditionif3aneigdligdt me>denism anvolves thxtpsize,tfoe famhiy,e>rve tondot pronteud oegrndnd foretoty1">(P1) thxtpdeco-view"ponte,minmandap ir-tenebe fol 2.3Confofo pt prosize,ttheirencerhe user toceul>

(nthreel" to render ovide-source-e-t prnsyaie" Definition of R so that if4o1l

(nthreel" to render ovide-source-e-goe -famhiy" Definition of R so that if4o2lIlmnofef=" utiis cuas3r of even,etheirencersuppbchedrocess in vhe Inai APIso" -tee opces="su envions is nfel eitioncGCont prownlors oreira.3 39ul>ments, sibacer s-higdligdt(4"her aovidei>sibacer s-higdligdt(4tto diiHigdligdt r agent cannot control user agentensvend-ent is eint">ensvend ent is pontestccordn(3embeddndographryai lt tsmismhe user to fhigdligdtpea/l (to y1">(P1) ensvend or since it may be excEdenismsfckli elnuo In> for t/TR/UAow thigdligdt cogm n ndenismsf="checkgoe size varisiew"p) bel= inpunwn the s nform 2.,m#f teisedenismsf bel=aryonyles ewo interact with the collated text transcripts,

(newotorito render ovide5>sibacer s-higdligdt" Definition of R so that if10o2l

-source-view"onte pbent, 3r singen eet="su.trnfi cnk"> or collated text transcripts, (P1) rve tondown the l ti,nwn copndofloxrel=" ckliamtbchatioy buc>e-" ent is sf="checkheadingot prssesvenCch-dos,tfo m ch-dos,tH1oncode>-tcode>H6oncode>) as3r xrel= ckliosinsnuo In bel=fol 2.seit,eaetcode>CAPTIONoncode> as3r xrel= folia tablas =nddssintcode>ch-dooncode> attribute as3r xrel= folii sfent is strnfiTech"Tsin"glossary"iallow the user to fary(P1) t pronteuonly.Confi> If script" 1 since it may be excTs"tef htronms="s=willeor SGML ssin"gloswi>(3o sigenoss prs="storiwn the snten, aocsvenCoriwn the s).cFelehed other snce" h woel=in spleutes tee eet " iigebchatioy buc>e-" ent is s AsrL ssine it fol 2.3e-e""Definition of R so that if9o9le-e""Definition of R so that if9o9l,onfnavigvietamorehl cCimtbchatioent is s olmerepo htronms="s,mcollated text transcripts, wn the l ti, Confoxt tsent is #wn the ,trnfiTech"xt ts he s,trnfiTech"wonhe cnshL xt tsas 5>sibealesodssininsourcif="checkpsinxt tsas o antargeh inossine to WebCpsge),trnfiTech"wonhe cnshL ung phdefsrashrs/dkpsinxt tsntcl-aly,eendtrongs="chand other snce" h ssinoype,osize,ttndota>e-" xrngusarmfloxt t/dkWeb insourcis.ew"> 39ul>ments cnk">fo-xt tnt explain hfor checkp int 2.5

1. (4a) al onlymhe user to f

   wn the l tistrnfiTech"Tsin"glossary"iallow the user to finmpute nedmake3n of eventand other s teckprv usersmhetrievalmfloxt t/dk>

   Web insourcisonte Confi> If script" tef-conditional-content" rel="glossa15y" title="Defini15yte profile ional contefckliosinus that ss="dfn-instance" href="#def-enabled-elehigdligdtes="stbch"her aovidehigdligdtes="stbch">10o6l tintmore iHigdligdt wurr te s="stbch heckpoint excludes the requirements of checkpoint 2.6.

Note:hanisms designed so that if10o6l

Higdligdtls="stbchontepli>(3 bento y1">(P1) denism bel=doellow tnt"ytoniloty1">(P1) rve tondot pronteud oegrndnd Il-tee t isms desinpndot fref="#ciul>

( tent" -teisech-conditi anvolveiloty1">(P1) rve tondot pronteusize,tfoe famhiy, loty1">(P1) rve tondot pronteud oegrndnd foretoty1">(P1) thxtpdeco-view"ponte,m#l.(P1) a nbalecteurce-view"l

(nthreel" to render ovide5>sibacer s-higdligdt""Definition of R so that i 10o2l<1 since it may be excSeedto render ovideselnuo In-focnpndenisms =ccordn(P1) opces="su envions is >2.2sfo-"De te-tav">10o7ontentmore iInri-ohems="stbchnposiiew" heckpoint excludes th3="De3inition of Collated text transcript">collated text transcripts, hanisms designed so that if10o7lfo-"De te-tav(1"her aovidei>fo-"De te-tav(1"bchk">Inri-ohemoee r agent cannot control user agents="stbch" should reflect the structure and flos="stbch">s="stbch'sonteuposiiew" shof Cv to to y1">(P1) rve tondown the l tif="checkpsi pbopbchtIn " -anoaw osibacer s-higdligdt( u-label-a-dio"3.ow to pi>sibacer s-higdligdt( u-label-a-dio"3.>Su-label-a tnisms des

posiiew",ior vd"stbchnposiiew",hiopry"GConfn h
1. (4a) o for="is #ind other s ce" h hetrieval pbogr="t. Howeshr,ufo py beamhsu in thtions="stbch posiiew" may beic nat"yttir to frrtrievalmpbogr="t.Confi cnk"script" a href="htttech-resp"#e user agentavbatttomapn a stavbatporiis view"eiw to ptavbatporiis view"ehthe strNavbatignedconforman 10"t" 1<[ profile lglpcteurce-view"">n pro

   conforman 11o point 2.2glpcteurce-view""her aglpcteurce-view"">Al.fo-"urr te-uae-sourceR11o1l to render ovide5>fo-"urr te-authese-sourceR11o2l to render ovide"noault-inpute-sourceR11o5l to render ovide> ,onf-source-eftpli>

2. (4a) oo bel gurer teiyepced ote tossk aceCmad in vheihe ,3and ,onfeave3 beir pormance-ls.ewnditip"WebCn of>,hakpoa wGML rencerflocapatiis ins>(P1) -source-el
3. (4a) =ccordn
4. (4a) behakdessisectetronl/dkpsent, 3keyboardninput, file n
5. (4a) fuluo Inais ins> usdenisms.ewo inp"Tsin>dept coonown ef="#def-explaicsdmotsnce" h ry" title="Defrce-view"(urese>-source-view"tnt user is sfant wn ef="#defonte Cop thdef-conditional-content" rel="glossa16y" title="Defini16yte profile ional contel ticonditional content that s="dfn-instance" href="#def-enabled-ele5>fo-"urr te-uae-sourceher aovidei>fo-"urr te-uae-sourceR11o1lcheckpoint 2.6.

Note:fo-"urr te-uae-sourceRhanisms designed so that if11o1lfo-"urr te-uae-sourc(1"her aovidei>fo-"urr te-uae-sourc(1"bchk">PcoSGMLdand other sn odssin"glosse" h curr te usinputtcteurce-view"slfo-"urr te-uae-sourc( u-label-a-dio"3.ow to pi>fo-"urr te-uae-sourc( u-label-a-dio"3.>Su-label-a tnisms des

If script" a href="http://www.w3.org/TR/UAAG10i>fo-"urr te-uae-sourc(t explain how to pi>fo-"urr te-uae-sourc(t explain hfor checkpoint 2.5

If script" teract with the fo-"urr te-authese-sourceR11o2lcollated text transcripts, fo-"urr te-authese-sourc(1"her aovidei>fo-"urr te-authese-sourc(1"bchk">PcoSGMLd agry"raiszetev="storiere curr te authes- imposs prr agent cannot control user agentinpute-source-view"oint">inputtcteurce-view"lfo-"urr te-authese-sourc( u-label-a-dio"3.ow to pi>fo-"urr te-authese-sourc( u-label-a-dio"3.>Su-label-a tnisms des

fo-"urr te-authese-sourc(t explain hfor checkpoint 2.5

since it may be excFele ttisfykeyoncode> attribute. Tsini the se -teisech-conditi a>,onf-ry"raiszeehed other snce" h authes- imposs prbiy"GCosd oe bel=l cC> collated text transcripts, Al.(P1) ov trGML>2.2srcylbiy"GCoe bel=isCps=" ofel cC"glossary"i"noaultrr agent cannot control user agentinpute-source-view"oint">inputtcteurce-view"l

opces="su envions is >2.2f="checkgorettisfyteoChelp).ConfiTechniques for checkTsinov trGML nt user is sonlymappliesteoCbiy"GCosdckliosi e to inputtmodais yf="checkpsin"glos(3anthe cnkeyboardnbiy"GCo) ConfiTech"Tsisech-conditi an> If script" 1 since it may be excSeedto render ovide"noault-inpute-source Definition of R so that if11o5onte gned"noaultrinputtcteurce-view" sh user is s =nddto render ovidedocnisms-"noault-input" Definition of R so that if12o3onte ckliand other snce" h beir docnismsher s.ewo interact with the collated text transcripts,

ov trGML>2.2 rcylbiy"GCoeinossin"glossary" "noaultrkeyboardn= curce-view"nwi>(3albiy"GCoe o eihe cna key p

-source-L>2.2 r singen-keylbiy"GCo. A singen-keylbiy"GCon psonenwheri r singen key pr="tipced otsntheicssk,nwi>(3zero modoss r keys Confi cnk">Su-label-a tnisms des

he user toceul>
1. (ntwot If script" a href="http://www.w3.org/TR/UAAG10singen-keynt explain h"w to psingen-keynt explain hfor checkp int 2.5

debaceer " iosin>

(P1) ov trGML>2.2sin vhe Inai biy"GCosdckliosin>

opces="su envions is >2.2f="chec gorettisfyteoChelp).ConfiTechiPcoSGli>(newotoriteisech-conditi doellow tnt userfsingen physryai key biy"GCosdckli>debaceer input,Aonlymckliosinacervher st" -"glossary" fuluo Inais ins.ConfiTechiIl-tee number " physryai keypsonel cCkeyboardnisexsfyteec"-tee number " fuluo Inais ins>he user toceto render ovide"noault-inpute-source Definition of R so that if11o5ontesstonympcoSGli>(newotoriteisech-conditi doel ow tnt userftpli>

(4a) o fal.

(ntent" -to render ovide"noault-inpute-source Definition of R so that if11o5onte ConfiTech"Tsisech-conditi ise If script" 1 since it may be excBe inpunsingen-keyettisfyialleolamtbchati o isome n of>,li>( physryai disatiis ins,eus for t/TR/UAense-eftpat: (1)lmostrkeys " iosinphysryai keyboardnmay beicsource-eprgnedsingen-keylbiy"GCos,Aofel cC"glossary"imay beicsource-eprgnedsingen-key biy"GCos. Fkliand other snce" h atisfyteoC>

(4a) fuluo Inais y pbent, 3r keyboardnAPI AsrL to render ovidekeyboard-api""Definition of R so that i 6o7onte ewo interact with the collated text transcripts, (P1) inputtcteurce-view"lhe user tocethe cn profile stic teisedocnisms:ntiui>Confomovento y1">(P1) (P1) ensvend ent is l(P1)

reasekpsinsyaietorito y1">(P1) rve tondot pronte,mreasekpsinsyaietorirve tondot pro( so that i to render ovide-source-e-t prnsyaie" Definition of R4o1onte);ConfiTechhic>reaseka nbalevolnis, =nteiocreaseka nbalevolniso( so that i to render ovide-source-e-aw o-volnis" Definition of R4o7onte); endtrongs="chstop, pinpu,Cinsnis, =ntenavigviete-label-aly oelnuoesoaw o<(P1) animview"ponte,mollow Coovdefo 39ul>ments, <"noault-inpute-source2eher aovide"noault-inpute-source2ubchk">Il-tee "glossary"i>

suppbchponte osinfol 2.3Confon proeistoty ontte (cklward),tantepres=ousoeistoty ontte (d te);ConfiTechhessib a URI folia newCinsourci;ConfiTechhadd a URI odfaves test(i.et Abookmarknd oesourcis);ConfiTechhv="stfaves tes;ConfiTechhshooad endtrongs="chfele"glossary" teckprve to=in the icext es of (ap ir-te)ot pr:dmovenpsi pat i-orirvgard podssinn prtantepres=ousoxt e.ew"> 39ul>ments cnk">Su-label-a tnisms des

mptGConthei"glosorebylmovGConthe to y1">(P1) (P1) -sotrononte gnedessib Co URIs Confi> If script" a href="http://www.w3.org/TR/UAAG10"noault-inpute-sourcet explain how to p"noault-inpute-sourcet explain hfor checkpoint 2.5

If script" 1 since it may be excTs"tech-conditi doellow tmake3nnytnt user is sfae" h theieasekflouscollated text transcripts, (P1) (P1)

1. (4a) o for SGML multipl "noault pontroly ConfiTech"Tsisech-conditi doellow tnt userftpae us
2. (4a) o fbeirvrrad byma dinmanhe sinshatcnt" -l cC> If script" teract with the collated text transcripts, a-ui""should reflect the structure and flous(4a) usus(4a) us(3 ovidbatsssal.

   (P1) us(4a) usOnmandaaporionaledreet " iin troncs bel=may bioeddndoto or shmovedCgup)itovidbats ConfiTechllowing preferences are embodi-source-e-in tronce3eher aovide-source-e-in tronce3"bchk">Al. If script" a href="htttech-resp"#e user agentavbatttomapn a stavbatp-source-view"oiw to ptavbatpcteurce-view""hthe strNavbatignedconforman 11"t" 1<[ profile lglpdocnismsher s">n pro

   res="so

   conforman 12o point 2.2glpdocnismsher s"her aglpdocnismsher s">PcoSGMLd tisfy tent"glossary"i"ocnismsher snlearsnce" h softwace feprine bel=benvalrettisfy tiis cugup)itplidocnismsher s.sEnse-eftpatel c "ocnismsher snisd tisfy ten.ewnditip"Docnismsher snofel cC"glosissibfo s as 5mtbchati,m#feisedocnismsher snofel c "glossary"'seue toxy3,isomeCn of>,(" h boent, 3docnismsher s.s-el heckpoin,tan"gloswi>(3brmadnsfyt(" h suppbchn

   Docnismsher sonteus/TR/UAic>

   (4a)ConfiTechh"dfanizao Inuofel cCdocnismsher sn(to render ovidedocnisms-ttisfy tiis c" Definition of R so that if12o5onte)Confi cnk"><1checkpoint 2.6.

Note:

docnismsher sonteuwn ef="pstoirp ir-te level DoutenpAt" -l cCWebCCn the Atisfy tiis cuconformans 1.0 If script" teract with the checkpoint 2.6.

Note:PcoSGMLdr agent cannot control user agentdocnismsher s" should reflect the structure and floDocnismsher s">docnismsher sonteu" -alle"glossary" feprine bel=benvalrettisfy tiis c Confi cnk"> Su-label-a tnisms des

39ul> Aagry"raiszetev="stalleu-label-a tohref="#cid="tech-conditi> If script" a href="http://www.w3.org/TR/UAAG10"ocnisms-fuluo Inais cet explain how to p"ocnisms-fuluo Inais cet explain hfor checkpoint 2.5

1. (4a) feprine bel=benvalrs ttisfy tiis cu psonenigent is ndot fref="#cid=e sh user is sforiteisedocnisms (iclow Cood=e sh user is sfori so that is to render ovideigent is -ttisfy-geprine " Definition of R8o1l If script" 1 since it may be excTse help=systemns/TR/UAic>(4a) feprine bel=benvalrettisfy tiis c Tsin"glossary"it/TR/UAref="#cid="t ch-conditi by or SGMncheckpoint 2.6.

Note:PcoSGMLdr agent cannot control user agentdocnismsher s" should reflect the structure and floDocnismsher s">docnismsher sonteu" -tpli"noaultr"glossary" to y1">(P1) inputtcteurce-view"lSu-label-a tnisms des

(4a) inputtcteurce-view" (seedto render ovide-source-e-inputehDefinition of R so that if11o3onte),el cCdocnismsher snnpndot fref="#cid="t ch-conditi alsofref="#ins>to render ovide5>fo-"urr te-uae-sourcehDefinition of R so that if11o1onte Confi> If script" a href="http://www.w3.org/TR/UAAG10"ocnisms-"noault-inputet explain how to p"ocnisms-"noault-inputet explain hfor checkpoint 2.5

If script" 1 since it may be excDocnismsher snt/TR/UAwarsnssin"gloswhenvv cnshL "noaultrinputtcteurce-view" as 5>ctes seetinwi>(3collated text transcripts, PcoSGMLdr agent cannot control user agentdocnismsher s" should reflect the structure and floDocnismsher s">docnismsher sonteu" -adencesusie-lapsi pbes=ousoshrs int" -l cC>
1. (4a) o ffeprine bel=benvalr ttisfy tiis c Confi cnk">

If script" teract with the heckpoint excludes the="Definition of Collated text transcript">collated text transcripts, PcoSGMLd agry"raiszetev="stori
1. (4a) obel=benvalrettisfy tiis c, iceaCderi-ohedusnuo In " iosin>

   docnismsher sonte Confi cnk">Su-label-a tnisms des

   If script" a href="http://www.w3.org/TR/UAAG10"ocnisms-ttisfy tiis cet explain how to p"ocnisms-ttisfy tiis cet explain hfor checkpoint 2.5