| For Content Accessibility (Priority 1) |
Labels |
Satisfied |
Comments |
| Checkpoint 2.1 Make all
content available through the user interface. As part of meeting this
requirement, provide a view (e.g., a document source view) of the text portions
of content. This is only required for formats defined by specifications that
the user agent implements.
(Techniques for 2.1) |
|
|
|
| Checkpoint 2.2 For content
that requires user input within a time interval controlled by the user agent,
allow configuration to make the time interval "infinite" (i.e., pause
automatically at the beginning of each time interval where user input is
required, and resume automatically after the user has explicitly completed
input).
(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
tracks and visual tracks.
(Techniques for 2.4) |
Video
Audio |
|
|
| Checkpoint 2.5 Respect
synchronization cues during rendering.
(Techniques for 2.5) |
Video
Audio |
|
|
| 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) |
Image |
|
|
| 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 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) |
Image
Video
Audio |
|
|
| Checkpoint 3.3 Allow the
user to configure the user agent to render animated or blinking text as
motionless, unblinking text.
(Techniques for 3.3) |
VisualText |
|
|
| Checkpoint 3.4 Allow the user
to configure the user agent not to execute any excecutable 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) |
Image |
|
|
| Checkpoint 3.5 Allow
configuration so that client-side content refreshes (i.e., those initiated by
the user agent, not the server) do not change content except on explicit user
request. Allow the user to request the new content on demand (e.g., by
following a link or confirming a prompt). 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.5) |
|
|
|
| Checkpoint 4.1 Allow the
user to configure globally and control the reference size of 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) |
VisualText |
|
|
| Checkpoint 4.2 Allow the
user to configure globally the font family of all rendered text, with an option
to override font families specified by the author or 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) |
VisualText |
|
|
| Checkpoint 4.3 Allow the
user to configure globally the foreground and background color of all 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) |
ColorText |
|
|
| Checkpoint 4.4 Allow the user
to slow the presentation rate of audio, video and animations. 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, video and animations whose recognized role is to create a purely
stylistic effect. (Techniques
for 4.4) |
Animation
Video
Audio |
|
|
| 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. The
user agent is not required to satisfy this checkpoint for audio, video and
animations whose recognized role is to create a purely stylistic effect.
(Techniques for 4.5) |
Animation
Video
Audio |
|
|
| 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) |
Animation
Video
Audio |
|
|
| Checkpoint 4.9 Allow
the user to configure globally and control 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) |
Audio |
|
|
| Checkpoint
4.10 Allow the user to control independently the volumes of distinct
audio sources synchronized to play simultaneously.
(Techniques for 4.10) |
Audio |
|
|
| Checkpoint 4.11 Allow
the user to configure and control synthesized speech playback rate according to
the full range offered by the speech synthesizer.
(Techniques for 4.11) |
Speech |
|
|
| Checkpoint 4.12 Allow
the user to control synthesized speech volume independent of other sources of
audio.
(Techniques for 4.12) |
Speech |
|
|
| 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 purpose of each table and the relationships among the table cells
and headers. (Techniques
for 8.1) |
|
|
|
| For User Interface (Priority 1) |
Labels |
Satisfied |
Comments |
| Checkpoint
1.2 Ensure that the user can interact with all active elements through
keyboard input alone, pointing device input alone, and voice input alone.
(Techniques for 1.2) |
|
|
|
| Checkpoint 1.3 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) |
|
|
|
| Checkpoint 4.14 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.14) |
|
|
|
| Checkpoint
5.11 Follow operating environment conventions that benefit
accessibility when implementing the selection, content focus, and user
interface focus.
(Techniques for 5.11) |
|
|
|
| Checkpoint 5.12 Ensure
that default input configurations do not interfere with operating environment
accessibility conventions.
(Techniques for 5.12) |
|
|
|
| Checkpoint 7.1 Allow the user to
navigate among all viewports (including frames). (Techniques
for 7.1) |
|
|
|
| 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) |
|
|
|
| Checkpoint 8.2 Ensure that
all of the default highlight styles for the selection, content focus, active
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.
(Techniques for 8.2) |
|
|
|
| Checkpoint
8.6 Provide a mechanism for highlighting the selection and content
focus, and allow the user to configure the highlight styles. The highlight
mechanism must not rely on color alone. 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 8.6) |
|
|
|
| Checkpoint 8.7 Provide a
mechanism for highlighting the current viewport. For graphical viewports, the
default highlight mechanism must not rely on color alone.
(Techniques for 8.7) |
|
|
|
| Checkpoint 9.1 Provide
information to the user about current user preferences for input
configurations.
(Techniques for 9.1) |
|
|
|
| For Communication (Priority 1) |
Labels |
Satisfied |
Comments |
| Checkpoint 1.1 Ensure
that the user can operate the user agent fully through keyboard input alone,
pointing device input alone, and voice input alone.
(Techniques for 1.1) |
|
|
|
| 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 environment).
(Techniques for 5.3) |
|
|
|
| Checkpoint 5.4 Provide
programmatic read and write access to user agent user interface controls using
standard APIs (e.g., platform-independent APIs such as the W3C DOM; standard
APIs defined for a specific operating system; and
conventions for programming languages, plug-ins, virtual machine environments,
etc.)
(Techniques for 5.4) |
|
|
|
| Checkpoint 5.5 Using standard APIs,
provide programmatic alert of changes to content and user interface controls
(including selection, content focus, and user interface focus). (Techniques for
5.5) |
|
|
|
| Checkpoint 5.6 Implement
standard accessibility APIs (e.g., of the operating environment). 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 environment.
(Techniques for 5.6) |
|
|
|
| Checkpoint 5.7 Implement the
operating environment's standard APIs for the keyboard. (Techniques for
5.7) |
|
|
|
| Checkpoint 5.8 For an API
implemented to satisfy requirements of this document, support the character
encodings required for that API. (Techniques
for 5.8) |
|
|
|
| For Accessible Documentation (Priority 1) |
Labels |
Satisfied |
Comments |
| Checkpoint 10.1 Ensure that at
least one version of the product documentation conforms to at least Level
Double-A of the Web Content Accessibility Guidelines 1.0
[WCAG10]. (Techniques
for 10.1) |
|
|
|
| Checkpoint
10.2 Document all user agent features that benefit accessibility.
(Techniques for 10.2) |
|
|
|
| Checkpoint
10.3 Document the default input configuration (e.g., the default
keyboard bindings).
(Techniques for 10.3) |
|
|
|