Provide a text equivalent for every non-text element.

[Priority 1]

1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (including)

Controls, Input: If it is a control or accepts user input, then it has a name that describes its purpose.

CAPTCHA: If it is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided.

Decoration, Formatting, Invisible: If it is pure decoration, or used only for visual formatting, or if it is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.

A

Many techniques for images (including short and long text alternatives and null alt), video, audio, CAPTCHA, form elements etc.

For example:

G94: Provide short text alternative

H65: With form inputs use title attribute when label element can't be used

G68: Provide descriptive label for live audio only and live video only content

G143: Provide text alternative that describes purpose of CAPTCHA – AND G144: Ensure page has another CAPTCHA for same purpose but using different modality

How to meet 1.1.1 – other techniques

1.2.1 Audio only and Video only: For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:

Prerecorded Audio-only: A text alternative is provided that presents equivalent information for prerecorded audio-only content.

Prerecorded Video-only: Either a text alternative or an audio track is provided that presents equivalent information for prerecorded video-only content.

A

G158: Providing a transcript for prerecorded audio only

G159: Providing a transcript for prerecorded video only

1.2.9 Live audio-only: A text alternative that presents equivalent information for live audio-only content is provided.

AAA

G151: Providing a link to a text transcript of a prepared statement or script if the script is followed

G150: Providing text alternatives for live audio-only content

G157: Incorporating a live audio captioning service into a Web page

Provide redundant text links for each active region of a server-side image map.

[Priority 1]

1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose. (see above)

A

NB: No direct equivalent for providing redundant text links for regions of server-side maps.

H24: Providing text alternatives for the area elements of image maps

SEE ALSO

2.4.4 Link Purpose (in context): The purpose of each link can be determined from the link text alone, or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

AAA

H24: Providing text alternatives for the area elements of image maps

SEE ALSO

2.1.1 (Keyboard): All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

A

NB: Server-side maps are not keyboard accessible

Until user agents can automatically read aloud the text equivalent of a visual track, provide an audio description of the important visual information of a multimedia presentation.

[Priority 1]

1.2.5 Audio Description: Audio description is provided for all prerecorded video content in synchronized media.

AA

G78: Providing a sound track that includes audio description

G78: USING SM6: SMIL 1.0

1.2.7 Audio Description (extended): Extended audio description is provided for all prerecorded video content in synchronized media.

AAA

G8: Providing an extended audio description for synchronized media content

G8: USING SM1: Extended audio in SMIL 1.0

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]

1.2.2 Captions (prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when media is a media alternative for text and is clearly labeled as such.

A

G93: Providing open (always visible) captions

G87: Providing closed captions USING available media format that has a video player that supports closed captioning

G87: Provide closed captions USING SM11: Synchronised text stream in SMIL 1.0

1.2.3 Audio description of full text alternative: A full text alternative for synchronized media including any interaction or audio description of the prerecorded video content is provided for synchronized media, except when media is a media alternative for text and is clearly labeled as such.

A

G69: Providing a full synchronized media text alternative including any interaction

G78: Providing a sound track that includes audio description

1.2.4 Captions (live): Captions are provided for all live audio content in synchronized media.

AA

G9: Creating captions for live synchronised media AND G93: Providing open (always visible) captions

How to meet 1.2.4 – other techniques

1.2.5 Audio Description: Audio description is provided for all prerecorded video content in synchronized media.

AA

G78: Providing a sound track that includes audio description

How to meet 1.2.5 – other techniques

1.2.7 Audio description (extended): Extended audio description is provided for all prerecorded video content in synchronized media.

AAA

G8: Providing an extended audio description for synchronized media content USING SM1: Extended audio in SMIL 1.0

1.2.8 Full Text Alternative: A full text alternative for synchronized media including any interaction is provided for all prerecorded synchronized media and a text alternative that presents equivalent information is provided for all prerecorded video-only media.

AAA

G69: Providing a full synchronized media text alternative including any interaction

G159: Providing a transcript for prerecorded video only

How to meet 1.2.8 – other techniques

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]

NO MATCHING WCAG 2.0 S.C.

NB: No WCAG 2.0 equivalent since user agents now render the text equivalents

