[previous section: implementation techniques for guideline 2] [contents of this page] [full techniques contents] [next chapter: implementation techniques for guideline 4]
Charles McCathieNevile
Copyright ©1999 - 2001 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
abbr
or acronym
).longdesc
for each frame
in a frameset.noframes
section to
the frameset. Encourage the author to include sufficient links
to navigate the site, and relevant information. For example,
where a frameset defines a navigation frame and a welcome page,
include the content of each of these frames in the
noframes
.select
, checkbox
or
radio
boxes) ask the author to identify
subgroupsinput
and textarea
elements)Tables: In Amaya, when the author creates a table, a dialog is generated which asks for number of rows, columns, border width. The author selects the appropriate information and a table is created. The cursor is placed at the position of the table caption. The status line, which appears at the bottom of the image, shows that the position is in the caption element of the table.
Use formats that allow for accessible annotation to be included in
the files, such as SMIL, PNG, and SVG.[Required] @@
Provide long descriptions, and associated text files with
appropriate text equivalent in
clip-art collections.[Required] @@
Provide video description files with prepackaged video.[Required] @@
Provide text caption files for prepackaged audio, or video with
auditory track(s).[Required] @@
IMG
, or specified that none is required, default to having
no "alt"
attribute, so that an accessibility problem will
be noted. Refer also to checkpoint 4.1.[Required] @@
Maintain a database registry that associates object identity
information with alternative information. Whenever an object is used
and an equivalent alternative is collected (as per checkpoint 3.1) add the object (or identifying
information) and the alternative information to the database. In the
case of a text equivalent, the
alternate information may be stored in the document source. For more
substantial information (such as video captions or audio descriptions),
the information may be stored externally and linked from the document
source. Allow different alternative information to be associated with a
single object.(Suggested)
If such a database is maintained, the pre-written descriptions can
be presented to the author as default text in the appropriate field,
whenever one of the associated files is inserted into the author's
document. This satisfies ATAG 3.4 because the equivalent alternatives
are not automatically generated and they are only reused with author
confirmation.(Suggested)
If no previous association is found, the field should be left empty
(i.e., no purely rule-generated alternative information should be
used). Note: The term "default" implies that the
alternative information is offered for the author's approval. The term
does not imply that the default alternative information is
automatically placed without the author's approval. Such automatic
placement may only occur when in situations where the function of the
object is known with certainty, per checkpoint
3.4. Such a situation might arise in the case of a "navigation bar
builder" that places a navigation bar at the bottom of every page on a
site. In this case, it would be appropriate to use the same "alt"-text
automatically for every instance of a particular image (with the same
target) on every page.(Suggested)
The pre-written alternative information provided for all packaged
multimedia files (per checkpoint 3.3) should be included in the database.
This would allow the alternative information to be automatically
retrieved whenever the author selected one of the packaged objects for
insertion. An important benefit of the system would be the ease of
adding a keyword search capability that would allow efficient location
of multimedia based on its alternative information.(Suggested)
[previous section] [top of this page] [full techniques contents] [next]