The Web Content Accessibility Guidelines 2.0

WCAG 2.0 Accessibility Guidelines

The Web Content Accessibility Guidelines relevant to the accessibility of page titles, text content, headings and link text are:-

Page Title

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

Text content

Guideline	Description
1.3	Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.4	Distinguishable: Make it easier for users to see and hear content including separating foreground from background.
2.1	Keyboard Accessible: Make all functionality available from a keyboard.
3.1	Readable: Make text content readable and understandable.
3.2	Predictable: Make Web pages appear and operate in predictable ways.

Headings

Guideline	Description
1.3	Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
2.4	Navigable: Provide ways to help users navigate, find content, and determine where they are.

Link text

Guideline	Description
1.1	Text Alternatives: 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.
1.3	Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.4	Distinguishable: Make it easier for users to see and hear content including separating foreground from background.
2.1	Keyboard Accessible: Make all functionality available from a keyboard.
2.4	Navigable: Provide ways to help users navigate, find content, and determine where they are.
3.1	Readable: Make text content readable and understandable.
3.2	Predictable: Make Web pages appear and operate in predictable ways.

WCAG 2.0 Success Criteria

The Web Content Accessibility Guidelines Success Criterion relevant to the accessibility of page titles, text content, headings and link text are:-

Page Title

SC	Description
2.4.2	Page Titled: Web pages have titles that describe topic or purpose.(Level A)

Text content

SC	Description
1.3.1	Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
1.3.2	Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A)
1.3.3	Sensory Characteristics: 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)
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)
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.
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)
3.1.1	Language of Page: The default human language of each Web page can be programmatically determined. (Level A)
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)
3.2.4	Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)

Headings

SC	Description
1.3.1	Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
2.4.6	Headings and Labels: Headings and labels describe topic or purpose. (Level AA)

Link text

SC	Description
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. (Level A) 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.) 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. 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 byassistive technology.
1.3.1	Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
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.
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)
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)
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)
2.4.7	Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
3.1.1	Language of Page: The default human language of each Web page can be programmatically determined. (Level A)
3.2.4	Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)

WCAG 2.0 Sufficient Techniques

For each of the guidelines and success criteria in WCAG 2.0 there are a wide variety of techniques. The techniques fall into two categories:

Sufficient techniques: techniques or a combination of techniques that are sufficient for meeting the success criteria.

Advisory techniques: techniques that should be considered (where relevant) to make content more accessible. The advisory techniques go beyond what is required by the individual success criteria and are not covered by these factsheets.

Page title

SC	Description
2.4.2	G88: Providing descriptive titles for Web pages AND associating a title with a Web page using the following technique: H25: Providing a title using the title element (HTML)

Text content

SC	Description
1.3.1	G115: Using semantic elements to mark up structure AND [H49: Using semantic markup to mark emphasized or special text] (HTML)G117: Using text to convey information that is conveyed by variations in presentation of text G140: Separating information and structure from presentation to enable different presentationsMaking information and relationships conveyed through presentation programmatically determinable using the following techniques: G138: Using semantic markup whenever color cues are used H48: Using ol, ul and dl for lists or groups of links (HTML) G117: Using text to convey information that is conveyed by variations in presentation of textMaking information and relationships conveyed through presentation programmatically determinable or available in text using the following techniques: T1: Using standard text formatting conventions for paragraphs (Text) T2: Using standard text formatting conventions for lists (Text) T3: Using standard text formatting conventions for headings (Text)
1.3.2	G57: Ordering the content in a meaningful sequence for all the content in the Web pageMarking 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) 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) C27: Making the DOM order match the visual order (CSS)
1.3.3	G96: Providing textual identification of items that otherwise rely only on sensory information to be understood
1.4.1	Situation A: If the color of particular words, backgrounds, or other content is used to indicate information: G14: Ensuring that information conveyed by color differences is also available in text H92: Including a text cue for colored form control labels (HTML) G182: Ensuring that additional visual cues are available when text color differences are used to convey information G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them Situation B: If color is used within an image to convey information: G111: Using color and pattern G14: Ensuring that information conveyed by color differences is also available in text
1.4.5	C22: Using CSS to control visual presentation of text (CSS)C30: Using CSS to replace text with images of text and providing user interface controls to switch (CSS)G140: Separating information and structure from presentation to enable different presentations
2.1.1	G202: Ensuring keyboard control for all functionality
3.1.1	H57: Using language attributes on the html element (HTML)
3.1.2	H58: Using language attributes to identify changes in the human language (HTML)
3.2.4	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.

Headings

SC	Description
1.3.1	G115: Using semantic elements to mark up structureMaking information and relationships conveyed through presentation programmatically determinable by using the following technique: H42: Using h1-h6 to identify headings (HTML)
2.4.6	G130: Providing descriptive headings G131: Providing descriptive labelsNote: Headings and labels must be programmatically determined, per Success Criterion 1.3.1.