Ensure that all information conveyed with colour is also available without colour, for example from context or markup.

[Priority 1]

1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

A

G14: Ensuring that information conveyed by colour differences is also available in text

G122: Including a text cue whenever colour cues are used

For colour within images

G111: Using colour and pattern

Ensure that foreground and background colour combinations provide sufficient contrast for viewing by someone having colour deficits.

[Priority 2 for images Priority 3 for text]

1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 5:1, except for the following:

Large print

Incidental text or images

Logotypes

AA

G18: Ensuring that a contrast ratio of at least 5:1 exists between text (and images of text) and background behind the text

Text more than 18 pt (14 pt if bold)

G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text

How to meet 1.4.3 – other techniques

1.4.6 Contrast (Enhanced): The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following:

Large print

Incidental text or images

Logotypes

AAA

Text less than 18 pt (14 pt if bold)

G17: Ensuring that a contrast ratio of at least 7:1 exists between text (and images of text) and background behind the text

Text more than 18 pt (14 pt if bold)

G18: Ensuring that a contrast ratio of at least 5:1 exists between text (and images of text) and background behind the text

GUIDELINE 3: Use markup and style sheets and do so properly.

When an appropriate markup language exists, use markup rather than images to convey information.

[Priority 2]

1.4.5 Images of text: If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following:

Customizable: The image of text can be visually customized to the user's requirements;

Essential: A particular presentation of text is essential to the information being conveyed.

AA

NB No direct WCAG 2 equivalent, but see S.C. 1.3.1 for mark-up requirements and techniques

G140: Separating information and structure from presentation so that Web pages can be presented different ways without losing information

1.4.9 Images of Text (Essential): Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.

AAA

G140: Separating information and structure from presentation so that Web pages can be presented different ways without losing information

Create documents that validate to published formal grammars.

[Priority 2]

4.1.1 Parsing: In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

A

NB: No a direct equivalent since validation is a more rigid requirement

G134: Validating Web pages

G154: Using HTML according to spec

How to meet 4.1.1 – other techniques

Use style sheets to control layout and presentation.

[Priority 2]

1.3.1 Info and relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

G140:Separating information and structure from presentation to enable different presentations.

NB: Not a direct equivalent.

Use relative rather than absolute units in markup language attribute values and style sheet property values.

[Priority2]

1.4.8 Visual Presentation: For the visual presentation of blocks of text, a mechanism is available to achieve the following: (See Point 5)

1. foreground and background colors can be selected by the user
2. width is no more than 80 characters or glyphs (40 if CJK)
3. text is not justified (aligned to both the left and the right margins)
4. line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing
5. text is resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window

AAA

G146: Using liquid layout AND using measurements that are relative to other measurements in the content by using one or more of the following:

• C12: Using percent for font sizes (CSS)
• C13: Using named font sizes (CSS)
• C14: Using em units for font sizes (CSS)

1.4.4 Resize text: Text (but not images of text) can be resized without assistive technology up to 200 percent without loss of content or functionality.

AA

G142: Using a technology that has commonly-available user agents that support zoom.

Techniques for relative measurements

• C12: Using percent for font sizes (CSS)
• C13: Using named font sizes (CSS)
• C14: Using em units for font sizes (CSS)

G146: Using liquid layout (Technique for text container resizing)

How to meet 1.4.4 – other techniques

Use header elements (eg h1 and h2) to convey document structure and use them according to specification.

[Priority 2]

1.3.1 Info and relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

A

H42: Using h1-h6 to identify headings

Markup lists and list items properly.

[Priority 2]

1.3.1 Info and relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

A

H48: Using ol, ul and dl for lists

Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

[Priority 2]

1.3.1 Info and relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

A

G115: Using semantic elements to markup structure AND H49: Using semantic markup to mark emphasized or special text

GUIDELINE 4:Clarify natural language use.

Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).

[Priority 1]

3.1.2 Language of parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

AA

H58: Using language attributes to identify changes in the human language

Specify the expansion of each abbreviation or acronym in a document where it first occurs.

[Priority 3]

3.1.4 Abbreviations: A mechanism for identifying the expanded form or meaning of abbreviations is available.

