Accessibility Comparisons

Last Updated: 9/15/15

A comparison of the requirements of Section 508, WCAG 1, and WCAG 1 2. This is a work in progress, and shouldn’t be relied upon to be perfect. If you have comments or corrections, please feel free to leave them here. Based on Comparison WCAG and Section 508 Web - http://www.jimthatcher.com/sidebyside.htm

WCAG 1.0 & 2.0 and Section 508 Comparisons
Keywords WCAG 1 WCAG 2 Comparison Section 508

Text Equivalent

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. Guideline 1.1 Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. Similar 1194.22 (a) A text equivalent for every non-text element shall be provided (e.g., via “alt”, “longdesc”, or in element content).
 

The Section 508 standard uses the exact language of WCAG 1.0 Checkpoint 1.1 without “This includes” of WCAG 1.1.

The picture is complicated by the role of such extensions to HTML in WCAG 1.0 compared to that in Section 508. For the former the pages must be usable with scripts and applets turned off or not supported. This makes the importance of the “text equivalent” much greater for WCAG compliance compared with Section 508. For section 508 these extensions must be accessible (see Paragraphs 1194.22 (l) and 1194.22 (m)). Jim Hatcher

WCAG 2.0 Guidline 1.1 clarifies the text equivalent issue over WCAG 1.1 in two ways.

  1. It does not have a list of includes, leaving this guideline open to new technology.
  2. It does include a list of excluded situations, but again leaves the specific technology open for future advances. The exclusions are:
    • Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.)
    • 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.)
    • Test: If non-text content is a test or exercise 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.
    • CAPTCHA: If the purpose non-text content 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 to accommodate different disabilities.
    • 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.

Time-based Media

1.4 For any time-based multi-media presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. Guideline 1.2 Provide alternatives for time-based media.

WCAG 1 and 508 are very similar, WCAG 2 goes into more detail about general purpose, and less detail about specific technology

WCAG 2 also has supporting sub-guidelines listed below, which are, for the most part, not reflected in the other two.

1194.22 (b) Equivalent alternatives for any multi-media presentation shall be synchronized with the presentation.
Audio or Video Only

Generally covered in 1.4 but not specifically mentioned.

1.2.1 Audio-only and Video-only (Prerecorded): 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: (Level A)

  • Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
  • Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
Not in Section 508 or WCAG 1 Generally covered in 1194.22 (b). but not specifically mentioned
Captions Generally covered in 1.4 but not specifically mentioned 1.2.2 Captions (Prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) Not in Section 508 or WCAG 1 Generally covered in 1194.22 (b). but not specifically mentioned.
Auditory description 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. 1.2.3 An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) Not specifically in Section 508. WCAG 2 is more specific than WCAG 1. Generally covered in 1194.22 (b). but not specifically mentioned.
Captions (Live) Generally covered in 1.4 but not specifically mentioned. 1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media. (Level AA) Not specifically covered in Section 508 or WCAG 1. Generally covered in 1194.22 (b). but not specifically mentioned.
Auditory description (prerecorded) 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. 1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. (Level AA) Not specifically covered in Section 508 or WCAG 1. Generally covered in 1194.22 (b). but not specifically mentioned.
Sign Language (prerecorded) Generally covered in 1.4 but not specifically mentioned. 1.2.6 Sign Language (Prerecorded): Sign language interpretation is provided for all prerecorded audio content in synchronized media. (Level AAA) Not specifically covered in Section 508 or WCAG 1. Generally covered in 1194.22 (b). but not specifically mentioned.
Extended Audio Description (prerecorded) Generally covered in 1.4 but not specifically mentioned.

 

1.2.7 Extended Audio Description (Prerecorded): Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media. (Level AAA) Not specifically covered in Section 508 or WCAG 1. Generally covered in 1194.22 (b). but not specifically mentioned.
Auditory description (prerecorded) 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. 1.2.8 Media Alternative (Prerecorded): An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media. (Level AAA) Not specifically covered in Section 508 or WCAG 1. Generally covered in 1194.22 (b). but not specifically mentioned.
Audio Only (Live) Generally covered in 1.4 but not specifically mentioned. 1.2.9 Audio-only (Live): An alternative for time-based media that presents equivalent information for live audio-only content is provided. (Level AAA) Not specifically covered in Section 508 or WCAG 1. Generally covered in 1194.22 (b). but not specifically mentioned.
 

