Techniques for Authoring Tool Accessibility Guidelines
1.0
Draft Day? Month? 2002
Appendix B: Relative Priority Checkpoints
Editor of this chapter: Jan Richards
Table of Contents
Relative Priority ATAG Checkpoints Referring to ATAG
- ATAG 1.3: Ensure that when the tool automatically generates
markup it conforms to the W3C's Web Content Accessibility Guidelines 1.0
- ATAG 1.4: Ensure that templates provided by the tool conform
to the Web Content Accessibility Guidelines 1.0
- ATAG 3.1: Prompt the author to provide equivalent alternative
information (e.g., captions, auditory descriptions, and collated text transcripts
for video)
- ATAG 3.2: Help the author create structured content and
separate information from its presentation.
- ATAG 3.3: Ensure that prepackaged content conforms to the
Web Content Accessibility Guidelines 1.
- ATAG 4.1: Check for and inform the author of accessibility
problems.
- ATAG 4.2: Assist authors in correcting accessibility problems.
@@ Extra Stuff:
@@icon storage
Defintion of "Generates Markup Automatically":
@@@ Author did not directly choose either the type the markup element or the
attributes of the element..
WCAG Checkpoints
WCAG 1.1: Provide a text equivalent for every
non-text
element (e.g., via "alt", "longdesc", or in element content). This includes:
images, graphical representations of text (including symbols), image map regions,
animations (e.g., animated GIFs), applets and programmatic objects, ascii
art, frames, scripts, images used as list bullets, spacers, graphical buttons,
sounds (played with or without user interaction), stand-alone audio files, audio
tracks of video, and video. [Priority 1]
ATAG 1.3 (Generating markup automatically):
When non-text
elements are generated during authoring or conversion,
the appropriate text equivalent markup (i.e. labels and descriptions for images,
etc.) is included. The source of the content for the text equivalents depends
on whether it was the tool or the author that chose the source of non-text
object (image file, sound file, video file, etc.). If it was the tool, and
the function of the object is known with certainty, the tool may
insert equivalent text content that has been written specifically for that
object by the author or by the distributer of the object. If it was the author
that chose the object, see ATAG 3.1, below.
When non-text
element creating program code (e.g. code that sends non-text element markup
to a user agent) is generated automatically, the code is specified in such
a way that it will include the appropriate text equivalent markup with the
non-text-element. The source of the content for the text equivalents depends
on whether it was the tool or the author that chose the source of non-text
object (image file, sound file, video file, etc.). If it was the tool, and
the function of the object is known with certainty, the tool may
generate code that inserts equivalent text content that has been written specifically
for that object by the author or by the distributer of the object. If it was
the author that chose the object, see ATAG 3.1, below.
ATAG 1.4/3.3 (Templates/pre-packaged content):
Templates and other pre-packaged content are authored following the techniques
for WCAG 1.1.
Template program code that generates markup is written so that the markup
generated follows the techniques
for WCAG 1.1.
ATAG 3.1 (Prompting for equivalent alternatives):
When the source object (i.e. image file, sound file, video file, etc.) of
a non-text element is chosen by the author, the tool has three options: (1)
if the function is known (e.g. the author is choosing an image for a button
that is known to have a "home" function), the tool may, if it has
them, use text equivalents pre-written for this function, (2) if the function
is unknown, but the object has previously associated text equivalent content
(provided by the distributer or saved from a previous entry by the author),
the tool may prompt
the author as to whether the equivalents are suitable to the current authoring
context, or (3) if the function is not known and the object does not have
any previously associated text equivalents, then the tool must prompt
the author to compose (or link to) a text equivalent. [T0015a].
ATAG 3.2 (Creating structured content and separating information from presentation):
Meeting the other ATAG checkpoints listed here will serve to separate
information from its presentation, because information presented textually
can be reformatted in ways that information presented non-textually cannot.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques:
WCAG 1.2: Provide redundant text links for
each active region of a server-side image map. [Priority 1].
ATAG 1.3 (Generating markup automatically):
When server-side image maps are generated during authoring
or conversion, the tool may automatically define the redundant text links
using the URI's in the image map file. Although it is possible to generate
the link text automatically from the file name of the URI, this text may not
be meaningful, so most authors would probably prefer to have the option to
edit the link text as part of a prompt. For more on prompting, see ATAG 3.1,
below.
???
ATAG 1.4/3.3 (Templates/pre-packaged content):
Templates and other pre-packaged content are authored following the techniques
for WCAG 1.2.
Template program code that generates markup is written so that the markup
generated follows the techniques
for WCAG 1.2.
ATAG 3.1 (Prompting for equivalent alternatives):
When the server-side image map targets have been located in the image map
file, the tool may prompt
the author to enter text for the link. In addition several potential sources
of default link text include: (1) previous link text used for this target,
(2) the title of the target document and (3) the file name of the URI.
The prompt might also include a query to the author regarding the location
and styling of the redundant links.
ATAG 3.2 (Creating structured content and separating information from presentation):
Meeting the other ATAG checkpoints listed here will serve to separate
information from its presentation, because information presented textually
can be reformatted in ways that information presented non-textually cannot.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 1.2.1
Verify that a server-side image map has associated text links
WCAG 1.3: Until
user agents can automatically read aloud the text equivalent of a visual
track, provide an auditory description of the important information of the visual
track of a multimedia presentation. [Priority 1]
ATAG 1.3 (Generating markup automatically):
When multimedia presentations are generated during authoring
or conversion, auditory descriptions are included. The source of the auditory
descriptions depends on whether it was the tool or the author that chose the
source of multimedia presentation (video file, etc.). If it was the tool,
and the function of the object is known with certainty, the
tool may insert an auditory description that has been recorded specifically
for that object by the author or by the distributer of the object. If it was
the author that chose the object, see ATAG 3.1, below.
When non-text
element creating program code (e.g. code that sends multimedia containing
markup to a user agent) is generated automatically, the code is specified
in such a way that it will include the appropriate audiotory descriptions
markup with the multimedia element. The source of the auditory descriptions
depends on whether it was the tool or the author that chose the source of
multimedia presentation (video file, etc.). If it was the tool, and
the function of the object is known with certainty, the tool may
generate code that inserts an auditory description that has been recorded
specifically for that object by the author or by the distributer of the object.
If it was the author that chose the object, see ATAG 3.1, below.
ATAG 1.4/3.3 (Templates/pre-packaged content):
Templates and other pre-packaged content are authored following the techniques
for WCAG 1.3.
Template program code that generates markup is written so that the markup
generated follows the techniques
for WCAG 1.3.
ATAG 3.1 (Prompting for equivalent alternatives):
@@
ATAG 3.2 (Creating structured content and separating information from presentation):
Not applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 1.3.1:
Verify that multimedia have audio descriptions
WCAG 1.4: For any time-based multimedia presentation
(e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions
or auditory descriptions of the visual track) with the presentation. [Priority 1]
ATAG 1.3 (Generating markup automatically):
@@
ATAG 1.4/3.3 (Templates/pre-packaged content):
Templates and other pre-packaged content are authored following the techniques
for WCAG 1.4.
Template program code that generates markup is written so that the markup
generated follows the techniques
for WCAG 1.4.
ATAG 3.1 (Prompting for equivalent alternatives):
@@
ATAG 3.2 (Creating structured content and separating information from presentation):
Meeting the other ATAG checkpoints listed here will serve to separate
information from its presentation, because information presented textually
can be reformatted in ways that information presented non-textually cannot.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques:
1.4.1 Verify
that multimedia have synchronized equivalents
1.4.2 Check SMIL files for synchronized media
WCAG 1.5: Until
user agents render text equivalents for client-side image map links, provide
redundant text links for each active region of a client-side image map. [Priority 3]
ATAG 1.3 (Generating markup automatically):
When client-side image maps are generated during authoring
or conversion, the tool may automatically define the redundant text links
using the URI's in the map element. If a text label exists for the map region,
that its probably the preferred link text. Although it is possible to generate
the link text automatically from the file name of the URI, this text may not
be meaningful, so most authors would probably prefer to have the option to
edit the link text as part of a prompt. For more on prompting, see ATAG 3.1,
below.
???
ATAG 1.4/3.3 (Templates/pre-packaged content):
Templates and other pre-packaged content are authored following the techniques
for WCAG 1.5.
Template program code that generates markup is written so that the markup
generated follows the techniques
for WCAG 1.5.
ATAG 3.1 (Prompting for equivalent alternatives):
When the client-side image map targets have been located in the image map
file, the tool may prompt
the author to enter text for the link. In addition several potential sources
of default link text include: (1) image map region label, (2) previous link
text used for this target, (3) the title of the target document and (4) the
file name of the URI.
The prompt might also include a query to the author regarding the location
and styling of the redundant links.
ATAG 3.2 (Creating structured content and separating information from presentation):
Meeting the other ATAG checkpoints listed here will serve to separate
information from its presentation, because information presented textually
can be reformatted in ways that information presented non-textually cannot.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique:
1.5.1 Verify that text
links are provided for client-side image maps
@@ Done to here.
WCAG 2.1: Ensure that all information conveyed
with color is also available without color, for example from context or markup.
[Priority 1]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Templates and other pre-packaged content are authored following the techniques
for WCAG 2.1.
Template program code that generates markup is written so that the markup
generated follows the techniques
for WCAG 2.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 2.1.1
Verify that information conveyed with color is available without color
WCAG 2.2: Ensure that foreground and background
color combinations provide sufficient contrast when viewed by someone having
color deficits or when viewed on a black and white screen. [Priority 2
for images, Priority 3 for text]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 2.2.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 2.2.1
Test the color attributes of the following elements for visibility
WCAG 3.1: When an appropriate markup language
exists, use markup rather than images to convey information. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 3.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 3.1.1
Verify that elements do not need to be converted to an appropriate markup
language
WCAG 3.2: Create documents that validate to
published formal grammars. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 3.2.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 3.2.1
Check document for public text identifier
WCAG 3.3: Use style sheets to control layout
and presentation. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 3.3.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 3.3.1
Check document for use of style sheets.
WCAG 3.4: Use relative rather than absolute
units in markup language attribute values and style sheet property values. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 3.4.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 3.4.1
Check document for relative units of measure.
WCAG 3.5: Use header elements to convey document
structure and use them according to specification. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 3.5.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques:
3.5.1 Check document
for header nesting
3.5.2 Check document for missing header markup
3.5.3 Verify that header elements are not used for formatting
WCAG 3.6: Mark up lists and list items properly.
[Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 3.6.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 3.6.1
Check that list elements are within a list container and well nested
WCAG 3.7: Mark up quotations. Do not use quotation
markup for formatting effects such as indentation. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 3.7.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques:
3.7.1 Verify instances where
quote markup should be used
3.7.2 Verify that Q and BLOCKQUOTE are used properly
3.7.3 Verify that BLOCKQUOTE is not used for formatting
WCAG 4.1: Clearly identify changes in the
natural language of a document's text and any
text equivalents (e.g., captions). [Priority 1]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 4.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 4.1.1
Verify changes in the natural language of document
WCAG 4.2: Specify the expansion of each abbreviation
or acronym in a document where it first occurs. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 4.2.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 4.2.1
Verify that abbreviations and acronyms need expanding
WCAG 4.3: Identify the primary natural language
of a document. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 4.3.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 4.3.1
Verify the primary language of the document
WCAG 5.1: For data tables, identify row and
column headers. [Priority 1]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 5.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques:
5.1.1 Determine the purpose
of the table
5.1.2 Check data table for row and column headers
WCAG 5.2: For data tables that have two or
more logical levels of row or column headers, use markup to associate data cells
and header cells. [Priority 1]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 5.2.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 5.2.1
Check data tables for multiple levels of row and column headers
WCAG 5.3: Do not use tables for layout unless
the table makes sense when linearized. Otherwise, if the table does not make
sense, provide an alternative equivalent (which may be a
linearized version). [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 5.3.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 5.3.1
Verify that layout tables make sense when linearized
WCAG 5.4: If a table is used for layout, do
not use any structural markup for the purpose of visual formatting. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 5.4.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 5.4.1
Check layout tables for structural markup
WCAG 5.5: Provide summaries for tables. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 5.5.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques:
5.5.1 Check TABLE
elements for valid "summary" attribute
5.5.2 Check TABLE elements for valid CAPTION element.
WCAG 5.6: Provide abbreviations for header
labels. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 5.6.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 5.6.1
Check tables for header abbreviations
WCAG 6.1: Organize documents so they may be
read without style sheets. For example, when an HTML document is rendered without
associated style sheets, it must still be possible to read the document. [Priority 1]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 6.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 6.1.1
Verify that the document is readable when style sheets are not applied.
WCAG 6.2: Ensure that equivalents for dynamic
content are updated when the dynamic content changes. [Priority 1]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 6.2.
ATAG 3.1 (Prompting for equivalent alternatives):
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques:
6.2.1 Check the
source of FRAME and IFRAME elements for valid
markup files
6.2.2 Verify that equivalents of dynamic content are updated and available
as often as the dynamic content
WCAG 6.3: Ensure that pages are usable when
scripts, applets, or other programmatic objects are turned off or not supported.
If this is not possible, provide equivalent information on an alternative accessible
page. [Priority 1]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 6.3.
ATAG 3.1 (Prompting for equivalent alternatives):
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 6.3.1
Verify that the page is usable when programmatic objects are disabled.
WCAG 6.4: For scripts and applets, ensure
that event handlers are input device-independent. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 6.4.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 6.4.1
Check for device independent event handlers
WCAG 6.5: Ensure that dynamic content is accessible
or provide an alternative presentation or page. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 6.5.
ATAG 3.1 (Prompting for equivalent alternatives):
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 6.5.1
Check that a NOFRAMES element exists within each FRAMESET
WCAG 7.1: Until
user agents allow users to control flickering, avoid causing the
screen to flicker. [Priority 1]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 7.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 7.1.1
Verify that the page does not cause flicker
WCAG 7.2: Until
user agents allow users to control blinking, avoid causing content
to blink (i.e., change presentation at a regular rate, such as turning on and
off). [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 7.2.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 7.2.1
Check for BLINK elements
WCAG 7.3: Until
user agents allow users to freeze moving content, avoid movement
in pages. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 7.3.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques:
7.3.1 Check for MARQUEE
elements
7.3.2 Verify that programmatic objects do not create moving content
WCAG 7.4: Until
user agents provide the ability to stop the refresh, do not create
periodically auto-refreshing pages. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for checkpoint 7.4.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 7.4.1
Remove auto-refresh attributes from META elements
WCAG 7.5: Until
user agents provide the ability to stop auto-redirect, do not use
markup to redirect pages automatically. Instead, configure the server to perform
redirects. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 7.5.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 7.5.1
Check auto-redirect attributes on META elements
WCAG 8.1: Make programmatic elements such
as scripts and applets directly accessible or compatible with assistive technologies
[Priority 1 if functionality is important
and not presented elsewhere, otherwise Priority 2.]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 8.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 8.1.1
Verify that programmatic objects are directly accessible
WCAG 9.1: Provide client-side image maps instead
of server-side image maps except where the regions cannot be defined with an
available geometric shape. [Priority 1]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 9.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 9.1.1
Check for use of server-side image maps
WCAG 9.2: Ensure that any element that has
its own interface can be operated in a device-independent manner. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 9.2.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
No automated evaluation and repair techniques identified.
WCAG 9.3: For scripts, specify logical event
handlers rather than device-dependent event handlers. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 9.3.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 9.3.1
Check scripts for logical event handlers
WCAG 9.4: Create a logical tab order through
links, form controls, and objects. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 9.4.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 9.4.1
Check for "tabindex" attribute
WCAG 9.5: Provide keyboard shortcuts to important
links (including those in client-side
image maps), form controls, and groups of form controls. [Priority 3]
For example, in HTML, specify shortcuts via the "accesskey" attribute.
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 9.5.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 9.5.1
Check for "accesskey" attribute
WCAG 10.1: Until
user agents allow users to turn off spawned windows, do not cause
pop-ups or other windows to appear and do not change the current window without
informing the user. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 10.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques:
10.1.1 Check A
and AREA elements for valid "target"
attributes
10.1.2 Verify that scripts do not spawn new windows
WCAG 10.2: Until
user agents support explicit associations between labels and form
controls, for all form controls with implicitly associated labels, ensure that
the label is properly positioned. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 10.2.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 10.2.1
Verify that LABEL elements are properly positioned
WCAG 10.3: Until
user agents (including assistive technologies) render side-by-side
text correctly, provide a linear text alternative (on the current page or some
other) for all tables that lay out text in parallel, word-wrapped columns.
[Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 10.3.
ATAG 3.1 (Prompting for equivalent alternatives):
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 10.3.1
Verify that a linearized version of tables used for layout is provided
WCAG 10.4: Until
user agents handle empty controls correctly, include default, place-holding
characters in edit boxes and text areas. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 10.4.
ATAG 3.1 (Prompting for equivalent alternatives):
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 10.4.1
Check for valid default values of INPUT, TEXTAREA,
and SELECT elements
WCAG 10.5: Until
user agents (including assistive technologies) render adjacent links
distinctly, include non-link, printable characters (surrounded by spaces) between
adjacent links. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 10.5.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 10.5.1
Check for non-whitespace characters between consecutive A elements
WCAG 11.1: Use W3C technologies when they
are available and appropriate for a task and use the latest versions when supported.
[Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 11.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 11.1.1
Verify that W3C technologies are used, where possible and appropriate
WCAG 11.2: Avoid deprecated features of W3C
technologies. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 11.2.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 11.2.1
Check for deprecated features of W3C technologies
WCAG 11.3: Provide information so that users
may receive documents according to their preferences (e.g., language, content
type, etc.) [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 11.3.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 11.3.1
Check that documents are served per user preferences
WCAG 11.4: If, after
best efforts, you cannot create an accessible
page, provide a link to an alternative page that uses W3C technologies, is accessible,
has equivalent
information (or functionality), and is updated as often as the inaccessible
(original) page. [Priority 1]. Techniques
for checkpoint 11.4.
ATAG 1.3 (Generating markup automatically):
Not Applicable. (Generated content should always be accessible.)
ATAG 1.4/3.3 (Templates/pre-packaged content):
Not Applicable. (Pre-packaged content and templates should always be
accessible.)
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 11.4.1
Verify that the page has passed all checkpoints of the desired conformance
level
WCAG 12.1: Title each frame to facilitate
frame identification and navigation. [Priority 1]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 12.1.
ATAG 3.1 (Prompting for equivalent alternatives):
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques: 12.1.1
Check FRAME elements for valid "title"
attributes
WCAG 12.2: Describe the purpose of frames
and how frames relate to each other if it is not obvious by frame titles alone.
[Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 12.2.
ATAG 3.1 (Prompting for equivalent alternatives):
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
No automated evaluation and repair techniques identified.
WCAG 12.3: Divide large blocks of information
into more manageable groups where natural and appropriate. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 12.3.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
No automated evaluation and repair techniques identified.
WCAG 12.4: Associate labels explicitly with
their controls. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 12.4.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques: 12.4.1
Check LABEL elements for valid "for" attribute
values
WCAG 13.1: Clearly identify the target of
each link. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 13.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 13.1.1
Verify that the target of each link is clearly identified
WCAG 13.2: Provide metadata to add semantic
information to pages and sites. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 13.2.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique: 13.2.1
Check for META, ADDRESS, TITLE and
LINK elements
WCAG 13.3: Provide information about the general
layout of a site (e.g., a site map or table of contents). [Priority 2]
In describing site layout, highlight and explain available accessibility features.
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 13.3.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
No automated evaluation and repair techniques identified.
WCAG 13.4: Use navigation mechanisms in a
consistent manner. [Priority 2]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 13.4.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
No automated evaluation and repair techniques identified.
WCAG 13.5: Provide navigation bars to highlight
and give access to the navigation mechanism. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 13.5.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
No automated evaluation and repair techniques identified.
WCAG 13.6: Group related links, identify the
group (for user agents), and, until
user agents do so, provide a way to bypass the group. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 13.6.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique:
13.6.1 Verify if links
should be grouped
WCAG 13.7: If search functions are provided,
enable different types of searches for different skill levels and preferences.
[Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 13.7.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique:
13.7.1 Verify that search
functions enable a variety of skill levels and preferences
WCAG 13.8: Place distinguishing information
at the beginning of headings, paragraphs, lists, etc. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 13.8.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
No automated evaluation and repair techniques identified.
WCAG 13.9: Provide information about
document collections (i.e., documents comprising multiple pages.). [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 13.9.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique:
13.9.1 Verify that
information about document collections is provided
WCAG 13.10: Provide a means to skip
over multi-line ASCII art. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 13.10.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Technique:
13.10.1 Verify that
one can skip over multi-line ASCII art
WCAG 14.1: Use the clearest and simplest language
appropriate for a site's content. [Priority 1]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 14.1.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
No automated evaluation and repair techniques identified.
WCAG 14.2: Supplement text with graphic or
auditory presentations where they will facilitate comprehension of the page.
[Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 14.2.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
Not Applicable.
ATAG 4.1/4.2 (Checking and correcting):
No automated evaluation and repair techniques identified.
WCAG 14.3: Create a style of presentation
that is consistent across pages. [Priority 3]
ATAG 1.3 (Generating markup automatically):
ATAG 1.4/3.3 (Templates/pre-packaged content):
Follow Techniques
for WCAG checkpoint 14.3.
ATAG 3.1 (Prompting for equivalent alternatives):
Not Applicable.
ATAG 3.2 (Creating structured content and separating information from presentation):
The easiest way to achieve a consistent style of presentation across
pages is to make use of style sheets. This has the added benefit of helping
to separate information from its presentation.
ATAG 4.1/4.2 (Checking and correcting):
See the following AERT Techniques:
14.3.1 Verify that a consistent
style of presentation is used across pages