AAA

Variety of techniques including linking to a definition or glossary.

How to meet 3.1.4 – many techniques

3.1.3 Unusual words: A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.

AAA

How to meet 3.1.3 – many techniques

Identify the primary natural language of a document.

[Priority 3]

3.1.1 Language of page: The default human language of each Web page can be programmatically determined.

A

H57: Using language attributes on the html element

GUIDELINE 5: Create tables that transform gracefully.

For data tables, identify row and column headers.

[Priority 1]

1.3.1 Info and relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

A

H51: Using table markup to present tabular information

H63: Using the scope attribute to associate header cells and data cells in data tables

H43: Using id and headers attributes to associate data cells with header cells in data tables

For data tables with two or more logical levels of row or column headers, use markup to associate data cells and header cells.

[Priority 1]

1.3.1 Info and relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

A

NB: WCAG 2.0 makes no distinction between simple and complex data tables.

See above for data table techniques

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]

1.3.2 Meaningful sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

NB: Not direct WCAG 2.0 equivalent

A

NB: No direct WCAG 2.0 equivalent, but 1.3.2 addresses sequence of content

G57: Ordering the content in a meaningful sequence

How to meet 1.3.2

If a table is used for layout, do not use any structural markup for the purpose of visual formatting.

[Priority 2]

1.3.1 Info and relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

A

NB: No clear equivalent techniques but failures indicated

F46: Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables

Provide summaries for tables.

[Priority 3]

1.3.1 Info and relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

A

H73: Using the summary attribute of the table element to give an overview of data tables.

Also consider H39: Using caption elements

Provide abbreviations for header labels.

[Priority 3]

NO MATCHING WCAG 2.0 S.C.

NB: No WCAG 2.0 equivalent

GUIDELINE 6: Ensure that pages featuring new technologies transform gracefully.

Organize documents so they may be read without style sheets. Eg, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.

[Priority 1]

NO MATCHING WCAG 2.0 S.C.

NB: No WCAG 2.0 equivalent

Ensure that equivalents for dynamic content are updated when the dynamic content changes.

[Priority 1]

NO MATCHING SUCCESS CRITERIA

Issue is addressed as part of "Conformance requirements".

Conformance requirement 1: Allows non-conforming pages to be included so long as they have a "conforming alternate version" that:

1. conforms at the designated level, and
2. provides all of the same information and functionality in the same human language, and
3. is as up to date as the non-conforming content, and
4. for which at least one of the following is true:

a. the conforming version can be reached from the non-conforming page via an accessibility supported mechanism, or

b. the non-conforming version can only be reached from the conforming version, or

c. the non-conforming version can only be reached from a conforming page that also provides a mechanism to reach the conforming version

Ensure that pages are usable when scripts, applets etc are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.

[Priority 1]

NO MATCHING WCAG 2.0 S.C.

Issue is addressed as part of "Conformance requirements".

NB: WCAG 2.0 does not require alternative to be always provided for JavaScript etc. But nominated "accessibility supported technologies" must be used in a way that is accessible.

Conformance requirement 4: Only accessibility supported technologies are relied on to satisfy the success criteria. AND

Conformance requirement 5: If technologies that are not accessibility supported are used, they do not stop users accessing the rest of the page.

For scripts and applets, ensure that event handlers are input device-independent.

[Priority 2]

2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

A

G90: Providing keyboard-triggered event handlers using one of the following techniques.

How to meet 2.1.1 – more techniques to come

2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys, the user is advised of the method for moving focus away.

A

G21: Ensuring that users are not trapped in content

2.1.3 Keyboard (No Exception): All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

AAA

NB: See techniques for Success Criteria 2.1.1

Ensure that dynamic content is accessible or provide an alternative presentation or page.

[Priority 2]

NO MATCHING WCAG 2.0 S.C.

Issue is covered by Conformance requirements.

Conformance requirement 1: Allows non-conforming pages to be included so long as they have a "conforming alternate version" (see note for Checkpoint 6.2)

GUIDELINE 7: Ensure user control of time-sensitive content changes.

Until user agents allow users to control flickering, avoid causing the screen to flicker.

[Priority 1]

