List of Checkpoints for User Agent Accessibility Guidelines
1.0
- This version:
-
http://www.w3.org/WAI/UA/WD-UAAG10-20010604/uaag10-chklist
- (Formats: plain text, PostScript,
PDF)
- This document is an appendix to:
-
http://www.w3.org/WAI/UA/WD-UAAG10-20010604/
- Latest version of User Agent Accessibility Guidelines 1.0:
-
http://www.w3.org/WAI/UA/UAAG10/
- Editors:
- Ian Jacobs, W3C
Jon Gunderson, University of Illinois at
Urbana-Champaign
Eric Hansen, Educational Testing Service
Copyright © 1999 - 2001 W3C® (MIT,
INRIA, Keio), All Rights
Reserved. W3C
liability,
trademark, document
use and software
licensing rules apply.
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.
A tabular version of the list of
checkpoints is also available (e.g., for printing).
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.
Please send comments about this document to the public mailing list w3c-wai-ua@w3.org; public archives are
available.
This document has been produced as part of the Web Accessibility Initiative. WAI
Accessibility Guidelines are produced as part of the WAI Technical Activity. The
goal of the WAI User Agent Accessibility
Guidelines Working Group is discussed in the Working Group
charter.
A list of current W3C Recommendations and
other technical documents can be found at the W3C Web site.
Priorities
Each checkpoint in this document is assigned a priority that indicates its
importance for users with disabilities.
- [Priority
1]
- 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.
- [Priority
2]
- 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.
- [Priority
3]
- 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
- 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. Both
(Techniques for 1.1)
- 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. Content only
(Techniques for 1.2)
- 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. User agent only
(Techniques for 1.3)
- 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. Content only
(Techniques for 2.1)
- 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.). Content only
(Techniques for 2.2)
- 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. Content only
(Techniques for 2.3)
- 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. Content only
(Techniques for 2.4)
- 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. Content only
(Techniques for 2.5)
Labels: Video, Audio
- Checkpoint 2.6 Respect synchronization cues. Respect
synchronization cues during rendering. Content only
(Techniques for 2.6)
Labels: 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. Content only
(Techniques for 3.1)
Labels: Image
- Checkpoint 3.2 Toggle audio, video, animated images. Allow
configuration not to render audio, video, or animated images except on explicit
user request. Content only
(Techniques for 3.2)
Labels: 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. Content only
(Techniques for 3.3)
Labels: 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). Content only
(Techniques for 3.4)
- 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. Content only
(Techniques for 3.5)
- 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. Content only
(Techniques for 4.1)
Labels: 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. Content only
(Techniques for 4.2)
Labels: 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. Content only
(Techniques for 4.3)
Labels: 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. Content only
(Techniques for 4.4)
Labels: 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. Content only
(Techniques for 4.5)
Labels: 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. Content
only
(Techniques for 4.6)
- 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). Content only
(Techniques for 4.9)
Labels: 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. Content only
(Techniques for 4.10)
Labels: 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. Content only
(Techniques for 4.12)
Labels: Speech
- Checkpoint
4.13 Configure speech volume. Allow
control of the synthesized speech volume, independent of other sources of
audio. Content only
(Techniques for 4.13)
Labels: Speech
- Checkpoint
4.14 Configure speech
characteristics. Allow configuration of speech characteristics according
to the full range of values offered by the speech synthesizer. Content only
(Techniques for 4.14)
- 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. Both
(Techniques for 4.17)
- 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. Content only
(Techniques for 6.1)
- 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. Content only
(Techniques for 6.2)
- 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. Content only
(Techniques for 6.3)
- 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. User agent only
(Techniques for 6.4)
- 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. Both
(Techniques for 6.5)
- 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. User agent only
(Techniques for 6.6)
- Checkpoint 6.7 API character encodings. For an API implemented to
satisfy requirements of this document, support the character encodings required
for that API. Both
(Techniques for 6.7)
- Checkpoint
7.1 Focus and selection conventions.
Follow operating environment conventions that benefit accessibility when
implementing the selection, content focus, and user interface focus. User agent
only
(Techniques for 7.1)
- Checkpoint
7.2 Respect input configuration
conventions. Ensure that default input configurations do not interfere
with operating environment accessibility conventions. User agent only
(Techniques for 7.2)
- 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].
Content only
(Techniques for 8.1)
- 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. Content only
(Techniques for 9.1)
- Checkpoint 9.2 Provide user interface focus. Provide a user
interface focus. User agent only
(Techniques for 9.2)
- 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. Content only
(Techniques for 9.3)
- 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. Content only
(Techniques for 9.4)
- 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. Content only
(Techniques for 10.1)
- 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. Content only
(Techniques for 10.2)
- 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. Content only
(Techniques for 10.3)
- 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. User agent only
(Techniques for 10.7)
- Checkpoint
11.1 Current user bindings. Provide
information to the user about current user preferences for input
configurations. User agent only
(Techniques for 11.1)
- 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]. User
agent only
(Techniques for 12.1)
- 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). User agent only
(Techniques for 12.2)
- Checkpoint
12.3 Document default bindings.
Document the default user agent input configuration (e.g., the default keyboard
bindings). User agent only
(Techniques for 12.3)
Priority 2 checkpoints
- Checkpoint 2.7 Repair missing content. Allow configuration to
generate repair text when the user agent recognizes that the author has failed
to provide conditional content that was required by the format specification.
The user agent may satisfy this checkpoint by basing the repair text on any of
the following available sources of information: URI reference, content type, or
element type. Content only
(Techniques for 2.7)
- Checkpoint
3.6 Toggle redirects. Allow
configuration so that a "client-side redirect" (i.e., one initiated by the user
agent, not the server) only changes content on explicit user request. Allow the
user to access the new content on demand (e.g., by following a link or
confirming a prompt). The user agent is not required to provide these
functionalities for client-side redirects specified to occur instantaneously
(i.e., after no delay). Content only
(Techniques for 3.6)
Labels: Image
- Checkpoint 3.7 Toggle images. Allow configuration not to render
images. Content only
(Techniques for 3.7)
- Checkpoint 4.7 Slow other multimedia. Allow the user to slow the
presentation rate of audio and animations (including video and animated images)
not covered by checkpoint
4.4. The same speed percentage requirements of checkpoint 4.4 apply. Content
only
(Techniques for 4.7)
Labels: Animation, Audio
- Checkpoint
4.8 Control other multimedia. Allow
the user to stop, pause, resume, fast advance, and fast reverse audio and
animations (including video and animated images) not covered by checkpoint 4.5. Content only
(Techniques for 4.8)
Labels: Animation, Audio
- Checkpoint 4.11 Control other volume. Allow independent control of
the volumes of distinct audio sources synchronized to play simultaneously that
are not covered by
checkpoint 4.10. Content only
(Techniques for 4.11)
Labels: Audio
- Checkpoint
4.15 Specific speech characteristics.
Allow configuration of the following speech characteristics: pitch, pitch
range, stress, richness. Pitch refers to the average frequency of the speaking
voice. Pitch range specifies a variation in average frequency. Stress refers to
the height of "local peaks" in the intonation contour of the voice. Richness
refers to the richness or brightness of the voice. Content only
(Techniques for 4.15)
- Checkpoint
4.16 Configure speech features.
Provide support for user-defined extensions to the speech dictionary, as well
as the following functionalities: spell-out (spell text one character at a time
or according to language-dependent pronunciation rules), speak-numeral (speak a
numeral as individual digits or as a full number), and speak-punctuation (speak
punctuation literally or render as natural pauses). Content only
(Techniques for 4.16)
- Checkpoint
5.1 No automatic content focus
change. Allow configuration so that if a viewport opens without explicit
user request, its content focus does not automatically become the current
focus. Configuration is preferred, but is not required if the content focus can
only ever be moved on explicit user request. Both
(Techniques for 5.1)
- Checkpoint 5.2 Keep viewport on top. For graphical user interfaces,
allow configuration so that the viewport with the current focus remains "on
top" of all other viewports with which it overlaps. Both
(Techniques for 5.2)
- Checkpoint 5.3 Manual viewport open only. Allow configuration so
that viewports only open on explicit user request. In this configuration,
instead of opening a viewport automatically, alert the user and allow the user
to open it on demand (e.g., by following a link or confirming a prompt). Allow
the user to close viewports. If a viewport (e.g., a frame set) contains other
viewports, these requirements only apply to the outermost container viewport.
Configuration is preferred, but is not required if viewports can only ever open
on explicit user request. Both
(Techniques for 5.3)
- Checkpoint 5.4 Selection and focus in viewport. Ensure that when a
viewport's selection or content focus changes, it is at least partially in the
viewport after the change. Both
(Techniques for 5.4)
- Checkpoint 5.5 Confirm form submission. Allow configuration to
prompt the user to confirm (or cancel) any form submission. Configuration is
preferred, but it not required if forms can only ever be submitted on explicit
user request. Content only
(Techniques for 5.5)
- Checkpoint 5.6 Confirm fee links. Allow configuration to prompt the
user to confirm (or cancel) any payment that results from activation of a fee
link. Configuration is preferred, but is not required if fee links can only
ever be activated on explicit user request. Content only
(Techniques for 5.6)
- Checkpoint 6.8 DOM CSS access. For user agents that implement
Cascading Style Sheets (CSS), provide programmatic access to
those style sheets by conforming to the CSS module of the W3C Document Object
Model (DOM) Level 2 Style
Specification [DOM2STYLE] and exporting the
interfaces it defines. Content only
(Techniques for 6.8)
- Checkpoint 6.9 Timely access. Ensure that programmatic exchanges
proceed in a timely manner. Both
(Techniques for 6.9)
- Checkpoint 7.3 Operating environment conventions. Follow operating
environment conventions that benefit accessibility. In particular, follow
conventions that benefit accessibility for user interface design, keyboard
configuration, product installation, and documentation. User agent only
(Techniques for 7.3)
- Checkpoint
7.4 Input configuration indications.
Follow operating environment conventions to indicate the input configuration.
User agent only
(Techniques for 7.4)
- Checkpoint 8.2 Conform to specifications. Use and conform to either
(1) W3C Recommendations when they are available and appropriate for a task, or
(2) non-W3C specifications that enable the creation of content that conforms at
level A or better to the Web Content Accessibility Guidelines 1.0 [WCAG10]. When a
requirement of another specification contradicts a requirement of the current
document, the user agent may disregard the requirement of the other
specification and still satisfy this checkpoint. Content only
(Techniques for 8.2)
- Checkpoint 9.5 No events on focus change. Allow configuration so
that moving the content focus to or from an enabled element does not
automatically activate any explicitly associated event handlers. Content only
(Techniques for 9.5)
- Checkpoint 9.6 Show event handlers. For the element with content
focus, make available the list of input device event handlers explicitly
associated with the element. Content only
(Techniques for 9.6)
- Checkpoint 9.7 Move content focus optimally. 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 and reverse sequential
navigation to each element, in document order. The user agent must not include
disabled elements in the navigation order. Content only
(Techniques for 9.7)
- Checkpoint 9.8 Text search. Allow the user to search within
rendered text for a sequence of characters from the document character set.
Allow the user to start a forward search (in document order) from any selected
or focused location in content. When there is a match (1) move the viewport so
that the matched text content is within it, and (2) allow the user to search
for the next instance of the text from the location of the match. Alert the
user when there is no match, when the search reaches the end of content, and
prior to any wrapping. Provide a case-insensitive search option for text in
scripts (i.e., writing systems) where case is significant. Content only
(Techniques for 9.8)
- Checkpoint 9.9 Structured navigation. Allow the user to navigate
efficiently to and among important structural elements. Allow forward and
backward sequential navigation to important structural elements. Content only
(Techniques for 9.9)
- Checkpoint 10.4 Highlight special elements. Provide a mechanism for
highlighting all enabled elements, recently visited links, and fee links. 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, fonts, or text decorations, allow the user to choose from
among the full range of colors, fonts, or text decorations supported by the
operating environment. For an image map, the user agent must highlight the
image map as a whole and should allow configuration to highlight each enabled
region. Content only
(Techniques for 10.4)
- Checkpoint 10.5 Outline view. 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.). Content only
(Techniques for 10.5)
- Checkpoint
11.2 Current author bindings. Provide
a centralized view of the current author-specified input configuration
bindings. Content only
(Techniques for 11.2)
- Checkpoint 11.3 Override bindings. Allow the user to override any
binding that is part of the user agent default input configuration The user
agent is not required to allow the user to override conventional bindings for
the operating environment (e.g., for access to help). User agent only
(Techniques for 11.3)
- Checkpoint 11.4 Single key access. Allow the user to override any
binding in the default keyboard configuration with a binding to either a key
plus modifier keys or to a single-key. For each functionality in the set
required by checkpoint
11.5, allow the user to configure a single-key binding (i.e., one key press
performs the task, with zero modifier keys). If the number of physical keys on
the keyboard is less than the number of functionalities required by checkpoint 11.5, allow
single-key bindings for as many of those functionalities as possible. The
single-key binding requirements may be satisfied with a "single-key mode"
(i.e., a mode where the current bindings are replaced by a set of single-key
bindings). The user agent is not required to allow the user to override
conventional bindings for the operating environment (e.g., for access to help).
User agent only
(Techniques for 11.4)
- Checkpoint 11.5 Default binding requirements. Ensure that the
default input configuration includes bindings for the following functionalities
required by other checkpoints in this document: move focus to next enabled
element; move focus to previous enabled element; activate focused link; search
for text; search again for same text; 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 and
animations (including video and animated images). If the user agent supports
the following functionalities, the default input configuration must also
include bindings for them: next history state (forward); previous history state
(back); 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.
User agent only
(Techniques for 11.5)
- Checkpoint 11.6 User profiles. For the configuration requirements of
this document, allow the user to save user preferences in at least one user
profile. Allow the user to choose from among available default profiles,
profiles created by the same user, and no profile (i.e., the user agent default
settings). User agent only
(Techniques for 11.6)
- Checkpoint 12.4 Document changes. Document changes from the previous
version of the user agent to accessibility features, including accessibility
features of the user interface. User agent only
(Techniques for 12.4)
- Checkpoint
12.5 Dedicated section on
accessibility. In a dedicated section of the documentation, describe all
features of the user agent that benefit accessibility. User agent only
(Techniques for 12.5)
Priority 3 checkpoints
- Checkpoint 2.8 No repair text. Allow at least two configurations
for when the user agent recognizes that conditional content required by the
format specification is present but empty: (1) generate no repair text, or (2)
generate repair as described in
checkpoint 2.7. Content only
(Techniques for 2.8)
- Checkpoint
2.9 Render conditional content
automatically. Allow configuration to render all conditional content
automatically. The user agent is not required to render all conditional content
at the same time in a single viewport. Provide access to this content according
to format specifications or where unspecified, by applying one of the following
techniques described in
checkpoint 2.3: 1a, 2a, or 1b. Content only
(Techniques for 2.9)
- Checkpoint 2.10 Toggle placeholders. Once the user has viewed the
original author-supplied content associated with a placeholder, allow the user
to turn off the rendering of the author-supplied content. Content only
(Techniques for 2.10)
- Checkpoint
2.11 Alert unsupported language.
Allow configuration not to render content in unsupported natural languages
(including scripts, i.e., writing systems). Indicate to the user in context
that author-supplied content has not been rendered. Content only
(Techniques for 2.11)
- Checkpoint 5.7 Manual viewport close only. Allow configuration to
prompt the user to confirm (or cancel) closing any viewport that starts to
close without explicit user request. User agent only
(Techniques for 5.7)
- Checkpoint 9.10 Configure important elements. Allow configuration
and control of the set of important elements required by checkpoint 9.9 and checkpoint 10.5. Allow the
user to include and exclude element types in the set of elements. Content only
(Techniques for 9.10)
- Checkpoint 10.6 Provide link information. To help the user decide
whether to traverse a link, make available the following information about it:
link element content, link title, whether the link is internal to the resource
(e.g., the link is to a target in the same Web page), 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. Content only
(Techniques for 10.6)
- Checkpoint 10.8 Indicate rendering progress. Indicate the viewport's
position relative to 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.). For two-dimensional renderings, relative position includes both
vertical and horizontal positions. User agent only
(Techniques for 10.8)
- Checkpoint 11.7 Configure tool bars. For graphical user interfaces,
allow the user to configure the position of controls on tool bars of the user
agent user interface, to add or remove controls for the user interface from a
predefined set, and to restore the default user interface. User agent only
(Techniques for 11.7)
For the latest version of any
W3C specification please consult the list of
W3C Technical Reports at http://www.w3.org/TR.
- [DOM2CORE]
-
"Document Object Model (DOM) Level 2 Core Specification", A. Le
Hors, P. Le Hégaret, L. Wood, G. Nicol, J. Robie, M. Champion, S. Byrne,
eds., 13 November 2000. This W3C Recommendation is
http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/.
- [DOM2STYLE]
-
"Document Object Model (DOM) Level 2 Style Specification", V.
Apparao, P. Le Hégaret, C. Wilson, eds., 13 November 2000. This W3C
Recommendation is
http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113/.
- [UAAG10]
- "User Agent Accessibility
Guidelines 1.0", I. Jacobs, J. Gunderson, E. Hansen, eds. The latest
draft of the guidelines is available at http://www.w3.org/WAI/UA/UAAG10/.
- [WCAG10]
- "Web
Content Accessibility Guidelines 1.0", W. Chisholm, G. Vanderheiden,
and I. Jacobs, eds., 5 May 1999. This W3C Recommendation is
http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/.