| Checkpoints |
Content/
User Agent/
Both |
Labels |
Satisfied |
Comments |
| Checkpoint 1.1 Full keyboard access. Ensure that the user can
operate through keyboard input alone any user agent functionality available
through the user interface.
(Techniques for 1.1) |
Both |
|
|
|
| Checkpoint
1.2 Activate event handlers. For the
element with content focus, allow the user to activate any explicitly
associated input device event handlers through keyboard input alone. The user
agent is not required to allow activation of event handlers associated with a
given device (e.g., the pointing device) in any order other than what the
device itself allows.
(Techniques for 1.2) |
Content only |
|
|
|
| Checkpoint 1.3 Provide text messages. Ensure that every message
(e.g., prompt, alert, notification, etc.) that is a non-text element and is
part of the user agent user interface has a text equivalent.
(Techniques for 1.3) |
User agent only |
|
|
|
| Checkpoint 2.1 Render by specification. Render content according to
specification. When a rendering requirement of another specification
contradicts a requirement of the current document, the user agent may disregard
the rendering requirement of the other specification and still satisfy this
checkpoint.
(Techniques for 2.1) |
Content only |
|
|
|
| Checkpoint 2.2 Provide text view. For text formats, provide a view
of the text source. For the purposes of this document, text formats are defined
to be: (1) all media objects given an Internet media type of "text" (e.g.,
text/plain, text/HTML, or text/*), and (2) all SGML and XML applications,
regardless of Internet media type (e.g., HTML 4.01, XHTML 1.1, SMIL, SVG,
etc.).
(Techniques for 2.2) |
Content only |
|
|
|
| Checkpoint 2.3 Render conditional content. Allow configuration to
provide access to each piece of unrendered conditional content "C". The
configuration may be a switch that, for all content, turns on or off the access
mechanisms described below. 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 querying 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); (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"; (3b) allow the user to follow a link in context to C.
(Techniques for 2.3) |
Content only |
|
|
|
| Checkpoint 2.4 Allow time-independent interaction. For content
where user input is only possible within a finite time interval controlled by
the user agent, allow configuration to make the time interval "infinite". Do
this by pausing automatically at the end of each time interval where user input
is possible, and resuming automatically after the user has explicitly completed
input. In this configuration, alert the user when the session has been paused
and which enabled elements are time-sensitive. When the user pauses a real-time
presentation, the user agent may discard packets that continue to arrive during
the pause.
(Techniques for 2.4) |
Content only |
|
|
|
| Checkpoint
2.5 Make captions, transcripts
available. Allow configuration or control so that text transcripts,
collated text transcripts, captions, and auditory descriptions are rendered at
the same time as the associated audio tracks and visual tracks.
(Techniques for 2.5) |
Content only |
Video
Audio |
|
|
| Checkpoint 2.6 Respect synchronization cues. Respect
synchronization cues during rendering.
(Techniques for 2.6) |
Content only |
Video
Audio |
|
|
| Checkpoint
3.1 Toggle background images. Allow
configuration not to render background images. This checkpoint only requires
control of background images for "two-layered renderings", i.e., one rendered
background image with all other content rendered "above it". In this
configuration, the user agent is not required to retrieve background images
from the Web.
(Techniques for 3.1) |
Content only |
Image |
|
|
| Checkpoint 3.2 Toggle audio, video, animated images. Allow
configuration not to render audio, video, or animated images except on explicit
user request.
(Techniques for 3.2) |
Content only |
Animation
Video
Audio |
|
|
| Checkpoint 3.3 Toggle animated/blinking text. Allow configuration
to render animated or blinking text as motionless, unblinking text. The user
agent also satisfies this checkpoint by always rendering animated or blinking
text as motionless, unblinking text.
(Techniques for 3.3) |
Content only |
VisualText |
|
|
| Checkpoint 3.4 Toggle scripts. Allow configuration not to execute
any executable content (e.g., scripts and applets). In this configuration,
provide an option to alert the user when executable content is available (but
has not been executed).
(Techniques for 3.4) |
Content only |
|
|
|
| Checkpoint
3.5 Toggle content refresh. Allow
configuration so that the user agent only refreshes content on explicit user
request. In this configuration, alert the user of the refresh rate specified in
content, and allow the user to request fresh content manually (e.g., by
following a link or confirming a prompt). When the user chooses not to refresh
content, the user agent may ignore that content; buffering is not required.
This checkpoint only applies when the user agent (not the server) automatically
initiates the request for fresh content.
(Techniques for 3.5) |
Content only |
|
|
|
| Checkpoint 4.1 Configure text size. Allow global configuration and
control over the reference size of visually rendered text, with an option to
override reference sizes specified by the author or user agent defaults. Allow
the user to choose from among the full range of font sizes supported by the
operating environment.
(Techniques for 4.1) |
Content only |
VisualText |
|
|
| Checkpoint 4.2 Configure font family. Allow global configuration of
the font family of all visually rendered text, with an option to override font
families specified by the author or by user agent defaults. Allow the user to
choose from among the full range of font families supported by the operating
environment.
(Techniques for 4.2) |
Content only |
VisualText |
|
|
| Checkpoint 4.3 Configure text colors. Allow global configuration of
the foreground and background color of all visually rendered text, with an
option to override foreground and background colors specified by the author or
user agent defaults. Allow the user to choose from among the full range of
colors supported by the operating environment.
(Techniques for 4.3) |
Content only |
ColorText |
|
|
| Checkpoint 4.4 Slow multimedia. Allow the user to slow the
presentation rate of audio and animations (including video and animated
images). 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. The user agent is not required to
satisfy this checkpoint for audio and animations whose recognized role is to
create a purely stylistic effect.
(Techniques for 4.4) |
Content only |
Animation
Audio |
|
|
| Checkpoint 4.5 Start, stop, pause, advance multimedia. Allow the
user to stop, pause, resume, fast advance, and fast reverse audio and
animations (including video and animated images) that last three or more
seconds at their default playback rate. The user agent is not required to
satisfy this checkpoint for audio and animations whose recognized role is to
create a purely stylistic effect. The user agent is not required to play
synchronized audio during fast advance or reverse of animations (though doing
so may help orient the user). The user agent is not required to play animations
during fast advance and fast reverse. When the user pauses a real-time audio or
animation, the user agent may discard packets that continue to arrive during
the pause.
(Techniques for 4.5) |
Content only |
Animation
Audio |
|
|
| Checkpoint 4.6 Position captions. For graphical viewports, allow
the user to position captions with respect to synchronized visual tracks as
follows: (a) if the user agent satisfies this checkpoint by using a markup
language or style sheet language to provide configuration or control, then the
user agent must allow the user to choose from among at least the range of
positions enabled by the format; (b) otherwise, the user agent must allow both
non-overlapping and overlapping positions (e.g., by rendering captions in a
separate viewport that may be positioned on top of the visual track). In either
case, the user agent must allow the user to override the author's specified
position. The user agent is not required to change the layout of other content
(i.e., reflow) after the user has changed the position of captions.
(Techniques for 4.6) |
Content only |
|
|
|
| Checkpoint
4.9 Global volume control. Allow
global configuration and control of the volume of all audio, with an option to
override audio volumes specified by the author or user agent defaults. The user
must be able to choose zero volume (i.e., silent).
(Techniques for 4.9) |
Content only |
Audio |
|
|
| Checkpoint
4.10 Independent volume control.
Allow independent control of the volumes of distinct audio sources synchronized
to play simultaneously. The user agent is not required to satisfy this
checkpoint for audio whose recognized role is to create a purely stylistic
effect.
(Techniques for 4.10) |
Content only |
Audio |
|
|
| Checkpoint
4.12 Configure speech rate. Allow
configuration and control of the synthesized speech rate, according to the full
range offered by the speech synthesizer.
(Techniques for 4.12) |
Content only |
Speech |
|
|
| Checkpoint
4.13 Configure speech volume. Allow
control of the synthesized speech volume, independent of other sources of
audio.
(Techniques for 4.13) |
Content only |
Speech |
|
|
| Checkpoint
4.14 Configure speech
characteristics. Allow configuration of speech characteristics according
to the full range of values offered by the speech synthesizer.
(Techniques for 4.14) |
Content only |
|
|
|
| Checkpoint 4.17 Choose style sheets. For user agents that support
style sheets, allow the user to choose from (and apply) available author and
user style sheets or to ignore them.
(Techniques for 4.17) |
Both |
|
|
|
| Checkpoint 6.1 DOM read access. 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 6.1) |
Content only |
|
|
|
| Checkpoint 6.2 DOM write access. 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 6.2) |
Content only |
|
|
|
| Checkpoint 6.3 Programmatic access to other content. For markup
languages other than HTML and XML,
provide programmatic read access to content. Provide programmatic write access
for those parts of content that the user can modify through the user interface.
To satisfy these requirements, implement at least one API that is either (a)
defined by a W3C Recommendation, or (b) a publicly documented API designed to
enable interoperability with assistive technologies. If no such API is
available, or if available APIs do not enable the user agent to satisfy the
requirements, implement at least one publicly documented API to satisfy the
requirements, and follow operating environment conventions for the use
of input and output APIs.
(Techniques for 6.3) |
Content only |
|
|
|
| Checkpoint 6.4 Programmatic operation. Provide programmatic read
access to user agent user interface controls. Provide programmatic write access
for those controls that the user can modify through the user interface. For
security reasons, user agents are not required to allow instructions in content
to modify user agent user interface controls. To satisfy these requirements,
implement at least one API that is either (a) defined by a W3C Recommendation,
or (b) a publicly documented API designed to enable interoperability with
assistive technologies. If no such API is available, or if available APIs do
not enable the user agent to satisfy the requirements, implement at least one
publicly documented API that allows programmatic operation of all of the
functionalities that are available through the user agent user interface,
and follow operating environment conventions for the use of input and
output APIs.
(Techniques for 6.4) |
User agent only |
|
|
|
| Checkpoint 6.5 Programmatic alert of changes. Provide programmatic
alert of changes to content, user interface controls, selection, content focus,
and user interface focus. To satisfy these requirements, implement at least one
API that is either (a) defined by a W3C Recommendation, or (b) a publicly
documented API designed to enable interoperability with assistive technologies.
If no such API is available, or if available APIs do not enable the user agent
to satisfy the requirements, implement at least one publicly documented API to
satisfy the requirements, and follow operating environment conventions
for the use of input and output APIs.
(Techniques for 6.5) |
Both |
|
|
|
| Checkpoint 6.6 Conventional keyboard APIs. Follow operating
environment conventions when implementing APIs for the keyboard. If such APIs
for the keyboard do not exist, implement publicly documented APIs for the
keyboard.
(Techniques for 6.6) |
User agent only |
|
|
|
| Checkpoint 6.7 API character encodings. For an API implemented to
satisfy requirements of this document, support the character encodings required
for that API.
(Techniques for 6.7) |
Both |
|
|
|
| Checkpoint
7.1 Focus and selection conventions.
Follow operating environment conventions that benefit accessibility when
implementing the selection, content focus, and user interface focus.
(Techniques for 7.1) |
User agent only |
|
|
|
| Checkpoint
7.2 Respect input configuration
conventions. Ensure that default input configurations do not interfere
with operating environment accessibility conventions.
(Techniques for 7.2) |
User agent only |
|
|
|
| Checkpoint
8.1 Implement accessibility features.
Implement the accessibility features of specifications (markup languages, style
sheet languages, metadata languages, graphics formats, etc.). For the purposes
of this checkpoint, an accessibility feature is either (a) one identified as
such, or (b) one that allows the author to satisfy any requirement of the "Web
Content Accessibility Guidelines 1.0" [WCAG10].
(Techniques for 8.1) |
Content only |
|
|
|
| Checkpoint 9.1 Provide content focus. Provide at least one content
focus for each viewport (including frames) where enabled elements are part of
the rendered content. Allow the user to make the content focus of each viewport
the current focus.
(Techniques for 9.1) |
Content only |
|
|
|
| Checkpoint 9.2 Provide user interface focus. Provide a user
interface focus.
(Techniques for 9.2) |
User agent only |
|
|
|
| Checkpoint 9.3 Move content focus. Allow the user to move the
content focus to any enabled element in the viewport. If the author has not
specified a navigation order, allow at least forward sequential navigation to
each element, in document order. The user agent may also include disabled
elements in the navigation order.
(Techniques for 9.3) |
Content only |
|
|
|
| Checkpoint 9.4 Restore history. For user agents that implement a
viewport history mechanism, for each state in a viewport's browsing history,
maintain information about the point of regard, content focus, and selection.
When the user returns to any state in the viewport history, restore the saved
values for all of these state variables.
(Techniques for 9.4) |
Content only |
|
|
|
| Checkpoint 10.1 Table orientation. Make available to the user the
purpose of each table (e.g., as expressed in a summary or table caption) and
the relationships among the table cells and headers.
(Techniques for 10.1) |
Content only |
|
|
|
| Checkpoint
10.2 Highlight selection and focus.
Provide a mechanism for highlighting the selection and content focus of each
viewport. The highlight mechanism must not rely on color alone. Allow global
configuration of selection and focus highlight styles. For graphical viewports,
if the highlight mechanism involves colors or text decorations, allow the user
to choose from among the full range of colors or text decorations supported by
the operating environment.
(Techniques for 10.2) |
Content only |
|
|
|
| Checkpoint 10.3 Distinct default highlight styles. Ensure that all
of the default highlight styles for the selection, content focus, enabled
elements, recently visited links, and fee links (1) do not rely on color alone,
and (2) differ from each other, and not by color alone. This checkpoint not
apply to those highlight styles inherited from the operating environment as
default values, as long as the user can change the styles in the operating
environment.
(Techniques for 10.3) |
Content only |
|
|
|
| Checkpoint 10.7 Highlight current viewport. Provide a mechanism for
highlighting the viewport with the current focus. For graphical viewports, the
default highlight mechanism must not rely on color alone. This default color
requirement does not apply if the highlight mechanism is inherited from the
operating environment as the default and the user can change it in the
operating environment.
(Techniques for 10.7) |
User agent only |
|
|
|
| Checkpoint
11.1 Current user bindings. Provide
information to the user about current user preferences for input
configurations.
(Techniques for 11.1) |
User agent only |
|
|
|
| Checkpoint 12.1 Accessible documentation. Ensure that at least one
version of the user agent documentation conforms to at least Level Double-A of
the Web Content Accessibility Guidelines 1.0 [WCAG10].
(Techniques for 12.1) |
User agent only |
|
|
|
| Checkpoint
12.2 Document accessibility features.
Document all user agent features that benefit accessibility. For the purposes
of this checkpoint, a user agent feature that benefits accessibility is one
implemented to satisfy the requirements of this document (including the
requirements of checkpoints 8.1 and
7.3).
(Techniques for 12.2) |
User agent only |
|
|
|
| Checkpoint
12.3 Document default bindings.
Document the default user agent input configuration (e.g., the default keyboard
bindings).
(Techniques for 12.3) |
User agent only |
|
|
|