2.3.1 Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

A

Using all possible 341 x 256 pixel rectangles on 1024 x 768 pixel display to represent a 10 degree field of view at normal viewing distance AND G15: Ensuring that content does not violate the general flash threshold or red flash threshold

G19: Ensuring that no component of the content flashes more than three times in any 1-second period

(NB: See also SC 2.2.2: Pause, Stop Hide)

2.3.2 Three Flashes: Web pages do not contain anything that flashes more than three times in any one second period.

AAA

G19: Ensuring that no component of the content flashes more than three times in any 1-second period

Until user agents allow users to control blinking, avoid causing content to blink.

[Priority 2]

2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true:

Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and

Auto-updating: For any auto-updating information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

G4: Allowing the content to be paused and restarted from where it was stopped

G11: Creating content that blinks for less than 3 seconds

How to meet 2.2.2 – more techniques to come

Until user agents allow users to freeze moving content, avoid movement in pages.

[Priority 2]

2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information

- see above.

A

G4: Allowing the content to be paused and restarted from where it was stopped

Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.

[Priority 2]

2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true:

Turn off: The user is allowed to turn off the time limit before encountering it; or

Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or

Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or

Real-time Exception: the time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or

Essential Exception: The time limit is essential and extending it would invalidate the activity; or

20 Hour Exception: The time limit is longer than 20 hours.

NB: Not direct WCAG 2.0 equivalent

A

G133: Providing a checkbox on the first page of a multipart form that allows users to ask for longer session time limit or no session time limit

SCR16: Providing a script that warns the user a time limit is about to expire AND SCR1: Allowing the user to extend the default time limit.

G4: Allowing the content to be paused and restarted from where it was stopped

How to meet 2.2.1 – other techniques

2.2.4 Interruptions: Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.

AAA

G75: Providing a mechanism to postpone any updating of content

SCR14: Using scripts to make nonessential alerts optional (Scripting)

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]

2.2.1 Timing Adjustable: For each time limit that is set by the content,-

See above

A

How to meet 2.2.1 – - techniques

2.2.4 Interruptions: Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.

AAA

G75: Providing a mechanism to postpone any updating of content

SCR14: Using scripts to make nonessential alerts optional (Scripting)

3.2.5 Change of request: Changes of context are initiated only by user request or a mechanism is available to turn off such changes.

AAA

SVR1: Implementing automatic redirects on the server side instead of on the client side

G110: Using an instant client-side redirect

GUIDELINE 8: Ensure direct accessibility of embedded user interfaces.

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]

4.1.2 Name, Role, Value: For all user user-interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.

A

G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes.

SCR21: Using functions of the Document Object Model (DOM) to add content to a page

G135: Using the accessibility API features of a technology to expose names and roles, to allow user-settable properties to be directly set, and to provide notification of changes

How to meet 4.1.2 – variety of techniques

2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

A

G90: Providing keyboard-triggered event handlers using one of the following techniques.

SCR20: Using both keyboard and other device-specific functions

How to meet 2.1.1 – more techniques to come

GUIDELINE 9: Design for device-independence

Provide client-side image maps instead of server-side image maps except where the regions cannot be defined available shapes.

[Priority 1]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent but see SC 1.1.1 (non-text content) and SC 2.4.4 (link Purpose).

H24: Providing text alternatives for the area elements of image maps

Ensure that any element that has its own interface can be operated in a device-independent manner.

[Priority 2]

2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

A

G90: Providing keyboard-triggered event handlers using one of the following techniques.

SCR20: Using both keyboard and other device-specific functions

How to meet 2.1.1 – more techniques to come

2.1.3 Keyboard (No Exception): All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

AAA

NB: No additional techniques see 2.1.1

How to meet 2.1.1

For scripts, specify logical event handlers rather than device-dependent event handlers.

[Priority 2]

See above (2.1.1 and 2.1.3)

NB: No direct equivalent in WCAG 2.0

See How to meet 2.1.1

Create a logical tab order through links, form controls, and objects.

[Priority 3]

2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

A

G59: Placing the interactive elements in an order that follows sequences and relationships within the content

H4: Creating a logical tab order through links, form controls, and objects

SCR26: SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element (Scripting)

Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.

