- From: gregory j. rosmaita <oedipus@hicom.net>
- Date: Tue, 17 Jul 2001 21:41:24 -0400
- To: <w3c-wai-gl@w3.org>
aloha, y'all!
at thursday's telecon, gregg asked me to post the User Agent Accessibility
Guidelines' content-type and output modalities to the GL list... i asked
permission to wait until ian published a new draft, and on bastille day, 14
july 2001, the latest working draft of UAAG 1.0 was released... it lives
at:
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html>
the pertinent bits follows:
3.5 Content type labels
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html#content-type-labels
>
Each content type label defines a set of requirements related to
support for images, video, animations generally, visually displayed
text (in color), and synthesized speech.
VisualText
This content type label refers to all of the requirements
related to the visual rendering of text for the following
checkpoints: 3.3, 4.1, and 4.2. To conform, the user agent must
support visually rendered text.
ColorText
This content type label refers to all of the requirements
related to text foreground and background color for the
following checkpoint: 10.4. To conform, the user agent must
support more than one text foreground color and more than one
text background color.
Image
This content type label refers to all of the requirements
related to images (excluding animated images) for the following
checkpoints: 3.1, and 3.7. To conform, the user agent must
implement at least one image format. The image requirements
apply to content that is recognized as distinct and that,
according to the encoding format, may be rendered as a coherent
unit.
Animation
This content type label refers to all of the requirements
related to animations (including video and animated images) for
the following checkpoints: 3.2, 4.4, 4.5, 4.7, and 4.8. To
conform, the user agent must implement at least one animation
format. The animation requirements apply to animation content
that is recognized as distinct and that, according to the
encoding format, may be rendered as a coherent unit.
Video
This content type label refers to all of the requirements
related to video for the following checkpoints: 2.5, 2.6, and
3.2. To conform, the user agent must implement at least one
video format. The video requirements apply to video content
that is recognized as distinct and that, according to the
encoding format, may be rendered as a coherent unit.
Audio
This content type label refers to all of the requirements
related to audio for the following checkpoints: 2.5, 2.6, 3.2,
4.4, 4.5, 4.7, 4.8, 4.9, 4.10, and 4.11 To conform, the user
agent must implement at least one audio format. The audio
requirements apply to audio content that is recognized as
distinct and that, according to the encoding format, may be
rendered as a coherent unit.
Speech
This content type label refers to all of the requirements
related to synthesized speech for the following checkpoints:
4.12, 4.13, 4.14, 4.15, and 4.16. To conform, the user agent
must support synthesized speech.
Note: Some of the labels above require implementation of at least one
format (e.g., for images). This document does not require
implementation of specific formats, (e.g., PNG [PNG] versus SVG [SVG]
for images). However, please see the requirements of checkpoint 8.2.
3.6 Input modality labels
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html#input-modality-labe
ls>
Each input modality label defines a set of requirements related to
support for pointing device and voice input. Input device requirements
in this document are either stated generically (e.g., "input
configuration" requirements) or as keyboard-specific requirements
(e.g., "keyboard API").
Pointer
This input modality label refers to all of the input device
requirements of this document, applied to pointing device
input. For keyboard-specific requirements, substitute "pointing
device input" for "keyboard." The set of pointing device input
requirements does not include the requirements of checkpoint
11.4.
Voice
This input modality label refers to all of the input device
requirements of this document, applied to voice input. For
keyboard-specific requirements, substitute "voice input" for
"keyboard." The set of voice input requirements does not
include the requirements of checkpoint 11.4.
Note: Developers are encouraged to design user agents that are at
least partially operable through all three input modalities.
3.7 Selection label
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html#selection-label>
This document does not require the user agent to implement a selection
mechanism in order to conform. However, if the user agent does
implement a selection mechanism, in order to conform it must satisfy
the relevant portions of the following checkpoints:
6.5
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html#tech-api-alert>
7.1
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html#tech-selection-focu
s-conventions>
9.4
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html#tech-tracking-previ
ous-por>
10.2
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html#tech-selection-focu
s-highlight>
10.3
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html#tech-default-highli
ght>
and 5.4
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html#tech-track-selectio
n-focus>
The Selection label refers to the selection requirements of these
checkpoints.
If a user agent does not implement a selection mechanism, then a
well-formed claim must say so.
Note: This document does require implementation of both content focus
and user interface focus; see checkpoint 9.1
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html#tech-nav-content-fo
cus>
and checkpoint 9.2.
<http://www.w3.org/WAI/UA/WD-UAAG10-20010714/uaag10.html#tech-nav-ui-focus>
Received on Tuesday, 17 July 2001 21:40:27 UTC