The Web Content Accessibility Guidelines 2.0

• Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose.
• Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)
• Tests: If non-text content is a test, exercise or game that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
• Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.
• Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.

• Reversible: Submissions are reversible.
• Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
• Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

• G82: Providing a short text alternative that identifies the purpose of the non-text content

1. G115: Using semantic elements to mark up structure AND H49: Using semantic markup to mark emphasized or special text (HTML)
2. G117: Using text to convey information that is conveyed by variations in presentation of text
3. G140: Separating information and structure from presentation to enable different presentations
4. Making information and relationships conveyed through presentation programmatically determinable using the following techniques:
   • G138: Using semantic markup whenever color cues are used
   • H44: Using label elements to associate text labels with form controls (HTML)
   • H65: Using the title attribute to identify form controls when the label element cannot be used (HTML)
   • H71: Providing a description for groups of form controls using fieldset and legend elements (HTML)
   • H85: Using OPTGROUP to group OPTION elements inside a SELECT (HTML)

• G57: Ordering the content in a meaningful sequence for all the content in the Web page
• Marking sequences in the content as meaningful using one of the following techniques AND G57: Ordering the content in a meaningful sequence for those sequences
• H34: Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) to mix text direction inline (HTML)
• C27: Making the DOM order match the visual order (CSS)

1. G202: Ensuring keyboard control for all functionality
2. Ensuring keyboard control by using one of the following techniques.
   • H91: Using HTML form controls and links (HTML)
3. G90: Providing keyboard-triggered event handlers using one of the following techniques:
   • SCR20: Using both keyboard and other device-specific functions (Scripting)
   • SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons (Scripting)
   • SCR2: Using redundant keyboard and mouse event handlers (Scripting)

1. G59: Placing the interactive elements in an order that follows sequences and relationships within the content
2. Giving focus to elements in an order that follows sequences and relationships within the content using one of the following techniques:
   • H4: Creating a logical tab order through links, form controls, and objects (HTML)
   • C27: Making the DOM order match the visual order (CSS)
3. Changing a Web page dynamically using one of the following techniques:
   • SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element (Scripting)
   • SCR37: Creating Custom Dialogs in a Device Independent Way (Scripting)
   • SCR27: Reordering page sections using the Document Object Model (Scripting)

1. G149: Using user interface components that are highlighted by the user agent when they receive focus
2. C15: Using CSS to change the presentation of a user interface component when it receives focus (CSS)
3. G165: Using the default focus indicator for the platform so that high visibility default focus indicators will carry over
4. G195: Using an author-supplied, highly visible focus indicator
5. SCR31: Using script to change the background color or border of the element with focus (Scripting)

3.2.1

Note: A change of content is not always a change of context. This success criterion is automatically met if changes in content are not also changes of context.

1. G80: Providing a submit button to initiate a change of context using a technology-specific technique listed below
   • H32: Providing submit buttons (HTML)
   • H84: Using a button with a select element to perform an action (HTML)
2. G13: Describing what will happen before a change to a form control that causes a change of context to occur is made
3. SCR19: Using an onchange event on a select element without causing a change of context (Scripting)

Note: A change of content is not always a change of context. This success criterion is automatically met if changes in content are not also changes of context.

G197: Using labels, names, and text alternatives consistently for content that has the same functionality AND following the sufficient techniques for Success Criterion 1.1.1 and sufficient techniques for Success Criterion 4.1.2 for providing labels, names, and text alternatives.

Note 1: Text alternatives that are “consistent” are not always “identical.” For instance, you may have an graphical arrow at the bottom of a Web page that links to the next Web page. The text alternative may say “Go to page 4.” Naturally, it would not be appropriate to repeat this exact text alternative on the next Web page. It would be more appropriate to say “Go to page 5”. Although these text alternatives would not be identical, they would be consistent, and therefore would satisfy this Success Criterion.

Note 2: A single non-text-content-item may be used to serve different functions. In such cases, different text alternatives are necessary and should be used. Examples can be commonly found with the use of icons such as check marks, cross marks, and traffic signs. Their functions can be different depending on the context of the Web page. A check mark icon may function as “approved”, “completed”, or “included”, to name a few, depending on the situation. Using “check mark” as text alternative across all Web pages does not help users understand the function of the icon. Different text alternatives can be used when the same non-text content serves multiple functions.

Situation A: If a form contains fields for which information from the user is mandatory.

1. G83: Providing text descriptions to identify required fields that were not completed
2. SCR18: Providing client-side validation and alert (Scripting)

Situation B: If information provided by the user is required to be in a specific data format or of certain values.

1. G84: Providing a text description when the user provides information that is not in the list of allowed values
2. G85: Providing a text description when user input falls outside the required format or values
3. SCR18: Providing client-side validation and alert (Scripting)
4. SCR32: Providing client-side validation and adding error text via the DOM (Scripting)

1. G131: Providing descriptive labels AND one of the following:
   • G89: Providing expected data format and example
   • G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input
   • G162: Positioning labels to maximize predictability of relationships
   • G83: Providing text descriptions to identify required fields that were not completed
   • H90: Indicating required form controls using label or legend (HTML)
2. H44: Using label elements to associate text labels with form controls (HTML)
3. H71: Providing a description for groups of form controls using fieldset and legend elements (HTML)
4. H65: Using the title attribute to identify form controls when the label element cannot be used (HTML)
5. G167: Using an adjacent button to label the purpose of a field

Note: The techniques at the end of the above list should be considered “last resort” and only used when the other techniques cannot be applied to the page. The earlier techniques are preferred because they increase accessibility to a wider user group.

Situation A: If a mandatory field contains no information:

Situation B: If information for a field is required to be in a specific data format:

1. G85: Providing a text description when user input falls outside the required format or values
2. G177: Providing suggested correction text
3. SCR18: Providing client-side validation and alert (Scripting)
4. SCR32: Providing client-side validation and adding error text via the DOM (Scripting)

Situation C: Information provided by the user is required to be one of a limited set of values:

1. G84: Providing a text description when the user provides information that is not in the list of allowed values
2. G177: Providing suggested correction text
3. SCR18: Providing client-side validation and alert (Scripting)
4. SCR32: Providing client-side validation and adding error text via the DOM (Scripting)

Situation A: If an application causes a legal transaction to occur, such as making a purchase or submitting an income tax return:

1. G164: Providing a stated time within which an online request (or transaction) may be amended or canceled by the user after making the request
2. G98: Providing the ability for the user to review and correct answers before submitting
3. G155: Providing a checkbox in addition to a submit button

Situation B: If an action causes information to be deleted:

1. G99: Providing the ability to recover deleted information
2. G168: Requesting confirmation to continue with selected action
3. G155: Providing a checkbox in addition to a submit button

Situation C: If the Web page includes a testing application:

1. G98: Providing the ability for the user to review and correct answers before submitting
2. G168: Requesting confirmation to continue with selected action