[Priority 3]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent in WCAG 2.0, but advisory technique in 2.4.1(Bypass Blocks)

How to meet 2.4.1

GUIDELINE 10: Use interim solutions.

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]

3.2.5 Change on request: Changes of context are initiated only by user request or a mechanism is available to turn off such changes.

AAA

G76: Providing a mechanism to request an update of the content instead of updating automatically

SCR19: Using an onchange event on a select element without causing a change of context (Scripting)

How to meet 3.2.5 - variety of techniques including use of auto redirects and popups

3.2.1 On Focus: When any component receives focus, it does not initiate a change of context.

A

G107: Using "activate" rather than "focus" as a trigger for changes of context

3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

A

G80: Providing a submit button to initiate a change of context using a technology-specific technique.

G13: Describing what will happen before a change to a form control is made

G147: Providing instruction about change of context due to change of input setting ahead of such encounter

How to meet 3.2.2 - other proposed techniques

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]

NO MATCHING WCAG 2.0 S.C.

No direct equivalent in WCAG 2.0, but see SC 3.3.2 technique for positioning labels to maximize predictability of relationships.

NB: See SC 1.3.1, technique:

H44: Using label elements to associate text labels with form controls

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]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent in WCAG 2.0, but see:
SC 1.3.1: Info and Relationships, and
SC 1.3.2: Meaningful Sequence.

Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.

[Priority 3]

NO MATCHING WCAG 2.0 S.C.

NB: No longer recommended

Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.

[Priority 3]

NO MATCHING WCAG 2.0 S.C.

NB: No longer recommended

GUIDELINE 11: Use W3C technologies and guidelines.

Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.

[Priority 2]

NO MATCHING WCAG 2.0 S.C.

NB: No longer recommended

Avoid deprecated features of W3C technologies.

[Priority 2]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent in WCAG 2.0

Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)

[Priority 3]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent in WCAG 2.0.

If you cannot create an accessible page, provide a link to an alternative page that is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible page.

[Priority 1]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent in WCAG 2.0. The assumption is that it will be possible to make pages that are accessible with the nominated "accessibility supported" technologies

Conformance Requirement 1 allows non-conforming pages to be included if they have a "conforming alternate version".

GUIDELINE 12: Provide context and orientation information.

Title each frame to facilitate frame identification and navigation.

[Priority 1]

2.4.2 Page titled: Web pages have titles that describe topic or purpose.

A

Advisory technique - Providing a meaningful name for identifying frames.

How to meet 2.4.2

2.4.1 Bypass blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

A

H70: Using frame elements to group blocks of repeated material (HTML) AND H64: Using the title attribute of the frame and iframe elements

4.1.2 Name, Role, Value: For all user user-interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.

A

G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes USING

H64: Using the title attribute of the frame and iframe elements (HTML)

Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.

[Priority 2]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent in WCAG 2.0, but see comments above

Divide large blocks of information into more manageable groups where natural and appropriate.

[Priority 2]

1.3.1 Info and relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

A

H71: Providing a description for groups of form controls using fieldset and legend elements

H82: Grouping form controls with FIELDSET and LEGEND

H85: Using OPTGROUP to group OPTION elements inside a SELECT

2.4.1 Bypass blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

A

NB: Not a direct equivalent for 12.3, but see

2.4.1 technique 2: Grouping blocks of repeated material in a way that can be skipped, USING one of the following techniques (including):

H69: Providing heading elements at the beginning of each section of content

H50: Using structural elements to group links

Associate labels explicitly with their controls.

[Priority 2]

1.3.1 Info and relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

A

H44: Using label elements to associate text labels with form controls

H65: Using the title attribute to identify form controls when the label element cannot be used

GUIDELINE 13: Provide clear navigation mechanisms.

Clearly identify the target of each link.

[Priority 2]

2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone, or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

A

Many suggested techniques including

G91: Providing link text that describes the purpose of a link

G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentence

How to meet 2.4.4 – variety of other techniques

2.4.9 Link Purpose (Link Only): A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.

AAA

G91: Providing link text that describes the purpose of a link

Providing a supplemental description of the purpose of a link USING