WCAG 2 goes into specific detail as of requirements, while WCAG 1 and Section 508 have more general requirements for “synchronized text equivalents”. WCAG also breaks down into various aspects of both prerecorded and live multimedia, video, and audio and treats each one independently.

Indeed there is a similar provision in the final rule as well. Paragraph 1194.24 (d) of the multi-media section (cited above) requires that training and informational multi-media productions which support the agency’s mission shall have audio descriptions.

Adaptable

Nonexistent Guideline 1.3 Create content that can be presented in different ways (for example simpler layout) without losing information or structure. Not in Section 508 or WCAG 1 Nonexistent
Info and Relationships Nonexistent 1.3.1 Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) Not in Section 508 or WCAG 1 Nonexistent
Meaningful Sequence Nonexistent 1.3.2 When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A) Not in Section 508 or WCAG 1 Nonexistent
Sensory Characteristics Nonexistent 1.3.3 Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A) Not in Section 508 or WCAG 1 Nonexistent
 

The purpose of this guideline is to ensure that all information is available in a form that can be perceived by all users. For example, spoken aloud, or presented in a simpler visual layout . If all of the information is available in a form that can be determined by software, then it can be presented to users in different ways (visually, audibly, tactilely etc.). If information is embedded in a particular presentation in such a way that the structure and information cannot be programmatically determined by the assistive technology, then it cannot be rendered in other formats as needed by the user.

Guideline 1.3.1, while isn’t long or complex, replaces a significant amount of WCAG 1. WCAG 1 focused on the application of specific technology (eg. use of table headers and complex tables.) , while WCAG 2 lists general concepts and leaves the technology up to the developer.

Distinguishable

Nonexistent Guideline 1.4 Make it easier for users to see and hear content including separating foreground from background. Not in Section 508 or WCAG 1 Nonexistent
Color 2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. 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. (Level A) Very similar 1194.22 (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
Audio Control Nonexistent 1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A) Not in Section 508 or WCAG 1 Nonexistent
Minimum Contrast 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. 1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA)

 

  • Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
  • Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
  • Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement
Not in Section 508. WCAG 1 and 2 are similar in intent, but WCAG 2 improves upon WCAG 1 by making identifying a specific testable ratio and by identifying exceptions to the rule. Nonexistent
Resize text Nonexistent 1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA) Not in Section 508 or WCAG 1 Nonexistent
Images of text Nonexistent

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: (Level AA)

  • 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.

Note: Logotypes (text that is part of a logo or brand name) are considered essential.

Not in Section 508 or WCAG 1 Nonexistent
Contrast enhanced 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.

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: (Level AAA)

  • Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1;
  • Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
  • Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.

Not in Section 508. WCAG 1 and 2 are similar in intent.

WCAG 2 Guideline 1.4.3, listed above, improves upon WCAG 1 2.2. WCAG 2 1.4.6 Contrast (Enhanced) takes it a step further, increasing the level of contrasdt required for passing.

Nonexistent
Low or no background audio Nonexistent

1.4.7 Low or No Background Audio: For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: (Level AAA)

  • No Background: The audio does not contain background sounds.
  • Turn Off: The background sounds can be turned off.
  • 20 dB: The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds.Note: Per the definition of “decibel,” background sound that meets this requirement will be approximately four times quieter than the foreground speech content.
Not in Section 508 or WCAG 1 Nonexistent
Visual Presentation Nonexistent

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

  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 can be 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.
Not in Section 508 or WCAG 1 Nonexistent
Images of Text Nonexistent 1.4.9 Images of Text (No Exception): Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. (Level AAA) Note: Logotypes (text that is part of a logo or brand name) are considered essential. Not in Section 508 or WCAG 1 Nonexistent

Keyboard

Guideline 8. Ensure direct accessibility of embedded user interfaces.

Ensure that the user interface follows principles of accessible design: device-independent access to functionality, keyboard operability, self-voicing, etc

