Web Content Accessibility Guidelines 2.0 -- Reorganization 5 - Single-A

Single-A Success Criteria for Guideline 1.1

1. non-text content that can be expressed in words has a text-equivalent explicitly associated with it. [Category 1]

   • The text equivalent fulfills the same function as the author intended for the non-text content (i.e. it presents all of the intended information and/or achieves the same function of the non-text content).

2. non-text content that can not be expressed in words has a descriptive label provided as its text-equivalent. [Category 1]

Single-A Success Criteria for Guideline 1.2

Editorial Note (06/10/03): There is discussion about moving some of the current success criteria from Required to Best Practice or to an Extended checkpoint. The issue stems from trying to apply the success criteria to every Web cam, newscast, and home broadcast. Another approach is to allow a conformance claim to state, for example, "All pages and applications on this site meet the Core checkpoints of WCAG 2.0 except the Web cam at http://example.org/webcam/."

1. an audio description is provided. [Category 1]
2. all significant dialogue and sounds are captioned [Category 1]

   Exception:

   If the Web content is real-time and audio-only and not time-sensitive and not interactive a transcript or other non-audio equivalent is sufficient.

   Editorial Note: This exception also applies to item 3.

3. descriptions and captions are synchronized with the events they represent. [Category 1]
4. if the Web content is real-time video with audio, real-time captions are provided unless the content: [Category 1]

   • is a music program that is primarily non-vocal

5. if the Web content is real-time non-interactive video (e.g., a Webcam of ambient conditions), either provide an equivalent that conforms to checkpoint 1.1 (e.g., an ongoing update of weather conditions) or link to an equivalent that conforms to checkpoint 1.1 (e.g., a link to a weather Web site). [Category 1]
6. if a pure audio or pure video presentation requires a user to respond interactively at specific times in the presentation, then a time-synchronized equivalent (audio, visual or text) presentation is provided. [Category 1]

Single-A Success Criteria for Guideline 1.3

1. the following can be derived programmatically (i.e. through a markup or data model that is assistive technology compatible) from the content without requiring user interpretation of presentation. [Category 1]

   1. any hierarchical elements and relationships, such as headings, paragraphs and lists

   2. any non-hierarchical relationships between elements such as cross-references and linkages, associations between labels and controls, associations between cells and their headers, etc.

   3. any emphasis

2. any information presented through color is also available without color (e.g. through context or markup or non-color dependent coding). [I#317] [Category 1]
3. text content is not presented over a background image or pattern OR the text is easily readable when the page is viewed in black and white (no grayscale). [Category 1]

Single-A Success Criteria for Guideline 1.4

Editorial Note: The CKW reorganization suggested that this checkpoint be combined with checkpoint 3.2. [I#442]

1. text in the content is provided in Unicode or sufficient information is provided so that it can be automatically mapped back to Unicode. [Category 1]

Single-A Success Criteria for Guideline 2.1

1. all of the functionality of the content, where the functionality or its outcome can be expressed in words, is operable at a minimum through a keyboard or keyboard interface. [Category 1]

   Note:

   refer to checkpoint 4.3 for information regarding user agent support.

Single-A Success Criteria for Guideline 2.2

1. content is designed so that time limits are not an essential part of interaction or at least one of the following is true for each time limit: [Category 1]

   • the user is allowed to deactivate the time limits,

   • or the user is allowed to adjust the time limit over a wide range which is at least ten times or default setting or average user's preference,

   • or the user is warned before time expires and given at least 10 seconds to extend the time limit,

   • or the time limit is due to a real-time event (e.g. auction) and no alternative to the time limit is possible,

   • or the time limit is part of a competitive activity where timing is an essential part of the activity (e.g. competitive gaming or time based testing).

Single-A Success Criteria for Guideline 2.3

Editorial Note (06/10/03): This Checkpoint is currently included in the Core set of Checkpoints because the WCAG WG expects that it will be possible to test content for flicker and the result will be a flicker rate in Hz that can be stored in a machine-readable format. If the assumption regarding a testing tool does not hold at time of final review of these guidelines, this checkpoint will be moved to the Extended set of Checkpoints."

1. At least one of the following is true: [Category 1]

   1. content was not designed to flicker (or flash) in the range of 3 to 49 Hz.

   2. if flicker is unavoidable, the user is warned of the flicker before they go to the page, and as close a version of the content as is possible without flicker is provided.

   Editorial Note:  We would like to include a third criteria here that would state that a test that was conducted and the pages passed. No test or tool exists yet though. We're looking into how such a test and/or tool might be designed.

Single-A Success Criteria for Guideline 3.1

1. passages or fragments of text occurring within the content that are written in a language other than the primary natural language of the content as a whole, are identified, including specification of the language of the passage or fragment.

   Note:

   1. Foreign words or phrases that are found in standard unabridged dictionaries for the natural language of the content do not need to be marked.

   2. This success criterion applies only to foreign words, not to imaginary words, dialect abbreviations and other words that may not be found in an unabridged dictionary of the primary language but that are not foreign words.

   [Category 1]
2. [???] document attributes identify the natural language of the document. [Category 1]

Editorial Note: In techniques discussion, it has been argued that language attributes for documents are as important as identifying changes in language within documents. Moving it up here for future discussion.

Single-A Success Criteria for Guideline 4.1

1. for markup, except where the site has documented that a specification was violated for backward compatibility, the markup has: [Category 1]

   1. passed validity tests of the language (whether it be conforming to a schema, Document Type Definition (DTD), or other tests described in the specification)

   2. structural elements and attributes are used as defined in the specification

   3. accessibility features are used

   4. deprecated features are avoided

   Editorial Note: The following two success criteria seem to overlap with checkpoint 4.3. There is an open question about whether they should be deleted since checkpoint 4.3 covers programmatic interfaces.

Single-A Success Criteria for Guideline 4.2

1. any custom user interface elements of the content conform to at least Level A of the User Agent Accessibility Guidelines 1.0. If the custom user interfaces cannot be made accessible, an alternative solution is provided that meets WCAG 2.0 (including this provision) to the level claimed. [Category 1]

   Editorial Note: This checkpoint includes a slightly reworded version of the suggestions from CKW reorganization. However, the following elements appeared to be redundant with the first sentence. Can they be removed?

   1. If the application renders visual text, it should conform to the VisualText checkpoints.

   2. If the application renders images, it should conform to the Image checkpoints.

   3. If the application renders animations, it should conform to the Animation checkpoints.

   4. If the application renders video, it should conform to the Video checkpoints.

   5. If the application renders audio, it should conform to the Audio checkpoints.

   6. If the application performs its own event handling, it should conform to the Events checkpoints.

   7. If the application implements a selection mechanism, it should conform to the Selection checkpoints.

   8. The application should support keyboard access per UAAG 1.0 checkpoints 1.1 and 6.7.

   9. If the application implements voice or pointer input, it should conform to the Input Modality checkpoints.

   10. accessibility conventions of the markup or programming language (API's or specific markup) are used (@@in UAAG somewhere?)

2. plug-ins required to access the content conform to at least Level A of UAAG 1.0. If required plug-ins are not accessible, an alternative solution is provided that conforms to WCAG 2.0. [Category 1]