Link text

SC	Description
1.1.1	H67: Using null alt text and no title attribute on img elements for images that AT should ignore (HTML)H2: Combining adjacent image and text links for the same resource (HTML)H86: Providing text alternatives for ASCII art, emoticons, and leetspeak (HTML)H30: Providing link text that describes the purpose of a link for anchor elements (HTML)Note: See Understanding Success Criterion 2.4.4 Link Purpose (In Context).G196: Using a text alternative on one item within a group of images that describes all items in the group
1.3.1	G115: Using semantic elements to mark up structure AND H49: Using semantic markup to mark emphasized or special text (HTML)G117: Using text to convey information that is conveyed by variations in presentation of text G140: Separating information and structure from presentation to enable different presentationsMaking information and relationships conveyed through presentation programmatically determinable using the following techniques: H48: Using ol, ul and dl for lists or groups of links (HTML)
1.4.3	Situation A: text is less than 18 point if not bold and less than 14 point if boldG18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text G148: Not specifying background color, not specifying text color, and not using technology features that change those defaultsSituation B: text is at least 18 point if not bold and at least 14 point if boldG145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults
2.1.1	G202: Ensuring keyboard control for all functionalityEnsuring keyboard control by using one of the following techniques: H91: Using HTML form controls and links (HTML) 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)
2.4.4	G91: Providing link text that describes the purpose of a link H30: Providing link text that describes the purpose of a link for anchor elements (HTML)G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentenceProviding a supplemental description of the purpose of a link using one of the following techniques: H33: Supplementing link text with the title attribute (HTML) C7: Using CSS to hide a portion of the link text (CSS) Identifying the purpose of a link using link text combined with programmatically determined link context using one of the following techniques: H77: Identifying the purpose of a link using link text combined with its enclosing list item (HTML) H78: Identifying the purpose of a link using link text combined with its enclosing paragraph (HTML) H79: Identifying the purpose of a link using link text combined with its enclosing table cell and associated table headings (HTML) H80: Identifying the purpose of a link using link text combined with the preceding heading element (HTML) H81: Identifying the purpose of a link in a nested list using link text combined with the parent list item under which the list is nested (HTML) G91: Providing link text that describes the purpose of a link
2.4.5	G125: Providing links to navigate to related Web pages G63: Providing a site map G126: Providing a list of links to all other Web pages G185: Linking to all of the pages on the site from the home page
2.4.7	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)G165: Using the default focus indicator for the platform so that high visibility default focus indicators will carry over G195: Using an author-supplied, highly visible focus indicator SCR31: Using script to change the background color or border of the element with focus (Scripting)
3.1.1	H57: Using language attributes on the html element (HTML)
3.2.4	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.

WCAG 2.0 Common Failures

The following are common mistakes that are considered failures of each Success Criterion by the WCAG Working Group.

Page Title

SC 2.4.2 Page Titled

Failure	Description
F25	Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents.

Text content

SC 1.3.1 Info and Relationships

Failure	Description
F2	Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text.
F17	Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML.
F43	Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content.
F87	Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the ‘content’ property in CSS.

SC 1.3.2 Meaningful sequence

Failure	Description
F33	Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content.
F32	Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word.
F1	Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS.

SC 1.3.3 Sensory Characteristics

Failure	Description
F14	Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location.
F26	Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information.

SC 1.4.1 Use of Color

Failure	Description
F13	Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alternative that does not include information that is conveyed by color differences in the image.
F73	Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision.

SC 2.1.1 Keyboard

Failure	Description
F54	Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function.

SC 3.2.4 Consistent Navigation

Failure	Description
F31	Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web pages within a set of Web pages.

Headings

SC 1.3.1 Info and Relationships

Failure	Description
F2	Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text.
F43	Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content.

Link Text

SC 1.1.1 Non-text Content

Failure	Description
F39	Failure of Success Criterion 1.1.1 due to providing a text alternative that is not null (e.g., alt=“spacer” or alt=“image”) for images that should be ignored by assistive technology.
F72	Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative.

SC 1.3.1 Info and Relationships

Failure	Description
F2	Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text.
F42	Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is not programmatically determinable.

SC 2.1.1 Keyboard

Failure	Description
F54	Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function.
F55	Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received.
F42	Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is not programmatically determinable.

SC 2.4.4 Link Purpose (In Context)

Failure	Description
F63	Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link.

SC 2.4.7 Focus Visible

Failure	Description
F55	Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received.
F78	Failure of Success Criterion 2.4.7 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator.

SC 3.2.4 Consistent Identification

Failure	Description
F31	Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web pages within a set of Web pages.