This document is an appendix to "User Agent Accessibility Guidelines 1.0"
[UAAG10]. It provides a list of all checkpoints from the User Agent
Accessibility Guidelines 1.0, organized by concept, as a checklist for user
agent developers. Please refer to the Guidelines document for introductory
information, information about related documents, a glossary of terms, and
more.

This list may be used to review a tool or set of tools for accessibility.
For each checkpoint, indicate whether the checkpoint has been satisfied, has
not been satisfied, or is not applicable.

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 document is an appendix to a Working Draft. It is a draft document and
may be updated, replaced or obsoleted by other documents at any time. It is
inappropriate to use W3C Working Drafts as reference material or to cite them
as other than "work in progress". This is work in progress and does not imply
endorsement by, or the consensus of, W3C Members.

Priorities

This checkpoint must be satisfied by user agents,
otherwise 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.

This checkpoint should be satisfied by user agents,
otherwise 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.

This checkpoint may be satisfied by user agents to make it
easier for one or more groups of users with disabilities to access information.
Satisfying this checkpoint will improve access to the Web for some people.

Priority 1 checkpoints

For Content Accessibility (Priority 1)

Checkpoint 2.2 For a
presentation that requires user input within a specified time interval, allow
the user to configure the user agent to pause the presentation automatically
and await user input before proceeding. (Techniques
for 2.2)

Checkpoint 2.3 Provide easy
access to each equivalent and each equivalency target through at least one of
the following mechanisms: (1) allowing configuration to render the equivalent
instead of the equivalency target; (2) allowing configuration to render the
equivalent in addition to the equivalency target; (3) allowing the user to
select the equivalency target and then inspect its equivalents; (4) providing a
direct link to the equivalent in content, just before or after the equivalency
target in document order. (Techniques
for 2.3)

Checkpoint 2.4 Allow
the user to specify that text transcripts, collated text transcripts, captions,
and auditory descriptions be rendered at the same time as the associated audio
and visual tracks.
(Techniques for 2.4)

Checkpoint
3.1 Allow the user to configure the user agent not to render
background images. In this configuration, provide an option to alert the user
when a background image is available but has not been rendered.
(Techniques for 3.1)

Checkpoint 3.2 Allow the
user to configure the user agent not to render audio, video, or animated images
except on explicit request from the user. In this configuration, provide an
option to render a substitute placeholder in context for each unrendered source
of audio, video, or animated image. When placeholders are rendered, allow the
user to activate each placeholder individually and replace it with the original
author-supplied content.
(Techniques for 3.2)

Checkpoint 3.5 Allow the user
to configure the user agent not to execute scripts or applets. In this
configuration, provide an option to alert the user when scripts or applets are
available. (Techniques
for 3.5)

Checkpoint 4.1 Allow the
user to configure and control the reference size of rendered text with an
option to override author-specified and user agent default sizes of rendered
text. Make available the range of system font sizes.
(Techniques for 4.1)

Checkpoint 4.2 Allow the
user to configure the font family of all rendered text, with an option to
override author-specified, and user agent default, font families. Allow the
user to select from among the range of system font families.
(Techniques for 4.2)

Checkpoint 4.3 Allow the
user to configure the foreground and background color of all text, with an
option to override foreground and background colors specified by the author or
user agent defaults. Allow the user to select from among the range of system
colors.
(Techniques for 4.3)

Checkpoint 4.4 Allow the user
to slow the presentation rate of audio, video and animations that are not
recognized as style. For a visual track, provide at least one setting between
40% and 60% of the original speed. For a prerecorded audio track including
audio-only presentations, provide at least one setting between 75% and 80% of
the original speed. When the user agent allows the user to slow the visual
track of a synchronized multimedia presentation to between 100% and 80% of its
original speed, synchronize the visual and audio tracks. Below 80%, the user
agent is not required to render the audio track. (Techniques
for 4.4)

Checkpoint 4.5 Allow the
user to stop, pause, resume, fast advance, and fast reverse audio, video, and
animations that last three or more seconds at their default playback rate and
that are not recognized as style.
(Techniques for 4.5)

Checkpoint 4.6 For
graphical viewports, allow the user to position text transcripts, collated text
transcripts, and captions in the viewport. Allow the user to choose from among
the same range of positions available to the author (e.g., the range of
positions allowed by the markup or style language).
(Techniques for 4.6)