Guideline 2.1: Make all functionality available from a keyboard. Section 508 and WCAG 2.0 are more restrictive than WCAG 1. 1194.21 - product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.
keyboard-only access Nonexistent 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. (Level A) Not in Section 508 or WCAG 1 Nonexistent
Keyboard trap Nonexistent 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 or other standard exit methods, the user is advised of the method for moving focus away. (Level A) Not in Section 508 or WCAG 1 Nonexistent
Keyboard (No Exception) Nonexistent 2.1.3 Keyboard (No Exception): All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA) Not in Section 508 or WCAG 1 Nonexistent

Time limits

Nonexistent Guideline 2.2: Provide users enough time to read and use content. Not in WCAG 1. Section 508 and WCAG 2 are similar in intent, though WCAG 2 is significantly more restrictive. 1194.22 (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
Timing Adjustable Nonexistent

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

  • 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.
Not in Section 508 or WCAG 1 Nonexistent
Pause, Stop, Hide Nonexistent

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

  • 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 and (2) 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.
Not in Section 508 or WCAG 1 Nonexistent
No timing Nonexistent 2.2.3 No Timing: Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. (Level AAA) Not in Section 508 or WCAG 1 Nonexistent
Interuptions Nonexistent 2.2.4 Interruptions: Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. (Level AAA) Not in Section 508 or WCAG 1 Nonexistent
Re-authenticating Nonexistent 2.2.5 Re-authenticating: When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. (Level AAA) Not in Section 508 or WCAG 1 Nonexistent

Seizure

7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. Guideline 2.3: Do not design content in a way that is known to cause seizures. WCAG 1 and Section 508 are similar, with Section 508 being more specific. WCAG 2 is more restrictive in that it doesn’t specify cause, but instead specifies negative results. 1194.22 (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
Three flashes, below threshold Nonexistent 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. (Level A) Not in Section 508 or WCAG 1 Nonexistent
Three flashes Nonexistent 2.3.2 Three Flashes: Web pages do not contain anything that flashes more than three times in any one second period. (Level AAA) Not in Section 508 or WCAG 1 Nonexistent

clear navigation

Guideline 13. Provide clear navigation mechanisms.

Provide clear and consistent navigation mechanisms — orientation information, navigation bars, a site map, etc. — to increase the likelihood that a person will find what they are looking for at a site.

Guideline 2.4: Provide ways to help users navigate, find content, and determine where they are. WCAG 1 and WCAG 2 are similar Nonexistent
bypass content blocks Nonexistent 2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)

Not in WCAG 1. Section 508 and WCAG 2 are similar. WCAG is more specific, refering to blocks of content rather than navigation.

(1194.22o) A method shall be provided that permits users to skip repetitive navigation links.

Page title Falls under the general category of Guideline 13. Provide clear navigation mechanisms, but has no specific mention of Page titles 2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A) Not in Section 508 or specifically mentioned in WCAG 1. Nonexistent
Focus order   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. (Level A) Not in Section 508 or WCAG 1 Nonexistent
Link purpose

13.1 Clearly identify the target of each link. [Priority 2]

Link text should be meaningful enough to make sense when read out of context — either on its own or as part of a sequence of links. Link text should also be terse.

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. (Level A) Not in Section 508. WCAG 1 and WCAG 2 are similar. WCAG 2 gives this a higher priority. Nonexistent
Muliple ways Nonexistent 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. (Level AA) Not in Section 508 or WCAG 1 Nonexistent
Headings and labels Nonexistent 2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA) Not in Section 508 or WCAG 1 Nonexistent
Focus visible Nonexistent 2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) Not in Section 508 or WCAG 1 Nonexistent
Location 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). [Priority 2] 2.4.8 Location: Information about the user’s location within a set of Web pages is available. (Level AAA) Not in Section 508. WCAG 1 suggests site information be available in the site, WCAG is more specific and requests location information be available on each page. Nonexistent
Link Purpose (Link Only)

13.1 Clearly identify the target of each link. [Priority 2]

Link text should be meaningful enough to make sense when read out of context — either on its own or as part of a sequence of links. Link text should also be terse.

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. (Level AAA)

Not in Section 508. WCAG 1 and WCAG 2 2.4.4, shown above are similar.

WCAG 2.4.9, shown here, is more specific than either WCAG 1 or WCAG 2.4.4

Nonexistent
Section Headings

3.5 Use header elements to convey document structure and use them according to specification. [Priority 2]

For example, in HTML, use H2 to indicate a subsection of H1. Do not use headers for font effects.