C7: Using CSS to hide a portion of the link text

Provide metadata to add semantic information to pages & sites.

[Priority 2]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent in WCAG 2.0 as no longer required for conformance.

Provide information about the general layout of a site (e.g., a site map or table of contents).

[Priority 2]

2.4.5 Multiple ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.

AA

USING two or more for the following techniques

G125: Providing links to navigate to related Web pages

G64: Providing a Table of Contents

G63: Providing a site map

G126: Providing a list of links to all other Web pages

Use navigation mechanisms in a consistent manner.

[Priority 2]

3.2.3 Consistent navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

AA

G61: Presenting repeated components in the same relative order each time they appear

3.2.4 Consistent identification: Components that have the same functionality within a set of Web pages are identified consistently.

AA

NB: No techniques directly associated to navigation

Provide navigation bars to highlight and give access to the navigation mechanism.

[Priority 3]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent in WCAG 2.0 but see:

How to meet 3.2.3 - Consistent navigation (AA)

How to meet 3.2.4 - Consistent identification (AA)

Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.

[Priority 3]

2.4.1 Bypass blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

A

Creating links to skip blocks of repeated material USING one of:

G1: Adding a link at the top of each page that goes directly to the main content area

G123: Adding a link at the beginning of a block of repeated content to go to the end of the block

G124: Adding links at the top of the page to each area of the content

Grouping blocks of repeated material in a way that can be skipped, USING one of:

H69: Providing heading elements at the beginning of each section of content

H50: Using structural elements to group links

H70: Using frame elements to group blocks of repeated material AND H64: Using the title attribute of the frame and iframe elements

If search functions are provided, enable different types of searches for different skill levels and preferences.

[Priority 3]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent in WCAG 2.0

Place distinguishing information at the beginning of headings, paragraphs, lists, etc.

[Priority 3]

2.4.6 Headings and Labels: Headings and labels describe topic or purpose.

NB:Not a direct equivalent

AA

G130: Providing descriptive headings

G131: Providing descriptive labels

Provide information about document collections (i.e., documents comprising multiple pages.).

[Priority 3]

NO MATCHING WCAG 2.0 S.C.

NB: Not required as no direct equivalent in WCAG 2.0. But see SC2.4.8 (Location)

How to meet 2.4.8

Provide a means to skip over multi-line ASCII art.

[Priority 3]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent in WCAG 2.0

Part of SC 1.1.1 (Non-text content)

GUIDELINE 14: Ensure documents and clear and simple.

Use the clearest and simplest language appropriate for a site's content.

[Priority 1]

NO MATCHING WCAG 2.0 S.C.

NB: No direct equivalent, but see

Guideline 1.3 Adaptable

Guideline 2.2 Enough Time

Guideline 3.1 Readable

Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.

[Priority 3]

No matching WCAG 2.0 S.C. but consider:

3.1.5 Reading Level: When text requires reading ability more advanced than the lower secondary education level, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.

AAA

NB: No direct equivalent in WCAG 2.0, but see SC 3.1.5 Reading level techniques:

G86: Providing a text summary that requires reading ability less advanced than the upper secondary education level

G103: Providing visual illustrations, pictures, and symbols to help explain ideas, events, and processes

G79: Providing a spoken version of the text

Create a style of presentation that is consistent across pages.

[Priority 3]

3.2.3 Consistent navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

AA

G61: Presenting repeated components in the same relative order each time they appear

3.2.4 Consistent identification: Components that have the same functionality within a set of Web pages are identified consistently.

AA

NB: Not a direct equivalent but see

H44: Using label elements to associate text labels with form controls

H65: Using the title attribute to identify form controls when the label element cannot be used

Guideline 1.2 Time-based Media: Provide alternatives for time-based media

AAA

G54: Including a sign language interpreter in the video stream

G81: Providing a synchronized video of the sign language interpreter that can be displayed in a different viewport or overlaid on the image by the player using one of:

SM13: Providing sign language interpretation through synchronized video streams in SMIL 1.0

SM14: Providing sign language interpretation through synchronized video streams in SMIL 2.0

Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout ) without losing information or structure

A

G57: Ordering the content in a meaningful sequence for all the content in the Web page

