| For Content Accessibility (Priority 1) |
Satisfied |
Comments |
| Checkpoint 2.1 Make all
content available through the user interface. (Techniques
for 2.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. Respect author-specified synchronization cues during
rendering.
(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.3 Allow the
user to configure the user agent to render animated or blinking text as
motionless text. (Techniques
for 3.3) |
|
|
| Checkpoint 3.4 Allow
the user to configure the user agent to render blinking images as motionless
images.
(Techniques for 3.4) |
|
|
| 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 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 color of all text, with
an option to override author-specified, and user agent default, foreground
colors. Allow the user to select from among the range of system colors.
(Techniques for 4.3) |
|
|
| Checkpoint
4.4 Allow the user to configure the background color of all text, with
an option to override author-specified and user agent default background
colors. Allow the user to select from among the range of system colors.
(Techniques for 4.4) |
|
|
| Checkpoint 4.5 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% - 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.5) |
|
|
| Checkpoint 4.6 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.6) |
|
|
| Checkpoint 4.7 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.7) |
|
|
| Checkpoint 4.10 Allow
the user to configure and control the global audio volume. The user must be
able to choose zero volume (i.e., silent).
(Techniques for 4.10) |
|
|
| Checkpoint
4.11 Allow the user to control independently the volumes of distinct
audio sources synchronized to play simultaneously.
(Techniques for 4.11) |
|
|
| Checkpoint 4.12 Allow
the user to configure and control synthesized speech playback rate according to
the full range offered by the speech synthesizer. The lower bound for this
range must be at most 120 words per minute. The upper bound for this range must
be at least 400 words per minute. The user must be able to increase or decrease
the playback rate in increments of 5% of the current playback rate.
(Techniques for 4.12) |
|
|
| Checkpoint 4.13 Allow
the user to control the synthesized speech volume independently of other
sources of audio.
(Techniques for 4.13) |
|
|
| 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) |
|
|
| For User Interface (Priority 1) |
Satisfied |
Comments |
| Checkpoint
1.4 Ensure that the user can interact with all active elements in a
device-independent manner.
(Techniques for 1.4) |
|
|
| Checkpoint 1.5 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.5) |
|
|
| Checkpoint 4.15 For user
agents that support style sheets, allow the user to select from (and apply)
available author and user style sheets or to ignore them. (Techniques
for 4.15) |
|
|
| Checkpoint
4.16 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.16) |
|
|
| Checkpoint
4.17 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.
For graphical viewports, 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.17) |
|
|
| 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.6 Implement selection, content focus, and user interface focus
mechanisms. Implement them according to system conventions (per checkpoint 5.8).
(Techniques for 8.6) |
|
|
| Checkpoint
8.7 Provide a mechanism for highlighting the current viewport,
selection, and content focus.
(Techniques for 8.7) |
|
|
| Checkpoint 9.1 Provide
information to the user about current user preferences for input configurations
(e.g., keyboard or voice bindings).
(Techniques for 9.1) |
|
|
| Checkpoint 9.2 Avoid
default input configurations that interfere with operating system accessibility
conventions.
(Techniques for 9.2) |
|
|
| For Communication (Priority 1) |
Satisfied |
Comments |
| Checkpoint 1.1 Ensure
that every functionality available through the user interface is also available
through every input API that is implemented by the user agent. This checkpoint
does not require developers to reimplement the input methods associated with
the keyboard, pointing device, voice, and other input APIs.
(Techniques for 1.1) |
|
|
| Checkpoint 1.2 Use the
standard input and output APIs of the operating system. Do not bypass the
standard output APIs when rendering information. (Techniques
for 1.2) |
|
|
| Checkpoint 1.3 Implement the
operating system's standard API for the keyboard and ensure that every
functionality available through the user interface is available through this
API. (Techniques for
1.3) |
|
|
| Checkpoint 5.1 Provide
programmatic read access to HTML and XML
content by conforming to the W3C Document Object Model (DOM) Level 2 Core and
HTML Specifications and exporting the interfaces they define. (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 W3C
Document Object Model (DOM)
Level 2 Core and HTML Specifications and exporting the
interfaces they define. (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) |
|
|
| 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) |
|
|
| For Accessible Documentation (Priority 1) |
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 promote accessibility.
(Techniques for 10.2) |
|
|
| Checkpoint
10.3 Document the default input configuration (e.g., default keyboard
bindings).
(Techniques for 10.3) |
|
|