2.4.10 Section Headings: Section headings are used to organize the content. (Level AAA) Not in Section 508. WCAG 1 and WCAG 2 are similar. Nonexistent

Readable and understandable

  Guideline 3.1: Make text content readable and understandable. Not in Section 508 or WCAG 1 Nonexistent
Language of page 4.3 Identify the primary natural language of a document.. [Priority 1] 3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A) Not in Section 508. WCAG 1 and 2 are very similar. Nonexistent
Language of parts 4.1 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. (Level AA) Not in Section 508. WCAG 1 and 2 are similar, with WCAG 2 being more specific. Nonexistent
Unusual words 4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs. [Priority 3] 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. (Level AAA)

Not in Section 508. WCAG 1 and 2 are somewhat similar, with WCAG 2 being more specific.

WCAG 1 is specific to one technology, while WCAG 2 is open to new technology.

Nonexistent
Abbreviations 4.2 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. (Level AAA)

Not in Section 508. WCAG 1 and 2 are somewhat similar, with WCAG 2 being more specific.

WCAG 1 is specific to one technology, while WCAG 2 is open to new technology.

Nonexistent
Reading level 14.1 Use the clearest and simplest language appropriate for a site’s content. [Priority 1] 3.1.5 Reading Level: When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. Level AAA) Not in Section 508. WCAG 1 and 2 are somewhat similar, with WCAG 2 being more specific. Nonexistent
Pronunciation

Guideline 4. Clarify natural language usage.

Use markup that facilitates pronunciation or interpretation of abbreviated or foreign text.

3.1.6 Pronunciation: A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. (Level AAA) Not in Section 508. WCAG 1 and 2 are somewhat similar, with WCAG 2 being more specific. Nonexistent

Predictable

Nonexistent Guideline 3.2: Make Web pages appear and operate in predictable ways. Not in Section 508 or WCAG 1 Nonexistent
On focus Nonexistent 3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A) Not in Section 508 or WCAG 1 Nonexistent
On input Nonexistent 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. (Level A) Not in Section 508 or WCAG 1 Nonexistent
Consistent navigation

13.4 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. (Level AA)

Not in Section 508 WCAG 2 is more specific than WCAG 1. Nonexistent
Consistent identification Nonexistent 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) Not in Section 508 or WCAG 1 Nonexistent
Change on request Nonexistent 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. (Level AAA) Not in Section 508 or WCAG 1 Nonexistent

Correct mistakes

Nonexistent Guideline 3.3: Help users avoid and correct mistakes. Not in Section 508 or WCAG 1 Nonexistent
Error identification Nonexistent 3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) Not in Section 508 or WCAG 1 Nonexistent
Labels or Instructions 12.4 Associate labels explicitly with their controls. [Priority 2] 3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) Not in Section 508. WCAG 2 is more specific than WCAG 1, and more open to advances in techniology. Nonexistent
Error suggestion   3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) Not in Section 508 or WCAG 1 Nonexistent
Error Prevention (Legal, Financial, Data) Nonexistent

3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA)

  1. Reversible: Submissions are reversible.
  2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
  3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Not in Section 508 or WCAG 1 Nonexistent
Help Nonexistent

3.3.5 Help: Context-sensitive help is available. (Level AAA)

Not in Section 508 or WCAG 1 Nonexistent
Error Prevention (All) Nonexistent

3.3.6 Error Prevention (All): For Web pages that require the user to submit information, at least one of the following is true: (Level AAA)

  1. Reversible: Submissions are reversible.
  2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
  3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Not in Section 508 or WCAG 1 Nonexistent
Maximize compatibility Nonexistent Guideline 4.1: Maximize compatibility with current and future user agents, including assistive technologies. Not in Section 508 or WCAG 1 Nonexistent
Parsing 3.2 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. (Level A)

Note:

  • Avoiding deprecated features of W3C technologies (future link)
  • Not displaying content that relies on technologies that are not accessibility-supported when the technology is turned off or not supported
Not in Section 508. WCAG 1 and WCAG 2 are similar, with WCAG 2 being more open to new technology, and being given a higher priority. Nonexistent
Name, Role, Value Nonexistent 4.1.2 Name, Role, Value: For all 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. (Level A) Not in Section 508 or WCAG 1 Nonexistent