Marking sequences in the content as meaningful using G57: AND one of the following techniques for those sequences

H34: Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) to mix text direction inline (HTML)

H56: Using the dir attribute on an inline element to resolve problems with nested directional runs (HTML)

C6: Positioning content based on structural markup (CSS)

C8: Using CSS letter-spacing to control spacing within a word (CSS)

A

G96: Providing textual identification of items that otherwise rely only on sensory information to be understood

Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background

A

G60: Playing a sound that turns off automatically within three seconds

AAA

G56: Mixing audio files so that non-speech sounds are at least 20 decibels lower than the speech audio content

AAA

Variety of sufficient and advisory techniques

See How to meet 1.4.8

Guideline 2.2 Enough time: Provide users with disabilities enough time to read and use content

A

If session time limits

G133: Providing a checkbox on the first page of a multipart form that allows users to ask for longer session time limit or no session time limit

If time limit is controlled by script on the page

SCR16: Providing a script that warns the user a time limit is about to expire AND SCR1: Allowing the user to extend the default time limit.

If there are time limits on reading

G4: Allowing the content to be paused and restarted from where it was stopped

How to meet 2.2.1 – other proposed techniques

AAA

G5: Allowing users to complete an activity without any time limit

AAA

G75: Providing a mechanism to postpone any updating of content

SCR14: Using scripts to make nonessential alerts optional

AAA

Providing options to continue without loss of data using one of the following techniques:

G105: Saving data so that it can be used after a user re-authenticates

Guideline 2.4 Navigable: Provide ways to help users navigate, find content and determine where they are.

AA

G149: Using user interface components that are highlighted by the user agent when they receive focus

C15: Using CSS to change the presentation of a user interface component when it receives focus (CSS)

AAA

G65: Providing a breadcrumb trail

G63: Providing a site map

G128: Indicating current location within navigation bars

G127: Identifying a Web page's relationship to a larger collection of Web pages USING H59: Using the link element and navigation tools

AAA

G141; Organizing a page using headings

Guideline 3.1 Readable: Make text content readable and understandable

AAA

G86: Providing a text summary that requires reading ability less advanced than the upper secondary education level

G103: Providing visual illustrations, pictures, and symbols to help explain ideas, events, and processes

G79: Providing a spoken version of the text

G153: Making the text easier to read

AAA

G120: Providing the pronunciation immediately following the word

G121: Linking to pronunciations

G62: Providing a glossary that includes pronunciation information for words that have a unique pronunciation in the content and have meaning that depends on pronunciation

Providing pronunciation information USING a technology-specific technique below

H62: Using the ruby element (HTML) (XHTML 1.1)

Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways

A

G107: Using "activate" rather than "focus" as a trigger for changes of context

A

G80: Providing a submit button to initiate a change of context using a technology-specific technique listed below

G13: Describing what will happen before a change to a form control is made

H32: Providing submit buttons (HTML)

H84: Using a button with a select element to perform an action (HTML)

G147: Providing instruction about change of context due to change of input setting ahead of such encounter

How to meet 3.2.2 - other proposed techniques

Guideline 3.3 Input Assistance: Help users avoid and correct mistakes

A

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

G83: Providing text descriptions to identify required fields that were not completed

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.

G85: Providing a text description when user input falls outside the required format or values

SCR18: Providing client-side validation and alert (Scripting)

A

G131: Providing descriptive labels AND one of the following:

G89: Providing expected data format and example

G83: Providing text descriptions to identify required fields that were not completed

H44:Using label elements to associate text labels with form controls

H71: Providing a description for groups of form controls using fieldset and legend elements

H65:Using the title attribute to identify form controls when the label element cannot be used

How to meet 3.3.2 - other proposed techniques

AA

Situation A: If a mandatory field contains no information:

G83: Providing text descriptions to identify required fields that were not completed

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

G85: Providing a text description when user input falls outside the required format or values

SCR18: Providing client-side validation and alert (Scripting)

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

G84: Providing a text description when the user provides information that is not in the list of allowed values

SCR18: Providing client-side validation and alert (Scripting)

How to meet 3.3.3 - other proposed techniques

AA

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