Copyright ©2002 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
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 is a Public Working Draft of a document that defines the RelativePriority checkpoints in ATAG 2.0 (now a working draft) will refer to the various versions of WCAG.
Please send comments about this document to the public mailing list: w3c-wai-au@w3.org.
For information about the current activities of the working group, please refer to the AUWG home page. This page includes an explanation of the inter-relation of each document as well as minutes and previous drafts.
The Authoring Tools Accessibility Guidelines version 2.0 (ATAG20) refers to the Web Content Accessibility Guidelines (WCAG) without specifying a version number. This allows ATAG 2.0 to remain in effect as new versions of WCAG are released.
The purpose of this document is to provide a bridge between ATAG 2.0 and the most current version of WCAG. This includes:
Note: When performing an ATAG 2.0 conformance assessment for an authoring tool, you must always specify the version of WCAG that was used to determine conformance of the Relative Priority ATAG 2.0 checkpoints.
Relative Priority Scheme:
WCAG 2.0 establishes four conformance levels for each of its checkpoints: not met, minimum (most important requirements met), level 2 and level 3 (least important requirements met). The ATAG 2.0 relative priority level reflects this as follows:
- Relative Priority 1: The ATAG 2.0 checkpoint satisfies all relevant WCAG 2.0 checkpoint requirements to at least the minimum level.
- Relative Priority 2: The ATAG 2.0 checkpoint satisfies all relevant WCAG 2.0 checkpoint requirements to at least level 2.
- Relative Priority 3: The ATAG 2.0 checkpoint satisfies all relevant WCAG 2.0 checkpoint requirements to at least level 3.
WCAG 2.0 Checkpoint Applicability to ATAG 2.0 Relative Priority Checkpoints:
ATAG 2.0 Relative Priority Checkpoints WCAG 2.0 Checkpoint Applicability
@@Proposed by JR@@2.5 Ensure that when the tool automatically generates content it conforms to the WCAG.
(ATAG Techniques for 2.5)All WCAG 2.0 checkpoints. (WCAG Techniques) 2.6 Ensure that all pre-authored content for the tool conforms to WCAG.
(ATAG Techniques for 2.6)All WCAG 2.0 checkpoints. (WCAG Techniques)
3.1 Prompt the author to provide equivalent alternative information (e.g., captions, auditory descriptions, and collated text transcripts for video).
- 1.1: For all non-text content that can be expressed in words, provide a text equivalent of the function or information the non-text content was intended to convey. (WCAG Techniques for 1.1)
- 1.2: Provide synchronized media equivalents for time-dependent presentations. (WCAG Techniques for 1.1)
- 1.6: Provide information needed for unambiguous decoding of the characters and words in the content.
- 4.2: Supplement text with non-text content.
- 4.3: Annotate complex, abbreviated, or unfamiliar information with summaries and definitions.
- 5.4: Ensure that user interfaces are accessible or provide an accessible alternative.
3.2 Help the author create structured content and separate information from its presentation.
- 1.3: Make all content and structure available independently of presentation.
- 1.4: Emphasize structure through presentation(s), positioning, and labels.
- 2.2: Allow users to control any time limits on their reading, interaction or responses unless control is not possible due to the nature of real-time events or competition.
- 3.1: Provide structure within content.
3.5 Check for and inform the author of accessibility problems. All WCAG 2.0 checkpoints. 3.6 Assist authors in correcting accessibility problems. All WCAG 2.0 checkpoints. 3.9 Document the process of using the tool to produce accessible content. All WCAG 2.0 checkpoints.
Relative Priority Scheme:
WCAG 1.0 establishes three priority levels: Priority 1 (most important requirements), Priority 2 and Priority 3 (least important requirements). The ATAG 2.0 relative priority level reflects this as follows:
- Relative Priority 1: The ATAG 2.0 checkpoint satisfies all relevant WCAG 1.0 Priority 1 checkpoints.
- Relative Priority 2: The ATAG 2.0 checkpoint satisfies all relevant WCAG 1.0 Priority 1 and 2 checkpoints.
- Relative Priority 3: The ATAG 2.0 checkpoint satisfies all relevant WCAG 1.0 checkpoints.
WCAG 2.0 Checkpoint Applicability to ATAG 1.0 Relative Priority Checkpoints:
ATAG 1.0 Relative Priority Checkpoints WCAG 1.0 Checkpoint Applicability 2.5 Ensure that when the tool automatically generates content it conforms to the WCAG. All WCAG 1.0 checkpoints except for:
- WCAG 11.4 (P1) Keep alternative pages synchronized with original pages.
2.6 Ensure that all pre-authored content for the tool conforms to WCAG. All WCAG 1.0 checkpoints except for:
- WCAG 11.4 (P1) Keep alternative pages synchronized with original pages.
3.1 Prompt the author to provide equivalent alternative information (e.g., captions, auditory descriptions, and collated text transcripts for video).
- 1.1 (P1) Provide text equivalent* for non-text elements.
- 1.2 (P1) Provide redundant text links* for server-side image map areas.
- 1.3 (P1) Provide auditory descriptions* for multimedia.
- 1.5 (P3) Provide redundant text links* for client-side image map areas.
- 5.3 (P2) Avoid layout tables or provide an alternative equivalent*.
- 5.5 (P3) Provide summaries* for tables.
- 6.2 (P1) Keep equivalents* for dynamic content up to date.
- 6.3 (P1) Ensure pages usable without scripts, applets, programmatic objects. Else, provide equivalent information*.
- 6.5 (P2) Ensure dynamic content is accessible or provide an alternative presentation*.
- 10.4 (P3) Include place-holding text* in edit boxes and text areas.
- 12.1 (P1) Title* each generated frame.
- 12.2 (P2) Describe* the purpose and relation of frames.
- 13.1(P2) Clearly identify the target* of each link.
- 13.2 (P2) Provide metadata* to pages and sites.
- 13.3 (P2) Provide information* about the general layout of a site.
- 13.9 (P3) Provide information* about document collections (i.e., documents comprising multiple pages.).
- 14.2 (P3) Supplement text with graphic or auditory presentations*.
3.2 Help the author create structured content and separate information from its presentation.
- 2.1(P1) Ensure information provided with color is also available without color.
- 2.2 (Images: P2, Text: P3) Use sufficient foreground/background contrast.
- 3.1 (P2) Use markup rather than images to convey information.
- 3.2 (P2) Validate to published formal grammars.
- 3.3 (P2) Use style sheets.
- 3.4 (P2) Use relative units.
- 3.5 (P2) Use header elements.
- 3.6 (P2) Use lists and list items properly.
- 3.7 (P2) Use quotations properly.
- 4.1 (P1) Identify natural language changes.
- 4.2 (P3) Specify abbreviation or acronym expansions.
- 4.3 (P3) Identify the primary natural language of documents.
- 5.1 (P1) Identify data table row and column headers.
- 5.2 (P1) Associate data cells and header cells in complex data tables.
- 5.3 (P2) Avoid layout tables or provide an alternative equivalent*.
- 5.4 (P2) Avoid structural markup in layout tables.
- 5.6 (P3) Provide abbreviations for table header labels.
- 6.1 (P1) Organize documents to be read without style sheets.
- 6.3 (P1) Ensure pages usable without scripts, applets, programmatic objects. Else, provide equivalent information*.
- 6.4 (P2) Ensure script and applet event handlers are input device-independent.
- 6.5 (P2) Ensure dynamic content is accessible or provide an alternative presentation*.
- 7.1 (P1) Avoid causing screen to flicker.
- 7.2 (P2) Avoid causing content to blink.
- 7.3 (P2) Avoid causing movement on the screen.
- 7.4 (P2) Avoid periodically auto-refreshing pages.
- 7.5 (P2) Avoid redirecting pages automatically. Use server redirects.
- 9.1 (P1) Use client-side image maps instead of server-side image maps.
- 9.2 (P2) Ensure element with own interface are input device-independent.
- 9.3 (P2) Specify logical (device independent) event handlers for scripts.
- 9.4(P3) Create a logical tab order.
- 9.5 (P3) Provide keyboard shortcuts to important elements.
- 10.1 (P2) Avoid spawned windows.
- 10.3 (P3) Provide a linear text alternative to tables with text in parallel, word-wrapped columns.
- 11.2 (P2) Avoid deprecated features of W3C technologies.
- 11.3 (P3) Include metadata information (e.g., language, content type, etc.)
- 12.2 (P2) Describe* the purpose and relation of frames.
- 12.3 (P2) Divide large blocks of information into manageable groups.
- 12.4 (P2) Associate labels explicitly with their controls.
- 13.2 (P2) Provide metadata* to pages and sites.
- 13.6 (P3) Group, identify, and provide a way to bypass related links.
- 14.1 (P1) Use clearest and simplest language appropriate.
3.5 Check for and inform the author of accessibility problems. All WCAG 1.0 checkpoint 3.6 Assist authors in correcting accessibility problems. All WCAG 1.0 checkpoint 3.9 Document the process of using the tool to produce accessible content. All WCAG 1.0 checkpoint