Checkpoint
6.1 Implement the accessibility features of all implemented
specifications (markup languages, style sheet languages, metadata languages,
graphics formats, etc.). The accessibility features of a specification are
those identified as such and those that satisfy all of the
requirements of the "Web Content Accessibility Guidelines 1.0"
[WCAG10].
(Techniques for 6.1)

Checkpoint 8.1 Make available to
the user the author-specified purpose of each table and the author-specified
relationships among the table cells and headers. (Techniques
for 8.1)

Checkpoint
4.15 Allow the user to configure how the selection is highlighted
(e.g., foreground and background color, voice pitch, etc.). For graphical
viewports, offer at least three rendering options, including colors and fonts.
Allow the user to select from among the range of system colors and fonts.
(Techniques for 4.15)

Checkpoint
4.16 Allow the user to configure how the content focus is highlighted
(e.g., foreground and background color, voice pitch, etc.). For graphical
viewports, offer at least three rendering options, including colors and fonts,
and allow the user to select from among the range of system colors and fonts.
The default focus highlight mechanism must be different from the default
selection highlight mechanism.
(Techniques for 4.16)

Checkpoint 7.2 Associate
a point of regard with each state in a viewport's browsing history and when the
user returns to a state in the history, restore the associated point of regard.
(Techniques for 7.2)

Checkpoint 7.3 Allow the user to
navigate all active elements. If the author has not specified a navigation
order, allow at least forward sequential navigation of elements, in document
order.
(Techniques for 7.3)

For Communication (Priority 1)

Checkpoint 1.2 Implement
the standard accessibility APIs of the operating system and supported
programming languages. Where these APIs do not enable the user agent to satisfy
the requirements of this document, use the standard input and output APIs of
the operating system and supported programming languages.
(Techniques for 1.2)

Checkpoint 5.1 Provide
programmatic read access to HTML and XML
content by conforming to the following modules of the W3C Document Object Model
DOM Level 2 Core Specification
[DOM2CORE] and exporting the
interfaces they define: (1) the Core module for HTML; (2) the Core and XML
modules for XML. (Techniques
for 5.1)

Checkpoint 5.2 If the user
can modify HTML and XML content through the user interface,
provide the same functionality programmatically by conforming to the following
modules of the W3C Document Object Model DOM Level 2 Core Specification
[DOM2CORE] and exporting the interfaces they define: (1) the Core
module for HTML; (2) the Core and XML modules for XML. (Techniques
for 5.2)

Checkpoint 5.3 For markup
languages other than HTML and XML,
provide programmatic access to content using standard APIs (e.g.,
platform-independent APIs and standard APIs for the
operating system).
(Techniques for 5.3)

Priority 2 checkpoints

For Content Accessibility (Priority 2)

Checkpoint 2.6 For non-text
content that has no recognized text equivalent, allow configuration to generate
repair text. If the non-text content is included by URI reference, base the
repair text on the URI reference and content type of the Web resource.
Otherwise, base the repair text on the name of the element that includes the
non-text content. (Techniques for
2.6)

Checkpoint
3.6 Allow configuration so that an author-specified "client-side
redirect" (i.e., one initiated by the user agent, not the server) does not
change content except on explicit user request. Allow the user to access the
new content manually (e.g., by following a link).
(Techniques for 3.6)

Checkpoint 3.7 Allow
configuration so that author-specified content refreshes do not change content
except on explicit user request. Allow the user to request the new content
manually (e.g., by activating a button or following a link). Alert the user,
according to the schedule specified by the author, whenever fresh content is
available (to be obtained on explicit user request).
(Techniques for 3.7)

Checkpoint 4.13 Allow
the user to configure synthesized voice gender, pitch, pitch range, stress,
richness, speech dictionary, and handling of spelling, punctuation, and number
processing according to the full range of values offered by the speech
synthesizer.
(Techniques for 4.13)

Checkpoint 8.2 Render
recently visited links in a distinct style and allow the user to configure this
style. For graphical viewports, offer at least three rendering options,
including colors and fonts. Allow the user to select from among the range of
system colors and fonts.
(Techniques for 8.2)

Checkpoint 8.3 Render in a
distinct style those links that have been marked up to indicate that following
them will involve a fee and allow the user to configure this style. For
graphical viewports, offer at least three rendering options, including colors
and fonts. Allow the user to select from among the range of system colors and
fonts.
(Techniques for 8.3)

Checkpoint 8.4 Make
available to the user an "outline" view of content, composed of labels for
important structural elements (e.g., heading text, table titles, form titles,
etc.). For discussion about what constitutes the set of important structural
elements, please refer to
checkpoint 7.6.
(Techniques for 8.4)

Checkpoint 4.19 Allow the user
to configure the user agent to only open viewports on explicit user request. In
this configuration, instead of opening a viewport automatically, alert the user
and allow the user to open it manually. Allow the user to close viewports. (Techniques
for 4.19)

Checkpoint 4.20 For graphical
user interfaces, allow the user to configure the user agent so that the
viewport with the current focus remains "on top" of all other viewports. In
this configuration, when a viewport opens without explicit user request, alert
the user. (Techniques
for 4.20)

Checkpoint 7.4 Allow the user
to choose to navigate only active elements. If the author has not specified a
navigation order, allow at least forward and reverse sequential navigation of
active elements, in document order. (Techniques
for 7.4)

Checkpoint 7.5 Allow the user to
search for a string of characters from the document character set in text
content that has been rendered. The search must encompass all text within the
viewport, both inside and outside the point of regard. Allow the user to start
a search forward in document order from any selected or focused location in
content. When there is a match, allow the user to search for the next instance
of the text from the location of the match. When there is a match, move the
point of regard so that the matched text is in the viewport. Alert the user
when there is no match. Provide a case-insensitive search option for text in
scripts (i.e., writing systems) where case is significant. (Techniques for
7.5)

Checkpoint 7.6 Allow the user to
navigate efficiently to and among important structural elements identified by
the author. Allow forward and backward sequential navigation to important
structural elements. (Techniques
for 7.6)

Checkpoint 8.9 Allow
configuration so the user is prompted to confirm any form submission not caused
by explicit user request to activate a form submit control. (Techniques
for 8.9)

Checkpoint
9.3 Provide information to the user about current author-specified
input configurations (e.g., keyboard bindings specified in HTML documents with
the "accesskey" attribute).
(Techniques for 9.3)

Checkpoint 9.4 Allow the user
to change the default input configuration as follows: Allow the user to
override any binding that is part of the user agent default input configuration
(checkpoint 9.8). The
user agent is not required to allow the user to override standard bindings for
the operating system (e.g., for access to help). For any binding in the default
keyboard configuration, allow the user to override it with a binding of a
single key alone or with modifier keys. (Techniques
for 9.4)

Checkpoint 9.7 For the
configuration requirements of this document, allow the user to save user
preferences in at least one user profile. Allow users to select from among
available profiles or no profile (i.e., the user agent default settings). (Techniques for
9.7)

Checkpoint 9.8 Ensure
that the default input configuration includes bindings for the following
functionalities required by other checkpoints in this document: move focus to
next active element; move focus to previous active element; activate focused
link; search for text; search again for same text; next history state
(forward); previous history state (back); increase size of rendered text;
decrease size of rendered text; increase global volume; decrease global volume;
(each of) stop, pause, resume, fast advance, and fast reverse selected audio,
video, and animation. If the user agent supports the following functionalities,
the default input configuration must also include bindings for them: enter URI
for new resource; add to favorites (i.e., bookmarked resources); view
favorites; stop loading resource; reload resource; refresh rendering; forward
one viewport; back one viewport; next line; previous line.
(Techniques for 9.8)

Checkpoint 2.8 Allow
the user to configure the user agent not to render content in unsupported
natural languages. Indicate to the user in context that author-supplied content
has not been rendered.
(Techniques for 2.8)

Checkpoint 8.5 To help the user
decide whether to traverse a link, make available the following information
about it: link content, link title, whether the link is internal to the local
resource, whether the user has traversed the link recently, whether traversing
it may involve a fee, and information about the type, size, and natural
language of linked Web resources. The user agent is not required to compute or
make available information that requires retrieval of linked Web resources. (Techniques for
8.5)

Checkpoint 8.10 Indicate the
relative position of the viewport in rendered content (e.g., the proportion of
an audio or video clip that has been played, the proportion of a Web page that
has been viewed, etc.). (Techniques
for 8.10)

Checkpoint 9.9 For
graphical user interfaces, allow the user to configure the position of controls
on tool bars of the user agent user interface, to select or remove controls for
the user interface from a predefined set, and to restore the default user
interface.
(Techniques for 9.9)