[contents] [checklist]

W3C

Techniques for WCAG 2.0

W3C Working Draft 27 April 2006

This version:
http://www.w3.org/TR/2006/WD-WCAG20-TECHS-20060427/
Latest version:
http://www.w3.org/TR/WCAG20-TECHS/
Editors:
Ben Caldwell, Trace Research & Development Center, University of Wisconsin-Madison
Wendy Chisholm, W3C
John Slatin, Accessibility Institute, University of Texas at Austin
Gregg Vanderheiden, Trace Research & Development Center, University of Wisconsin-Madison

Abstract

This document provides information to Web content developers who wish to satisfy the success criteria of "Web Content Accessibility Guidelines 2.0" [WCAG20] . General Techniques in this document are applicable to all technologies while HTML, CSS, Scripting, and SMIL techniques apply only to those technologies.

Use of the techniques provided in this document makes it easier for Web content to demonstrate conformance to WCAG 2.0 success criteria than if these techniques are not used.

There may be other techniques besides those provided in this document that may be used to demonstrate conformance to WCAG 2.0; in that case, submission of the techniques to the WCAG WG is encouraged so they can be considered for inclusion in this document, so that the set of techniques maintained by the WCAG WG is as comprehensive as possible. Please submit techniques for consideration using the "Techniques Submission Form."

This document is part of a series of documents published by the W3C Web Accessibility Initiative (WAI) to support WCAG 2.0.

Status of this Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

This is a First Public Working Draft of Techniques for WCAG 2.0. It is the first publication as a combined document; previously, techniques were published as separate documents - one for each technology. This document is being published as WCAG 2.0 goes to Last Call. It provides explanation of the techniques documented by the Web Content Accessibility Guidelines Working Group. Some are sufficient to meet a particular success criterion (either by themselves or in combination with other techniques) while other techniques are advisory and optional. None of the techniques are required to meet WCAG 2.0 although some may be the only known method if a particular technology is used.

The Working Group encourages review and comments on this document, in particular: is the format of the techniques clear? is the information useful? is the relationship to the normative document (WCAG 2.0) clear? Your comments on this Working Draft will help the WCAG Working Group improve the document before it is published as a Working Group Note when WCAG 2.0 becomes a W3C Recommendation.

Comments on this working draft are due on or before 31 May, 2006. To comment, please use one of the following standard response formats.

Instructions and downloads for all are available at http:///www.w3.org/WAI/WCAG20/comments/. Please send completed forms to public-comments-wcag20@w3.org.

The archives for the public comments list are publicly available. Archives of the WCAG WG mailing list discussions are also publicly available.

Please refer to Issue tracking for WCAG 2.0 Techniques for a list of open issues related to this Working Draft. The History of Changes to Techniques for WCAG 2.0 Working Drafts is also available.

Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document has been produced as part of the W3C Web Accessibility Initiative (WAI). The goals of the WCAG Working Group are discussed in the WCAG Working Group charter. The WCAG Working Group is part of the WAI Technical Activity.

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. The group does not expect this document to become a W3C Recommendation. This document is informative only. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.


Table of Contents


1. Common Failures


F1: Failure of SC 1.3.3 due to changing the meaning of content by positioning information with CSS

Applicability

All technologies that support CSS.

This technique is referenced from:

Description

This describes the failure condition that results when CSS, rather than structural markup, is used to modify the visual layout of the content, and the modified layout changes the meaning of the content. Using the positioning properties of CSS2, content may be displayed at any position on the user's viewport. The order in which items appear on a screen may be different than the order they are found in the source document. Assistive technologies rely on the source code or other programmatically determined order to render the content in the correct sequence. Thus, it is important not to rely on CSS for a visual-only layout which differs from the source code or programmatically determined reading order.

Examples

Failure Example 1

The following example demonstrates how CSS has been improperly used to create a set of columns. In addition, the text appears visually in the browser in a different order than in the markup.

In this example a class is defined for each object that is being positioned. When style sheets are applied, the text appears in two columns. Elements of class "menu1" (Products) and "menu2" (Locations) appear as column headings. "Telephones, Computers, and Portable MP3 Players" are listed under Products and "Idaho" and "Wisconsin" are listed under Locations (note the different order for Idaho and Wisconsin in the source code order).

Since appropriate structural elements have not been used, when style sheets are not applied, all of the text appears in one line in the source order, "Products Locations Telephones Computers Portable MP3 Players Wisconsin Idaho."

Here is the HTML content:

<div class="box">      
     <span class="menu1">Products</span>       
     <span class="menu2">Locations</span>       
     <span class="item1">Telephones</span>       
     <span class="item2">Computers</span>       
     <span class="item3">Portable MP3 Players</span>       
     <span class="item5">Wisconsin</span>       
     <span class="item4">Idaho</span>
</div>

Here are the styles for the above content:

.menu1 { 
     position: absolute; 
     top: 3em; 
     left: 0em;     
     margin: 0px; 
     font-family: sans-serif;     
     font-size: 120%; 
     color: red; 
     background-color: white 
}        
.menu2 { 
     position: absolute; 
     top: 3em; 
     left: 10em;     
     margin: 0px; 
     font-family: sans-serif;     
     font-size: 120%; 
     color: red; 
     background-color: white 
}      
.item1 { 
     position: absolute; 
     top: 7em; 
     left: 0em; 
     margin: 0px 
}      
.item2 { 
     position: absolute; 
     top: 8em; 
     left: 0em; 
     margin: 0px 
}      
.item3 { 
     position: absolute; 
     top: 9em; 
     left: 0em; 
     margin: 0px 
}      
.item4 { 
     position: absolute; 
     top: 7em; 
     left: 14em; 
     margin: 0px 
}      
.item5 { 
     position: absolute; 
     top: 8em; left: 14em; 
     margin: 0px 
}      
#box { 
     position: absolute; 
     top: 5em; 
     left: 5em 
} 

A better solution for this content would be to use more meaningful elements, such as a table or a definition list.

Resources

No resources available for this technique.

Tests

Procedure

For content which uses CSS for positioning:

  1. Remove the style information from the document or turn off use of style sheets in the user agent.

  2. Check that the reading order of the content is correct and the meaning of the content is preserved.

Expected Results
  • If step #2 is false, then this failure condition applies and the content fails this success criterion.


F2: Failure of SC 1.3.1 and 1.3.4 due to using CSS to create variations in presentation of text that conveys information without also using the appropriate markup or text

Applicability

All technologies that support CSS.

This technique is referenced from:

Description

It is a failure to use CSS to style text to convey information instead of conveying the information by using the appropriate markup or text. An HTML example is to use CSS to style text in bold for emphasis rather than using the strong element.

Examples

Failure Example 1: Emphasis in written dialogue.

Here is a CSS class to specify bold.

 .yell {
   font-weight:bold;
 }

The following example fails because the information conveyed by using the CSS font-weight property to change to a bold font is not conveyed through semantic markup or stated explicitly in the text.

<p>
 &quot;I said, <span class="yell">NO</span>, not before dinner!&quot;, 
 was the exasperated response when Timmy asked his mother for the 
 fourth time for an ice cream cone. 
</p>

Resources

No resources available for this technique.

Tests

Procedure
  1. Find visually styled elements on the page that convey information.

  2. Check that the appropriate semantics of the technology are used and that the information is not conveyed only by variations in presentation through CSS.

Expected Results
  • If step #2 is false, then this failure condition applies and the content fails this success criterion.


F3: Failure of SC 1.1.1 due to using CSS to include images that convey important information

Applicability

All technologies that support CSS.

This technique is referenced from:

Description

The CSS background-image property provides a way to include images in the document with CSS without any reference in the HTML code. The CSS background-image property was designed for decorative purposes and it is not possible to associate text alternatives with images that are included via CSS. Text alternatives are necessary for people who cannot see images that convey important information. Therefore, it is a failure to use this property to add images to convey important information.

Examples

Failure Example 1:

In the following example, part of the content is contained in an image that is presented by CSS alone. In this example, the image TopRate.png is a 180 by 200 pixel image that contains the text, "19.3% APR Typical Variable."

 The CSS contains: 
p#bestinterest {
  padding-left: 200px;
  background: transparent url(/images/TopRate.png) no-repeat top left;
}

It is used in this excerpt:

 
<p id="bestinterest">
  Where else would you find a better interest rate?
</p>
Failure Example 2:

A book distributor uses background images to provide icons against a list of book titles to indicate whether they are new, limited, in-stock, or out of stock.

The CSS contains:

ul#booklist li {
  padding-left: 20px;
}

ul#booklist li.new {
  background: transparent url(new.png) no-repeat top left; 
}
                            
ul#booklist li.limited {
  background: transparent url(limited.png) no-repeat top left; 
}
                            
ul#booklist li.instock {
  background: transparent url(instock.png) no-repeat top left; 
}

ul#booklist li.outstock {
  background: transparent url(outstock.png) no-repeat top left; 
}

It is used in this excerpt:

<ul id="booklist">
  <li class="new">Some book</li>
  <li class="instock">Some other book</li>
  <li class="limited">A book we desperately want to get rid of</li>
  ...
  <li class="outstock">A book you actually want </li>
</ul>

Resources

No resources available for this technique.

Tests

Procedure
  1. Examine all images added to the content via CSS.

  2. Check that the images do not convey important information.

Expected Results
  • Step #2. If it is true then this failure condition applies and content fails the success criterion.


F4: Failure of SC 2.2.2 due to using text-decoration:blink without a mechanism to stop it in less than three seconds

Applicability

Cascading Style Sheets.

This technique is referenced from:

User Agent and Assistive Technology Support Notes

The blink value of the text-decoration property is not supported by Internet Explorer. It is supported in Netscape/Mozilla family browsers. Not tested in others (e.g., Safari, Opera).

Description

CSS defines the blink value for the text-decoration property. When used, it causes any text in elements with this property to blink at a predetermined rate. This cannot be interrupted by the user, nor can it be disabled as a user agent preference. The blinking continues as long as the page is displayed. Therefore, content that uses text-decoration:blink fails the success criterion because blinking can continue for more than three seconds.

Examples

Failure Example 1

A product list page uses the text-decoration:blink style on an element to draw attention to sale prices. This fails the success criterion because users cannot control the blink.

<p>My Great Product <span style="text-decoration:blink">Sale! $44,995!</span></p>

Resources

Tests

Procedure
  1. Examine inline styles, internal stylesheets, and external stylesheets for the text-decoration property with a value of "blink".

  2. If the property is used, determine if the ID, class, or element identified by selectors on which this property is defined are used in the document.

Expected Results
  • If step #1 and step #2 are true, the content fails the success criterion.


F5: Failure of SC 3.1.1 due to using CSS styling to control directionality in XHTML/HTML

Applicability

(X)HTML documents that use CSS

This technique is referenced from:

User Agent and Assistive Technology Support Notes

Description

This describes a failure condition for (X)HTML documents that specify a text direction by using CSS styling, rather than using bidirectional markup. CSS provides support for text direction via the unicode-bidi and direction properties.

Because directionality is an integral part of the document structure, markup should be used to set the directionality for a document or chunk of information, or to identify places in the text where the Unicode bidirectional algorithm alone is insufficient to achieve desired directionality. Styling applied by CSS is not permanent. It may be turned off, be overridden, go unrecognised, or be changed/replaced in different contexts. Although bidirectional markup is only needed for the visual rendering of text, it is not purely decorative in function.

Examples

Failure Example 1

A style sheet setting the writing direction:

/* Rules for bidi */
HEBREW, HE-QUO  {direction: rtl; unicode-bidi: embed}
ENGLISH         {direction: ltr; unicode-bidi: embed} 
/* Rules for presentation */
HEBREW, ENGLISH, PAR  {display: block}
EMPH                  {font-weight: bold}

Resources

Tests

Procedure
  1. Remove the style information from the document or turn off use of style sheets in the user agent.

  2. Check that the text direction is correct.

Expected Results
  • If step #2 is false, then this failure condition applies and the content fails the success criterion.


F7: Failure of SC 2.2.2 due to an object or applet, such as Java or Flash, that has blinking content without a mechanism to pause the content that blinks for more than three seconds

Applicability

Technologies that support blinking content within an object, applet, or a plug-in.

This technique is referenced from:

Description

When content that is rendered by a plug-in or contained in an applet blinks, there may be no way for the user agent to pause the blinking. If neither the plug-in, applet, nor the content itself provides a mechanism to pause the content, the user may not have sufficient time to read the content between blinks or it may be so distracting that the user will not be able to read other content on the page.

Examples

  • An applet displays an advertisement on a news site. The applet blinks key words in the advertisement in order to call the user's attention to it. The blinking cannot be paused through any user agent settings and the applet does not provide a mechanism to stop it.

Tests

Procedure

For each page that has blinking content in a plugin or applet:

  1. Determine if the content continues to blink for longer than 3 seconds.

  2. Determine if there is a means to pause the blinking content.

Expected Results
  • If step #1 is true and step #2 is false, the content fails the success criterion.


F8: Failure of SC 1.2.1 due to captions omitting some dialogue or important sound effects

Applicability

Applies to all technologies.

This technique is referenced from:

Description

This describes a failure condition for all techniques involving captions. If the "caption" does not include all of the dialog (either verbatim or in essence) as well as all important sounds then the 'Captions' are not real captions.

NOTE: Captions sometimes simplify the spoken text both to make it easier to read and to avoid forcing the viewer to read at very high speed. This is standard procedure and does not invalidate a caption.

Examples

Failure Example 1

Examples of text streams that are not captions include:

  • subtitles that do not include important sounds

  • text that omits dialog during portions of the material

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. View the material with captioning turned on.

  2. Check that all dialog is accompanied by a caption.

  3. Check that all important sounds are captioned.

Expected Results
  • Step #2 and step #3 are true.


F9: Failure of SC 3.2.5 due to changing the context when the user removes focus from a form element

Applicability

General.

This technique is referenced from:

Description

This document describes a failure that occurs when removing focus from a form element, such as by moving to the next element, causes a change of context.

Examples

Failure Example 1:

The user is going through the form filling out the fields in order. When he moves from the third field to the forth, the form submits.

Resources

Tests

Procedure
  1. Find all form elements.

  2. Go through them in order.

  3. Check if the form submits when you move from one field to the next.

  4. Check if moving from one field to the next launches any new windows.

  5. Check if moving from one filed to the next navigates to another screen.

Expected Results
  • If step #3, step #4, or step #5 is true, then this failure condition applies and the content fails the success criterion.


F10: Failure of SC 2.1.1 due to combining multiple content formats in a way that traps users inside one format type

Applicability

Applies when content creates a situation where the user can enter the content using the keyboard, but can not exit the content using the keyboard.

User Agent and Assistive Technology Support Notes

  • None listed.

This technique is referenced from:

Description

When content includes multiple formats, one or more user agents or plug-ins are often needed in order to successfully present the content to users. For example, a page that includes (X)HTML, SVG, SMIL and XForms may require a browser to load as many as three different plug-ins in order for a user to successfully interact with the content. Some plug-ins create a common situation in which the keyboard focus can become "stuck" in inaccessible plug-ins, leaving a keyboard-only user with no way to return to the accessible content.

Examples

  • A plug-in traps the user A user tabs into a plug-in and is unable to return to content outside the plug-in content with the keyboard. The user has to restart their browser in order to regain control and navigate to a new page and is unable to access any content that appears beyond the plug-in content.

Resources

No resources available for this technique.

Tests

Procedure
  1. Using a keyboard, navigate through the content.

  2. Check to see that the keyboard focus is not "trapped" and it is possible to move keyboard focus out of the plug-in content without closing the user agent or restarting the system.

Expected Results
  • If the keyboard focus becomes "trapped," then this failure condition applies and content fails the success criterion.


F12: Failure of SC 2.2.6 due to having a session time-out without a mechanism for saving user's input and re-establishing that information upon re-authentication

Applicability

Sites that require user login to submit input and that terminate the session after a some period of inactivity.

This technique is referenced from:

Description

Web servers that require user authentication usually have a session mechanism in which a session times out after a period of inactivity from the user. This is sometimes done for security reasons, to protect users who are assumed to have left their computer exposed in a state where someone could do something harmful to them such as transfer bank funds or make an unauthorized purchase. A user with a disability may actually still be working to complete the form as it may take him or her longer to complete the form than would normally be expected. Upon re-authentication, if the state of the user's session is not restored, including all data that had been previously entered into the form, he or she will have to start over. And for these users, it is likely that the session will time out again before they can complete the form. This sets up a situation where a user who needs more time to complete the form can never complete it.

Examples

  • A user submits a form on an authenticated site after their login has expired. On submitting the form, they are prompted to log in again, and then taken to a general welcome page. The data is not processed and they must try again.

  • A user submits a form on an authenticated site after their login has expired. On submitting the form, they are prompted to log in again, and then taken back to the page they were on just before the login, which in this case contains the form they attempted to submit. However, the form is not populated with the data they just entered, and they must re-enter it.

Tests

Procedure

On a site where authentication is required, user input is collected, and which ends the user's session after a known period of inactivity:

  1. Provide user input as required but allow the session to time out, then submit the form.

  2. When requested, re-authenticate with the server.

  3. Determine if the function is performed using the previously submitted data.

Expected Results
  • If step #3 is false, the site fails the success criterion.


F13: Failure of SC 1.3.2 due to having a text alternative that does not include information that is conveyed by color in the image

Applicability

All technologies.

This technique is referenced from:

Description

This objective of this technique is to describe the failure that occurs when an image uses color to convey information, but the text alternative for the image does not convey that information. This can cause problems for people who are blind or colorblind because they will not be able to perceive the information conveyed by the color.

Examples

  • A bar chart of sales data is provided as an image. The chart includes yearly sales figures for four employees in the Sales Department. The text alternative for the image says, "The following bar chart displays the yearly sales figures for the Sales Department. Mary sold 3.1 Million; Fred, 2.6 Million; Bob, 2.2 Million; and Andrew, 3.4 Million. The red bars indicate sales that were below the yearly quota". This text alternative fails to provide the information which is conveyed by the color red in the image. The alternative should indicate which people did not meet the sales quota rather than relying on color.

Resources

No resources available for this technique.

Tests

Procedure

For all images in the content that convey information by way of color :

  1. Check that the information conveyed by color is not included in the text alternative for the image.

Expected Results
  • If step #1 is true, then this failure condition applies and content fails the success criterion.


F14: Failure of SC 1.3.5 due to identifying content only by its shape or location

Applicability

All technologies.

This technique is referenced from:

Description

The objective of this technique is to show how identifying content only by its shape or location makes content difficult to understand and operate. When only visual identification or location is used, users with visual disabilities may find it difficult to locate content since they cannot see the screen or may perceive only a small portion of the screen at one time. Also, location of content can vary if page layout varies due to variations in font, window, or screen size.

Examples

  • A user is completing an on-line survey. There are three buttons at the bottom of the survey form. The instructions state, "Press the square button to exit the survey without saving, Press the triangle button to save in-progress survey results. You may return later to complete the survey. Press the round button to submit the survey results." A screen reader user cannot determine which button is square, triangular, or round. The buttons must have additional information to indicate their functions.

  • A user is reading a news article in an on-line newspaper. The article contains an illustration and additional links for more information. Within the text of the article is a statement, "Please see sidebar to the left of the illustration for links to additional information." An assistive technology user would have difficulty finding the illustration and the sidebar. Some alternatives would be to include the list of links within the text; to provide an in-page link within the text which links to the sidebar; to provide a heading for the sidebar which can be used for navigation and refer to the heading in the instructions.

  • The navigation instructions for a site state, "To go to next page, press the button to the right. To go back to previous page, press the button to the left."

Resources

No resources available for this technique.

Tests

Procedure
  1. Examine the Web unit for textual references to content within the Web unit.

  2. Check that the references do not rely on only the shape or location of the content.

Expected Results
  • If step #2 is false, then this failure condition applies and the content fails this success criterion.


F15: Failure of SC 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely

Applicability

Applies to all technologies that support an accessibility API.

This technique is referenced from:

Description

When standard controls from accessible technologies are used, they usually are programmed in a way that uses and supports the accessibility API. If custom controls are created, however, then it is up to the programmer to be sure that the newly created control supports the accessibility API. If this is not done, then assistive technologies will not be able to understand what the control is or how to operate it or may not even know of its existence.

Examples

Failure Example 1

A music player is designed with custom controls that look like musical notes that are stretched for volume, tone etc. The programmer does not make the new control support the Accessibility API. As a result - the controls cannot be identified or controlled from AT.

Resources

(none currently listed)

Tests

Procedure
  1. Using the accessibility checker for the technology (or if that is not available, inspect the code or test with an assistive technology), check the controls to see if they support the accessibility API.

Expected Results
  • If step #1 is false, then this failure condition applies and the content fails this success criterion


F16: Failure of SC 2.2.3 due to including scrolling content where there is not a mechanism to pause and restart the content

Applicability

All technologies that support visual movement or scrolling.

This technique is referenced from:

Description

In this failure technique, there is moving or scrolling content that cannot be paused and resumed by users. In this case, some users with low vision or cognitive disabilities will not be able to perceive the content.

Examples

  • A page has a scrolling news ticker without a mechanism to pause it. Some users are unable to read the scrolling content.

Tests

Procedure

On a page with moving or scrolling content,

  1. Check that a mechanism is provided in the Web unit or user agent to pause moving or scrolling content.

  2. Use the pause mechanism to pause the moving or scrolling content.

  3. Check that the moving or scrolling has stopped and does not restart by itself.

  4. Check that a mechanism is provided in the Web unit or user agent to restart the paused content.

  5. Use the restart mechanism provided to restart the moving content.

  6. Check that the movement or scrolling has resumed from the point where it was stopped.

Expected Results
  • If steps step #1, step #3, step #4, or step #6 are false, then the content fails the success criterion.


F17: Failure of SC 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML

Applicability

Applies to the Document Object Model (DOM) for HTML 4.01 and XHTML 1.x.

This technique is referenced from:

Description

The objective of this technique is to ensure that Web pages can be interpreted consistently by user agents, including assistive technology. If it is ambiguous, different user agents including assistive technologies could present different information to their users. Users of assistive technology for example may have different information presented to them than users of other mainstream user agents. Some elements and attributes in markup languages are required to have unique values, and if this requirement is not honored, the result can be irregular or not uniquely resolvable content. For example, when id attribute values are not unique, they are particularly problematic when referenced by labels, headers in data tables, or used as fragment identifiers, as user agents do not have enough information to provide determine essential relationships (i.e. to determine which label goes with which item).

Examples

Failure Example 1
  • A label element whose for attribute value is an idref that points to a non-existent id

  • An id attribute value that is not unique.

  • An accesskey attribute value that is not unique

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Check for id and accesskey values which are not unique within the document.

  2. Check that attribute values that have an idref value have a corresponding id value.

  3. For tables that use the axis attribute, check that all values listed in the axis attribute have a corresponding id value in a table header cell in the same table.

  4. For client-side image maps, check that the value of the usemap attribute has a corresponding id value if the usemap attribute is not a URL.

Expected Results
  • If step #1, step #3 or step #4 is true or step #2 is false, then this failure condition applies and the content fails the success criterion.


F19: Failure of SC 4.2.1 and 4.2.3 due to not providing a method for the user to find the alternative conforming version of a non-conforming Web unit

Applicability

Sites that provide alternative, WCAG conforming versions of nonconforming primary content.

This technique is referenced from:

Description

This failure technique describes the situation in which an alternate, conforming version of the content is provided, but there is no direct way for a user to tell that it is available or where to find it. Such content fails the success criterion because the user cannot find the conforming version.

Examples

  • A link or a search takes a user directly to one of the nonconforming pages in the Web site. There is neither an indication that an alternate page is available, nor a path to the alternate page from the nonconforming page.

  • Nonconforming pages on the Web site inform the user that a conforming version is available and provide a link to the home page. However, the user must search the site for the conforming version of the page, so the functionality does not meet the requirements of the success criterion.

  • A user is able to use the nonconforming Web site for most pages. But when the user is not able to access a particular page, there is no way to find the conforming version of the page.

Tests

Procedure
  1. Identify a nonconforming page that has an alternative conforming version.

  2. Determine if the nonconforming page provides a link to the conforming version.

Expected Results
  1. If step #2 is false, the content fails the success criterion.


F20: Failure of SC 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur

Applicability

Applies to all technologies.

This technique is referenced from:

Description

The objective of this failure condition is to address situations where the non-text content is updated, but the text alternative is not updated at the same time. If the text in the text alternative can not still be used in place of the non-text content without losing information or function, then it fails because it is no longer a text alternative for the non-text content.

Examples

  • Failure Example 1: A Sales chart is updated to October results, but the text alternative still describes September results.

  • Failure Example 2: Pictures on a home page change daily, but text alternatives are not updated at the same time.

  • Failure Example 3: The source attribute of images on a page is updated periodically using script, but the text alternatives are not updated at the same time.

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Check each text alternative to see if it is describing content other than the currently-displayed non-text content.

Expected Results
  • If step #1 is true then the text alternative is not up to date with current item, this failure condition applies, and content fails the success criterion.


F22: Failure of SC 3.2.5 due to opening windows that are not requested by the user

Applicability

General

This technique is referenced from:

Description

Failure due to opening new windows when the user does not expect them. New windows take the focus away from what the user is reading or doing. This is fine when the user has interacted with a piece of User Interface and expects to get a new window, such as an options dialog. The failure comes when pop-ups appear unexpectedly.

Examples

Failure Example 1:

When a user navigates to a page, a new window appears over the existing user agent window, and the focus is moved to the new window.

Failure Example 2:

A user clicks on a link, and a new window appears. The original link has no associated text saying that it will open a new window.

Failure Example 3:

A user clicks on the body of a page and a new window appears. No indication that the area that was clicked has functionality is present.

Failure Example 4:

A user clicks on undecorated text within the page and a new window appears. No indication that the text is a link is available.

Resources

No resources available for this technique.

Tests

Procedure
  1. Load the Web unit.

  2. Check if new (additional) windows open.

  3. Find every actionable element, such as links and buttons, in the Web unit.

  4. Activate each element.

  5. Check if activating the element opens a new window.

  6. Check if elements that open new windows have associated text saying that will happen. The text can be displayed in the link, or available through a hidden association such as an HTML title attribute.

Expected Results
  • If step #2 is true, the failure condition applies and the content fails the success criterion

  • If step #5 is true and step #6 is false, the failure condition applies and the content fails the success criterion


F23: Failure of SC 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off

Applicability

Applies to all technologies except those for voice interaction.

This technique is referenced from:

Description

This describes a failure condition for SC involving sound. If sound does not turn off automatically within 3 seconds and there is no way to turn the sound off then SC 1.4.2 would not be met. Sounds that play over 3 seconds when there is no mechanism to turn off the sound included in the content would fall within this failure condition.

Examples

Example 1
  • a site that plays continuous background music

Example 2
  • a site with a narrator that lasts more than 3 seconds before stopping.

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Check that there is a way in content to turn off any sound that plays more than three seconds.

Expected Results
  • If step #1 is not true then content fails Success Criterion 1.4.2


F24: Failure of SC 1.4.1 due to specifying foreground colors without specifying background colors or vice versa

Applicability

All technologies that allow user agents to control foreground and background colors through personal stylesheets or other means.

This technique is referenced from:

Description

Users with vision loss or cognitive challenges often require specific foreground and background color combinations. For instance, many people with low vision find it much easier to see a Web page that has white text on a black background, so they may have set their user agent to create this contrast. If the author specifies that the text must be black, then it may override the settings of the user agent and render a page that has black text (specified by the author) on black background (that was set in the user agent). This principle also works in reverse. If the Webmaster forces the background to be white, then the white background specified by the author would be the same color as the white text (which was set in the user agent) rendering the page unusable to the user. Therefore, if the author specifies a foreground text color then they should also specify a background color which has sufficient contrast (link) with the foreground and vice versa.

Examples

Failure Example 1:

In the example below the background color is defined on the body element, however the foreground color is not defined. Therefore, the example fails the Success Criterion.

   
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  <html xmlns="<url>http://www.w3.org/1999/xhtml">http://www.w3.org/1999/xhtml</title>">
      <html>
          <head>
              <title>A study of population dynamics</title>
          </head>
          <body bgcolor="white">
              <p> ... document body...</p>
          </body>
  </html>
Failure Example 2:

In the example below the background color is defined on the CSS stylesheet, however the foreground color is not defined. Therefore, the example fails the Success Criterion.

  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<html>
<head>
 <title>Setting the canvas background</title>
    <style type="text/css">

       body {background-color:white}
    </style>
  </head>
  <body>
    <p>My background is white.</p>
  </body>
</html>
Failure Example 3:

In the example below the foreground color is defined on the body element, however the background color is not defined. Therefore, the example fails the Success Criterion.

 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<html>
<head>
 <title>A study of population dynamics</title>

</head>
<body color="white">
  <p>... document body...</p>
</body>
</html>
Failure Example 4:

In the example below the foreground color is defined on the CSS stylesheet, however the background color is not defined. Therefore, the example fails the Success Criterion.

 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<html>
<head>
 <title>Setting the canvas background</title>
    <style type="text/css">
       body {color:white}
    </style>
  </head>

  <body>
    <p>My foreground is white.</p>
  </body>
</html>
Failure Example 5:

In the example below the link text (foreground)color is defined on the body element, however the background color is not defined. Therefore, the example fails the Success Criterion.

  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" 
    "http://www.w3.org/TR/html4/strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<html>
<head>
 <title>A study of population dynamics</TITLE>
 <style type="text/css">
  a:link { color: red }
  a:visited { color: maroon }
  a:active { color: fuchsia }
 </style>

</head>
<body>
  <p>... document body... <a href="foo.htm">Foo</a></p>
</body>
</html>

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Examine the code of the Web unit.

  2. Check to see if a foreground color is specified

  3. Check to see if a background color is specified

Expected Results

If step #2 is true but step #3 is false, OR if step #3 is true but step #2 is false then this failure condition applies and content fails the success criterion.


F25: Failure of SC 2.4.3 due to the title of a Web unit not identifying the contents

Applicability

All technologies.

This technique is referenced from:

Description

This describes a failure condition when the Web unit has a title, but the title does not identify the contents or purpose of the Web unit.

Examples

Failure Example 1

Examples of text that are not titles include:

  • Authoring tool default titles, such as

    • "Enter the title of your HTML document here,"

    • "Untitled Document"

    • "No Title"

    • "Untitled Page"

    • "New Page 1"

  • Filenames that are not descriptive in their own right, such as "report.html" or "spk12.html"

  • Empty text

  • Filler or placeholder text

Failure Example 2

A site generated using templates includes the same title for each page on the site. So the title cannot be used to distinguish among the pages.

Resources

No resources available for this technique.

Tests

Procedure
  1. Check whether the title of each Web unit identifies the contents or purpose of the Web unit .

Expected Results
  • If step #1 is false, then this failure condition applies and the content fails this success criterion.


F26: Failure of SC 1.3.5 due to using a non-text mark alone to convey information

Applicability

All technologies.

This technique is referenced from:

Description

The objective of this technique is to show how using a non-text mark to convey information can make content difficult to comprehend. A non-text mark may be non-text content such as an image, or a font glyph which is not text nor an image of text. Users with cognitive disabilities or those using assistive technologies may have difficulty determining the meaning of the non-text mark. If a non-text mark is used to convey information, provide an alternative using features of the technology or use a different mechanism that can be marked with an alternative to represent the non-text mark. For example, an image with a text alternative can be used instead of the glyph.

Examples

Failure Example 1: Glyphs Used to Indicate Status

An instant messaging application uses two simple glyphs to indicate a person's instant messaging status. A check mark indicates that a person is on-line and available. An "x" character indicates that a person is not available. An assistive technology user could not determine a person's instant messaging status.

Resources

No resources available for this technique.

Tests

Procedure
  1. Examine the page for non-text marks that convey information.

  2. Check whether there are other means to determine the information conveyed by the non-text marks.

Expected Results
  • If step #2 is false, then this failure condition applies and the content fails this success criterion.


F28: Failure of SC 4.1.1 due to using markup that results in inconsistent DOMs in user agents

Applicability

Applies to the Document Object Model (DOM).

This technique is referenced from:

Description

The objective of this technique is to prevent Web pages from being presented inconsistently to users whose assistive technologies utilize a document object model (DOM). Incorrectly nested markup leads to inconsistent DOM representations being generated by user agents. The HTML specification does not define how user agents should deal with incorrectly nested markup, so user agent manufacturers have to define their own methods of dealing with it. In an attempt to honour the author's markup, some user agents introduce extra elements in the DOM to maintain a tree-like structure; other user agents end up with a DOM structure that is no longer a tree. As assistive technology gets more sophisticated and starts to make more use of the DOM, consistency becomes more critical.

Examples

Failure Example 1:

Incorrectly nested tags will cause inconsistencies in the DOM amongst different user agents, such as the following invalid example in HTML 4.01.

<strong><p>ABC</strong>DEF</p>

The above markup results in the following (differing)DOM representations in Firefox 1.5, Internet Explorer 6, and Opera 8.51.

Firefox 1.5

  • DOCTYPE: html

  • HTML

    • HEAD

    • BODY

      • STRONG

      • P

        • STRONG

          • #text: ABC

          #text: DEF

Internet Explorer 6

  • comment: CTYPE html PUBLIC "-//W3C//DTD HTML 4.01//E

  • HTML

    • HEAD

      • TITLE

      BODY

      • STRONG

        • P

          • #text: ABC

          • #text: DEF

        #text: DEF

Opera 8.51

  • HTML

    • BODY

      • STRONG

        • P

          • #text: ABC

          • #text: DEF

Resources

(none currently listed)

Tests

Procedure
  1. Using at least two different user agents examine the DOM generated from the markup. The user agents must have the same capabilities available. For example, if the markup relies on scripting, make certain that both user agents have scripting enabled.

  2. Determine if the DOMs are the same.

Expected Results

If step #2 is false, this failure condition applies and content fails the success criterion.


F30: Failure of SC 1.1.1 due to using text alternatives that are not alternatives (e.g. filenames or placeholder text)

Applicability

Applies to all technologies.

This technique is referenced from:

Description

This describes a failure condition for all techniques involving text alternatives. If the text in the "text alternative" cannot be used in place of the non-text content without losing information or function then it fails because it is not, in fact, an alternative to the non-text content.

Examples

Failure Example 1

Examples of text that are not text alternatives include:

  • placeholder text such as " " or "spacer" or "image" or "picture" etc that are put into the 'text alternative' location on images or pictures.

  • programming references that do not convey the information or function of the non-text content such as "picture 1", "picture 2" or "0001", "0002" or "Intro#1", "Intro#2".

  • filenames that are not valid text alternatives in their own right such as "Oct.jpg" or "Chart.jpg" or "sales\\oct\\top3.jpg"

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Check each text alternative to see if it is not actually a text alternative for the non-text content.

Expected Results
  • If step #1 is true then this failure condition applies and content fails the success criterion.


F31: Failure of SC 3.2.4 due to using two different labels for the same function on different pages

Applicability

Applies to all technologies.

This technique is referenced from:

Description

Components that have the same function in different Web units are more easily recognized if they are labeled consistently. If the naming is not consistent, some users may get confused.

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

Examples

Failure Example 1:

One of the most common examples of using inconsistent labels for components with the same function is to use a button that says "search" in one page and to use a button that says "find" on another page when they both serve the identical function.

Failure Example 2:

An online authoring tool that uses a button with "Save page" on one page and "Save" on another page, in both cases for the same function.

Example 3:

A Web site publishes articles online. Each article spans multiple Web pages and each page contains a link to the first page, the next page and the previous page of the article. If the references to the next page read "page 1", "page 2", "page 2" etcetera, the labels are not the same but they are consistent. Therefore, these references are not failures of this success criterion.

Failure Example 4:

An e-commerce application uses a printer icon that allows the user to print receipts and invoices. In one part of the application, the printer icon is labeled "Print receipt" and is used to print receipts, while in another part it is labeled "Print invoice" and is used to print invoices. The labeling is consistent ("Print x"), but the labels are different to reflect the different functions of the icons. Therefore, this example does not fail the success criterion.

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. In a set of Web units, find components with the same function that are repeated in multiple Web units.

  2. For each component with the same function found in step #1, check that the naming is consistent.

Expected Results

If step #2 is false then this failure condition applies and content fails the success criterion.


F32: Failure of SC 1.3.3 due to using white space characters to control spacing within a word

Applicability

All technologies.

This technique is referenced from:

Description

The objective of this technique is to describe how using blank characters, such as space, tab, line break, or carriage return, to format individual words visually can be a failure to present meaningful sequences properly. Blank characters have no appearance when rendered visually, but affect the positioning of adjacent characters. When blank characters are inserted to control letter spacing within a word, they may change the interpretation of the word or cause it not to be recognized as a single word.

Inserting white space characters into an initialism is not an example of this failure, since the white space does not change the interpretation of the initialism and may make it easier to understand.

The use of white space between words for visual formatting is not a failure, since it does not change the interpretation of the words.

Examples

Failure Example 1: Failure due to adding white space in the middle of a word

This example has white spaces within a word to space out the letters in a heading. Screen readers may read each letter individually instead of the word "Welcome."

<h1>W e l c o m e</h1>

&nbsp; can also be used to add white space, producing similar failures:

<h1>H&nbsp;E&nbsp;L&nbsp;L&nbsp;O</h1>
Failure Example 2: White space in the middle of a word changing its meaning

In Japanese, Han characters(Kanji) may have multiple readings that mean very different things. In this example, the word is read incorrectly because screen readers may not recognize these characters as a word because of the white space between the characters. The characters mean "Tokyo," but screen readers say "Higashi Kyo".

<h1>東 京</h1>
Failure Example 3: Using line break characters to format vertical text

In the row header cell of a data table containing Japanese text, authors often create vertical text by using line break characters. However screen readers are not able to read the word of vertical text correctly because the line breaks occur within the word. In the following example, "東京都"(Tokyo-to) will be read "Higashi Kyo Miyako".

<table>
<caption>表1. 都道府県別一覧表</caption>
<tr>
<td></td>
<th scope="col">(見出しセル 1.)</th>
<th scope="col">(見出しセル 2.)</th>
</tr>
<tr>
<th scope="row">東<br />京<br />都</th>
<td>(データセル 1.)</td>
<td>(データセル 2.)</td>
</tr>
・・・・・・
</table>

Resources

No resources available for this technique.

Tests

Procedure

For each word that appears to have non-standard spacing between characters:

  1. Check whether any words in the text of the content contain white space characters .

Expected Results
  • If step #1 is true, then this failure condition applies and the content fails this success criterion.


F33: Failure of SC 1.3.1 and 1.3.3 due to using white space characters to create multiple columns in plain text content

Applicability

All technologies.

This technique is referenced from:

Description

The objective of this technique is to describe how using white space characters, such as space, tab, or carriage return, to format columns of data in text content is a failure to use structure properly. Assistive technologies will interpret content in the reading order of the current language. Using white space characters to create multiple columns does not provide the information in a natural reading order. Thus, the assistive technology user will not be presented with the information in an understandable manner.

Plain text is not suitable for displaying multiple columns of text. Modify the content to present the data in a different layout. Alternatively, use a technology that provides structural elements to represent columnar data.

Examples

Failure Example 1

The following example incorrectly uses white space characters to format a paragraph into a two column format.

Web Content Accessibility Guidelines      including blindness and low vision, 
2.0 (WCAG 2.0) covers a wide range of     deafness and hearing loss, learning 
issues and recommendations for making     difficulties, cognitive limitations, limited 
Web content more accessible. This         movement, speech difficulties, and 
document contains principles,             others. Following these guidelines will 
guidelines, success criteria, benefits,   also make your Web content more 
and examples that define and explain      accessible to the vast majority of users, 
the requirements for making Web-based     including older users. It will also enable
information and applications accessible.  people to access Web content using 
"Accessible" means usable to a wide       many different devices - including a 
range of people with disabilities,        wide variety of assistive technologies.

If this table was to be interpreted and spoken by a screen reader it would speak the following lines:

  • Web Content Accessibility Guidelines including blindness and low vision,

  • 2.0 (WCAG 2.0) covers a wide range of deafness and hearing loss, learning

  • issues and recommendations for making difficulties, cognitive limitations, limited

  • Web content more accessible. This movement, speech difficulties, and

  • (additional lines eliminated for brevity)

If the text were reflowed, or changed from a fixed to a variable font, or increased in size until lines no longer fit on the page, similar interpretation issues would arise in the visual presentation.

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Examine the document for data or information presented in columnar format.

  2. Check whether the columns are created using white space characters to lay out the information.

Expected Results
  • If step #2 is true, then this failure condition applies and the content fails this success criterion.


F34: Failure of SC 1.3.1 and 1.3.3 due to using white space characters to format tables in plain text content

Applicability

All technologies.

This technique is referenced from:

Description

The objective of this technique is to describe how using white space characters, such as space, tab, or carriage return, to format tables in text content is a failure to use structure properly. When tables are created in this manner there is no way to indicate that a cell is intended to be a header cell, no way to associate the table header cells with the table data cells, or to navigate directly to a particular cell in a table.

In addition, assistive technologies will interpret content in the reading order of the current language. Using white space to organize data in a visual table does not provide the information in a natural reading order in the source of the document. Thus, the assistive technology user will not be presented with the information in a logical reading order.

Plain text is not suitable for displaying complex information like tables because the structure of the table cannot be perceived. Rather than using visual formatting to represent tabular relations, present the data in a presentation format other than a table. Alternatively, use a technology that provides structural elements to represent tables.

Examples

Failure Example 1

The following example incorrectly uses white space to format a Menu as a visual table.

Menu
         Breakfast        Lunch           Dinner

Monday   2 fried eggs    tomato soup     garden salad
         bacon           hamburger       Fried Chicken
         toast           onion rings     green beans
                         Oatmeal cookie  mashed potatoes

Tuesday   Pancakes       vegetable soup  Caesar salad
          sausage        hot dogs        Spaghetti with meatballs
          orange juice   potato salad    Italian bread
                         brownie         ice cream

If this table was to be interpreted and spoken by a screen reader it would speak the following lines:

  • Menu

  • Breakfast Lunch Dinner

  • Monday 2 fried eggs tomato soup garden salad

  • bacon hamburger Fried Chicken

  • toast onion rings green beans

  • Oatmeal cookie mashed potatoes

This reading order does not make sense since there is no structure in the table for the assistive technology to identify it as a table. If the text were reflowed, or changed from a fixed to a variable font, or increased in size until lines no longer fit on the page, similar issues would arise in the visual presentation.

Resources

No resources available for this technique.

Tests

Procedure
  1. Examine the document for visually formatted tables.

  2. Check whether the tables are created using white space characters to layout the tabular data.

Expected Results
  • If step #2 is true, then this failure condition applies and the content fails this success criterion.


F36: Failure of SC 3.2.2 due to automatically submitting a form and presenting new content without prior warning when the last field in the form is given a value

Applicability

HTML 4.x and XHTML 1.x.

This technique is referenced from:

Description

Forms are frequently designed so that they submit automatically when the user has filled in all the fields, or when focus leaves the last field. There are two problems with this approach. First is that a disabled user who needs more context may move focus away from the field to the directions on how to fill in the form, or to other text, accidentally submitting the form. The other is that, with some form elements, the value of the field changes as each item is navigated with the keyboard, again accidentally submitting the form. It is better to rely on the standard form behavior of the submit button and enter key.

Examples

Failure Example 1:

This failure example submits a form when the user leaves the last field of a three-field telephone number form. The form will submit if the user leaves the field after editing it, even navigating backwards in the tab order. Developers should not use this method to submit a form, and should instead use a submit button, or rely on the form's default behavior of submitting when the user hits enter in a text field.

 
<form method="get" id="form1">
  <input type="text" name="text1" size="3" maxlength="3"> - 
  <input type="text" name="text2" size="3" maxlength="3"> - 
  <input type="text" name="text3" size="4" maxlength="4" onchange="form1.submit();">
</form> 
Failure Example 2:

This is a deprecated example that submits a form when the user selects an option from the menu. The form will submit as soon as an item from the menu is selected. A user using a keyboard will not be able to navigate past the first item in the menu.

 
<form method="get" id="form2">
 <input type="text" name="text1">
  <select name="select1" onchange="form2.submit();">
    <option>one</option>
    <option>two</option>
    <option>three</option>
    <option>four</option>
  </select>
</form>

Resources

Tests

Procedure
  1. Enter data in all fields on page starting at top.

  2. Enter data in last field and exit from it (tab out of it).

  3. Check whether leaving the last field causes change of context.

Expected Results
  • If step #3 is true, then this failure condition applies and content fails the success criterion.


F37: Failure of SC 3.2.2 due to launching a new window without prior warning when the status of a radio button, check box or select list is changed

Applicability

HTML 4.x and XHTML 1.x.

This technique is referenced from:

User Agent and Assistive Technology Support Notes

Internet Explorer 6 also triggers the onclick event when a radio button with onclick receives focus; adding other event handlers (onxxx attributes) to prevent this does not work.

Description

This document describes a failure that occurs when changing the status of a radio button, a check box or an item in a select list causes a new window to open. It is possible to use scripting to create an input element that causes a change of context (submit the form, open a new page, a new window) when the element is selected. Developers can instead use a submit button (see Providing a submit button to initiate a change of context) or clearly indicate the expected action.

Examples

Failure Example 1:

The example below fails the success criterion because it processes the form when a radio button is selected instead of using a submit button.

  
<script type="text/JavaScript"> 
  function goToMirror(theInput) {
   var mirrorSite = "http://download." + theInput.value + "/"; 
   window.open(mirrorSite); 
  }
</script>
  …
<form name="mirror_form" id="mirror_form" action="" method="get">
       <p>Please select a mirror download site:</p> 
       <p> 
       <input type="radio" onclick="goToMirror(this);" name="mirror" 
       id="mirror_belnet" value="belnet.be" /> 
       <label for="mirror_belnet">belnet (<abbr>BE</abbr>)</label><br /> 
       <input type="radio" onclick="goToMirror(this);" name="mirror" 
       id="mirror_surfnet" value="surfnet.nl" /> 
       <label for="mirror_surfnet">surfnet (<abbr>NL</abbr>)</label><br /> 
       <input type="radio" onclick="goToMirror(this);" name="mirror" 
       id="mirror_puzzle" value="puzzle.ch" /> 
       <label for="mirror_puzzle">puzzle (<abbr>CH</abbr>)</label><br /> 
       <input type="radio" onclick="goToMirror(this);" name="mirror" 
       id="mirror_voxel" value="voxel.com" /> 
       <label for="mirror_voxel">voxel (<abbr>US</abbr>)</label><br /> 
       </p> 
</form>

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Find each form in a page.

  2. For each form control that is a radio button, check box or an item in a select list, check if changing the status of the control launches a new window.

  3. For each new window resulting from step 2, check if the user is warned in advance.

Expected Results

If step #3 is false, then this failure condition applies and content fails the success criterion.


F38: Failure of SC 1.1.1 due to omitting the alt-attribute for non-text content used for decorative purposes only in HTML

Applicability

Applies to HTML 4.x and XHTML 1.x.

This technique is referenced from:

Description

This describes a failure condition for text alternatives for images that should be ignored by AT. If there is no alt attribute at all assistive technologies are not able to ignore the non-text content. The alt attribute must be proved and have a null value (i.e. alt="" or alt=" ") to avoid a failure of this success criterion.

Note: Although alt=" " is valid, alt="" is recommended.

Examples

  • Failure Example 1: Decorative images that have no alt attribute

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Identify any img and applet elements that are used for purely decorative content;

  2. Check that the alt attribute for these elements exists.

  3. Check that the alt attribute for these elements is null.

Expected Results
  • if step #2 or step #3 is false, this failure condition applies and content fails the success criterion.


F39: Failure of SC 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 AT

Applicability

Applies to HTML 4.x and XHTML 1.x.

This technique is referenced from:

Description

This describes a failure condition for text alternatives for images that should be ignored by AT. If there is no alt attribute at all assistive technologies are not able to ignore the non-text content. The alt attribute must be proved and have a null value (i.e. alt="" or alt=" ") to avoid a failure of this success criterion.

Note: Although alt=" " is valid, alt="" is recommended.

Examples

  • Failure Example 1: Decorative images that have no alt attribute

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Identify any img and applet elements that are used for purely decorative content;

  2. Check that the alt attribute for these elements exists.

  3. Check that the alt attribute for these elements is null.

Expected Results
  • If step #2 or step #3 is false, this failure condition applies and content fails the success criterion.


F40: Failure of SC 2.2.1 due to using meta redirect with a time-out

Applicability

All pages

This technique is referenced from:

Description

meta http-equiv of {time-out}; url=... is often used to automatically redirect users. When this occurs after a time delay, it is an unexpected change of context that may interrupt the user.

It is acceptable to use the meta element to create a redirect when the time-out is set to zero, since the redirect is instant and will not be perceived as a change of context. However, it is preferable to use server-side methods to accomplish this. See Implementing automatic redirects on the server side instead of on the client side.

Examples

Failure Example 1

The page below is a failure because it will redirect to the URL http://www.example.com/newpage after a time-out of 5 seconds.

<html xmlns="http://www.w3.org/1999/xhtml">
   <head>     
      <title>Do not use this!</title>     
      <meta http-equiv="refresh"
      content="5; url=http://www.example.com/newpage" />   
   </head>   
   <body>     
      <p>       
         If your browser supports Refresh, you'll be       
         transported to our        
         <a href="http://www.example.com/newpage">new site</a>        
         in 5 seconds, otherwise, select the link manually.     
      </p>   
   </body> 
</html>

Resources

Tests

Procedure
  1. View a page.

  2. Check that the page does not redirect after a time-out.

Expected Results
  1. #2 is true.


F41: Failure of SC 2.2.1, 2.2.5, and 3.2.5 due to using meta refresh with a time-out

Applicability

HTML 4.x and XHTML 1.x.

This technique is referenced from:

Description

meta http-equiv of refresh is often used to periodically refresh pages or to redirect users to another page. If the time interval is too short, people who are blind will not have enough time to make their screen readers read the page before the page refreshes unexpectedly and causes the screen reader to begin reading at the top. Sighted users may also be disoriented by the unexpected refresh.

Examples

Failure Example 1

This is a deprecated example that changes the user's page at regular intervals. Content developers should not use this technique to simulate "push" technology. Developers cannot predict how much time a user will require to read a page; premature refresh can disorient users. Content developers should avoid periodic refresh and allow users to choose when they want the latest information. (The number in the content attribute is the refresh interval in seconds.)

<html xmlns="http://www.w3.org/1999/xhtml">   
  <head>     
    <title>HTML Techniques for WCAG 2.0</title>     
    <meta http-equiv="refresh" content="60" />   
  </head>   
  <body>
    ...     
  </body> 
</html>
Failure Example 2

This is a deprecated example that redirects the user to another page after a number of seconds. Content developers are recommended to user server-side redirects instead. (The number in the content attribute is the refresh interval in seconds.)

<html xmlns="http://www.w3.org/1999/xhtml">   
  <head>     
    <title>The Tudors</title>     
    <meta http-equiv="refresh" content="10;URL='http://thetudors.example.com/'" />   
  </head>   
  <body>
    <p>This page has moved to a <a href="http://thetudors.example.com/">
    theTudors.example.com</a>. Please note that we now have our own 
    domain name and will redirect you in a few seconds. Please update 
    your links and bookmarks.</p>
  </body> 
</html>

Tests

Procedure
  1. Find meta elements in the document.

  2. For each meta element, check if it contains the attribute http-equiv with value "refresh" (case-insensitive) and the content attribute with a number (representing seconds) greater than 0.

Expected Results
  • If step 2 is true then this failure condition applies and content fails the success criterion.


F42: Failure of SC 1.3.1 due to using scripting events to emulate links

Applicability

HTML 4.01 and XHTML 1.x with Scripting.

This technique is referenced from:

Description

This failure occurs when JavaScript event handlers are attached to elements to ''emulate links''. If scripting events are used to emulate links, user agents including assistive technology may not be able to identify the links in the content as links. They may not be recognized as interactive controls by assistive technology, or they may be recognized as interactive controls but still not recognized as links. Such elements do not appear in the links list generated by user agents or assistive technology.

The <a href> and <area> elements are intended to mark up links.

Attaching event handlers to elements that are not normally interactive, such as span and div, can be quite disorienting to users. Even if care is taken to provide keyboard access to such elements, users may have a difficult time discovering that there are interactive controls in the content or understanding what type of behavior to expect from them. For example, users may not know which keystrokes are supported by the script to activate the element. Additionally, these elements do not generate the same operating system events as interactive elements, so assistive technology may not be notified when the user activates them.

Examples

Failure Example 1: Scripting a <span> element

Scripted event handling is added to a span element so that it functions as a link when clicked with a mouse. Assistive technology does not recognize this element as a link.

<span onclick="this.location.href='newpage.html'">
    Fake link
</span>
Failure Example 2: Scripting an <img> element

Scripted event handling is added to an img element so that it functions as a link when clicked with a mouse. Assistive technology does not recognize this element as a link.

   src="go.gif" 
   alt="go to the new page" 
   onclick="this.location.href='newpage.html'"
Failure Example 3: Scripting an <img> element, with keyboard support

Scripted event handling is added to an img element so that it functions as a link. In this example, the link functionality can be invoked with the mouse or via the Enter key if the user agent includes the element in the tab chain. Nevertheless, the element will not be recognized as a link.

function doNav(url)
{
   window.location.href = url;
}

function doKeyPress(url)
{
   //if the enter key was pressed
   if (window.event.type == "keypress" &&
       window.event.keyCode == 13)
   {
      doNav(url);
   }
}

The markup for the image is:

<p>
	<img src="bargain.jpg"
		tabindex="0" 
		alt="View Bargains"
		onclick="doNav('viewbargains.html');"
		onkeypress="doKeyPress('viewbargains.html');"
	>
</p>
Failure Example 4: Scripting a <div> element

This example uses script to make a div element behave like a link. Although the author has provided complete keyboard access and separated the event handlers from the markup to enable repurposing of the content, the div element will not be recognized as a link by assistive technology.

window.onload = init;

function init()
{
	var objAnchor = document.getElementById('linklike');

	objAnchor.onclick = function(event){return changeLocation(event,
'surveyresults.html');};
	objAnchor.onkeypress = function(event){return changeLocation(event,
'surveyresults.html');};
}

function changeLocation(objEvent, strLocation)
{
	var iKeyCode;

	if (objEvent && objEvent.type == 'keypress')
	{
		if (objEvent.keyCode)
			iKeyCode = objEvent.keyCode;
		else if (objEvent.which)
			iKeyCode = objEvent.which;

		if (iKeyCode != 13 && iKeyCode != 32)
			return true;
	}

	window.location.href = strLocation;
}

The markup for the div element is:

<div id="linklike">
View the results of the survey.
</div>

Resources

No resources available for this technique.

Tests

Procedure
  1. Check whether there are JavaScript event handlers on an element that emulates a link.

  2. Check whether the programmatically determined role of the element is link.

Expected Results
  • If check #1 is true and check #2 is false, then this failure condition applies and content fails the success criterion.


F43: Failure of SC 1.3.1 due to using structural markup in a way that does not represent relationships in the content

Applicability

(X)HTML

This technique is referenced from:

Description

The objective of this technique is to describe a failure that occurs when structural markup is used to achieve a presentational effect, but indicates relationships that do not exist in the content. This is disorienting to users who are depending on those relationships to navigate the content or to understand the relationship of one piece of the content to another. Note that the use of HTML tables for layout is not an example of this failure as long as the layout table does not include improper structural markup such as <th> or <caption> elements.

Examples

Failure Example 1: A heading used only for visual effect

In this example, a heading element is used to display an address in a large, bold font. The address does not identify a new section of the document, however, so it should not be marked as a heading.

<p>Interested in learning more? Write to us at</p> 
<h4>3333 Third Avenue, Suite 300 · New York City</h4>

<p>And we’ll send you the complete informational packet absolutely Free!</p>
Failure Example 2: Using heading elements for presentational effect

In this example, heading markup is used in two different ways: to convey document structure and to create visual effects. The h1 and h2 elements are used appropriately to mark the beginning of the document as a whole and the beginning of the abstract. However, the h3 and h4 elements between the title and the abstract are used only for visual effect — to control the fonts used to display the authors’ names and the date.

<h1>Study on the Use of Heading  Elements in Web Pages</h1>
<h3>Joe Jones and Mary Smith<h3>
<h4>March 14, 2006</h4>
<h2>Abstract</h2>
<p>A study was conducted in early 2006 ...
</p>
Failure Example 3: Using blockquote elements to provide additional indentation

The following example uses blockquote for text that is not a quotation to give it prominence by indenting it when displayed in graphical browsers.

<p>After extensive study of the company Web site, the task force 
identified the following common problem.</p>

<blockquote>
<p>The use of markup for presentational effects made Web 
pages confusing to screen reader users.</p>
</blockquote>

<p>The committee lists particular examples of the problems 
introduced by this practice below.</p>
Failure Example 4: Using the fieldset and legend elements to give a border to text
<fieldset>
<legend>Bargain Corner</legend>
<p>Buy today, and save 20%</p>
</fieldset>

Resources

No resources available for this technique.

Tests

Procedure
  1. Check that each element's semantic meaning is appropriate for the content of the element.

Expected Results
  • If check #1 is false, then this failure condition applies and the content fails the success criterion.


F44: Failure of SC 2.4.6 due to using tabindex to create a tab order that does not follow relationships and sequences in the content

Applicability

(X)HTML

This technique is referenced from:

Description

This document describes a failure that occurs when the tab order does not follow logical relationships and sequences in the content.

Focusable elements like links and form elements have a tabindex attribute. The elements receive focus in ascending order of the value of the tabindex attribute. When the values of the tabindex attribute are assigned in a different order than the relationships and sequences in the content, the tab order no longer follows the relationships and sequences in the content.

One of the most common causes of this failure occurs when editing a page where tabindex has been used. It is easy for the tab order and the content order to fall out of correspondence when the content is edited but the tabindex attributes are not updated to reflect the changes to the content.

Examples

Failure Example 1

The following example incorrectly uses tabindex to specify an alternative tab order:

<ul>
   <li><a href="main.html" tabindex="1">Homepage</a></li>
   <li><a href="chapter1.html" tabindex="4">Chapter 1</a></li>
   <li><a href="chapter2.html" tabindex="3">Chapter 2</a></li>
   <li><a href="chapter3.html" tabindex="2">Chapter 3</a></li>
</ul>

If this list is navigated by the tab key, the list is navigated in the order Homepage, chapter 3, chapter 2, chapter 1, which does not follow the sequence in the content.

Failure Example 2

The tab order has been set explicitly in a Web page by providing tabindex attributes for all fields. Later, the page is modified to add a new field in the middle of the page, but the author forgets to add a tabindex attribute to the new field. As a result, the new field is at the end of the tab order.

Resources

Tests

Procedure
  1. If tabindex is used, check that the tab order specified by the tabindex attributes follows relationships in the content.

Expected Results
  • If check #1 is false, then this failure condition applies and content fails the success criterion.


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

Applicability

(X)HTML

This technique is referenced from:

Description

The objective of this technique is to describe a failure that occurs when a table used only for layout includes either th elements, a summary attribute, or a caption element. This is a failure because it uses structural (or semantic) markup only for presentation. The intent of the HTML table element is to present data.

Assistive technologies use the structure of an HTML table to present data to the user in a logical manner. The th element is used to mark the column and row headers of the table. A screen reader uses the information in th elements to speak the header information that changes as the user navigates the table. The summary attribute on the table element provides a textual description of the table that describes its purpose and function. Assistive technologies make the summary attribute information available to users. The caption element is part of the table and identifies the table.

While the preference is to use CSS for visual formatting, tables are often used to visually layout content in an HTML document. When a table is used for layout purposes the th element should not be used. Since the table is not presenting data there is no need to mark any cells as column or row headers. Likewise, there is no need for an additional description of a table which is only used to layout content. Do not include a summary attribute and do not use the summary attribute to describe the table as, for instance, "layout table". When spoken, this information does not provide value and will only distract users navigating the content via a screen reader. Empty summary attributes are acceptable on layout tables, but not recommended.

Examples

Failure Example 1

Here is a simple example that uses a table to layout content in a three column format. The navigation bar is in the left column, the main content in the middle column, and an additional sidebar is on the right. At the top is a page title. The example marks the page title as <th>, and provides a summary attribute indicating that the table is a layout table.

 <table summary="layout table">
 <tr>
   <th colspan=3>Page Title</th>
 </tr>
 <tr>
   <td><div>navigation content</div></td>
   <td><div>main content</div></td>
   <td><div>right sidebar content</div></td>
 </tr>
 <tr>
   <td colspan=3>footer</td>
 </tr>
 </table>

Resources

No resources available for this technique.

Tests

Procedure
  1. Examine the source code of the HTML document for the table element

  2. If the table is used only to visually lay out elements within the content

    1. Check that the table does not contain any th elements.

    2. Check that the table element does not contain a non-empty summary attribute.

    3. Check that the table element does not contain a caption element.

Expected Results
  • If any check above is false, then this failure condition applies and the content fails the success criterion.


F47: Failure of SC 2.2.2 due to using the blink element

Applicability

HTML and XHTML.

This technique is referenced from:

User Agent and Assistive Technology Support Notes

The blink element is not supported by Internet Explorer. It is supported in Netscape/Mozilla family of user agents and Opera. Not tested in others (e.g., Safari).

Description

The blink element, while not part of the official HTML specification, is supported by many user agents. It causes any text inside the element to blink at a predetermined rate. This cannot be interrupted by the user, nor can it be disabled as a preference. The blinking continues as long as the page is displayed. Therefore, content that uses blink fails the success criterion because blinking can continue for more than three seconds.

Examples

Failure Example 1

A product list page uses the blink element to draw attention to sale prices. This fails the success criterion because users cannot control the blink.

<p>My Great Product <blink>Sale! $44,995!</blink></p>

Tests

Procedure
  1. Examine code for the presence of the blink element.

Expected Results
  • If #1 is true, the content fails the success criterion.


F48: Failure of SC 1.3.1 due to using the pre element to markup tabular information

Applicability

HTML 4.01, XHTML 1.x

This technique is referenced from:

Description

This document describes a failure caused by use of the HTML pre element to markup tabular information. The pre element preserves only visual formatting. If the pre element is used to markup tabular information, the visually implied logical relationships between the table cells and the headers are lost if the user cannot see the screen or if the visual presentation changes significantly.

Instead, the HTML table element is intended to present tabular data. Assistive technologies use the structure of an HTML table to present data to the user in a logical manner. This structure is not available when using the pre element.

Examples

Failure Example 1: A schedule formatted with tabs between columns
 <pre>
 	Monday	Tuesday	Wednesday	Thursday	Friday
 8:00-
 9:00	Meet with Sam				
 9:00-
 10:00			Dr. Williams	Sam again	Leave for San Antonio
 </pre>
Failure Example 2: Election results displayed using preformatted text
 <pre>
   CIRCUIT COURT JUDGE BRANCH 3
                                                  W
                                                   R
                                          M R E     I
                                           A . L     T
                                     M L    R   B     E
                                      I A    Y   E     -
                                       K N        R     I
                                        E G        T     N
                                       -----   -----   -----
0001 TOWN OF ALBION WDS 1-2               22      99       0
0002 TOWN OF BERRY WDS 1-2                52     178       0
0003 TOWN OF BLACK EARTH                  16      49       0
0004 TOWN OF BLOOMING GROVE WDS 1-3       44     125       0
0005 TOWN OF BLUE MOUNDS                  33     117       0
0006 TOWN OF BRISTOL WDS 1-3             139     639       1
0007 TOWN OF BURKE WDS 1-4                80     300       0
0008 TOWN OF CHRISTIANA WDS 1-2           22      50       0

 </pre>

Resources

No resources available for this technique.

Tests

Procedure
  1. Check to see if the pre element is used

  2. For each occurrence of the pre element, check whether the enclosed information is tabular.

Expected Results
  • If check #2 is true, then this failure condition applies and the content fails the success criterion.


F49: Failure of SC 1.3.3 due to changing the meaning of content by positioning information with HTML layout tables

Applicability

HTML, XHTML 1.x

This technique is referenced from:

User Agent and Assistive Technology Support Notes

Early screen readers literally read Web content from the screen, which lead to problems when tables were used for layout where one table cell was meant to be read in its entirety before reading the next table cell. Today's screen readers work with the underlying markup, which means that they do read a table cell in its entirety before moving on to the next cell, but layout tables may still inadvertently introduce problems with the natural reading order of the content.

Description

This failure occurs when a meaningful sequence of content conveyed through presentation is lost because HTML tables used to control the visual placement of the content do not “linearize” correctly. Tables present content in two visual dimensions, horizontal and vertical. However, screen readers present this two-dimensional content in linear order of the content in the source, beginning with the first cell in the first row and ending with the last cell in the last row. The screen reader reads the table from top to bottom, reading the entire contents of each row before moving to the next row. The complete content of each cell in each row is spoken—including the complete content of any table nested within a cell. This is called linearization.

Suppose that a Web page is laid out using a table with 9 columns and 22 rows. The screen reader speaks the content of the cell at Column 1, Row 1 followed by the cells in columns 2, 3, 4 and so on to column 9. However, if any cell contains a nested table, the screen reader will read the entire nested table before it reads the next cell in the original (outer) table. For example, if the cell at column 3, row 6 contains a table with 6 columns and 5 rows, all of those cells will be read before Column 4, Row 6 of the original (outer) table. As a result, the meaningful sequence conveyed through visual presentation may not be perceivable when the content is spoken by a screen reader.

Examples

Failure Example 1: A layout table that does not linearize correctly

An advertisement makes clever use of visual positioning, but changes meaning when linearized.

<table>
<tr>
  <td><img src="logo.gif" alt="XYZ mountaineering"></td>
  <td>top!</td>
</tr>
<tr>
  <td colspan="2">XYZ gets you to the</td>
</tr>
</table>

The reading order from this example would be:

  • XYZ mountaineering top!

  • XYZ gets you to the

Failure Example 2: A layout table that separates a meaningful sequence when linearized

A Web page from a museum exhibition positions a navigation bar containing a long list of links on the left side of the page. To the right of the navigation bar is an image of one of the pictures from the exhibition. To the right of the image is the kind of "placard" text you'd see on the wall next to the object if you were at the museum. Below that text is a heading that says "Description," and below that heading is a description of the image. The image, placard text, Description heading, and text of the description form a meaningful sequence.

A layout table is used to position the elements of the page. The links in the navigation bar are split into different cells in the leftmost column.

<table>
<tr>
	<td><a href="#">Link 1</a></td>
	<td rowspan="20"><img src="img.png" alt="Museum Picture"></td>
	<td rowspan="6"><img src="placard.png" alt="Placard text"></td> 
</tr> 
<tr>
	<td><a href="#">Link 2</a></td>
</tr>
<tr>
	<td><a href="#">Link 3</a></td>
</tr>
<tr>
	<td><a href="#">Link 4</a></td>
</tr>
<tr>
	<td><a href="#">Link 5</a></td>
</tr>
<tr>
	<td><a href="#">Link 6</a></td>
</tr>
<tr>
	<td><a href="#">Link 7</a></td>
	<td rowspan="2"><h2>Image Heading</h2></td> 
</tr> 
<tr>
	<td><a href="#">Link 8</a></td>
</tr>
<tr>
	<td><a href="#">Link 9</a></td>
	<td rowspan="12">Description of the image</td> 
</tr> 
<tr>
	<td><a href="#">Link 10</a></td>
</tr>
 ...
<tr>
	<td><a href="#">Link 20</a></td>
</tr>
</table>

The reading order from this example would be:

  • Link 1

  • Image

  • Placard Text

  • Link 2

  • Link 3

  • Link 4

  • Link 5

  • Link 6

  • Link 7

  • Image Heading

  • Link 8

  • Link 9

  • Link 10

  • ...

  • Link 20

Because the navigation bar links are interleaved with the content describing the image, screen readers cannot present the content in a meaningful sequence corresponding to the sequence presented visually.

Resources

No resources available for this technique.

Tests

Procedure
  1. Linearize the content in either of the following ways:

    • Present the content in source code order

    • Remove the table markup from around the content

  2. Check that the linear reading order matches any meaningful sequence conveyed through presentation.

Expected Results
  • If check #2 is false, then this failure condition applies and the content fails this success criterion.


F50: Failure of SC 2.2.2 due to a script that causes a blink effect without a mechanism to stop the blinking at 3 seconds or less

Applicability

Technologies that support script-controlled blinking of content.

This technique is referenced from:

Description

Scripts can be used to blink content by toggling the content's visibility on and off at regular intervals. It is a failure for the script not to include a mechanism to stop the blinking at 3 seconds or earlier. See Using scripts to control blinking and stop it in three seconds or less for information about how to modify the technique to stop the blinking.

Examples

Failure Example 1

The following example uses script to blink content, but the blink continues indefinitely rather than stopping after three seconds.

...
<script type="text/javascript">
<!--
// blink "on" state
function show()
{
	if (document.getElementById)
	document.getElementById("blink1").style.visibility = "visible";
	settime-out("hide()", 450);
}
// blink "off" state
function hide()
{
	if (document.getElementById)
	document.getElementById("blink1").style.visibility = "hidden";
	settime-out("show()", 450);
}
// kick it off
show();
//-->
</script>
...
<span id="blink1">This content will blink</span>

Tests

Procedure

For each instance of blinking content:

  1. Determine if the blinking stops in 3 seconds or less.

Expected Results

If #1 is false, then the content fails the success criterion.


F52: Failure of SC 3.2.1 due to opening a new window as soon as a new page is loaded without prior warning

Applicability

Applies when scripting is used to open new windows.

This technique is referenced from:

Description

Some Web sites open a new window when a page is loaded, to advertise a product or service. The objective of this technique is to ensure that pages do not disorient users by opening up one or more new windows as soon as a page is loaded. Unless instructions that describe the behavior are provided before the request to open the new page is made, opening a new window as soon as a new page is loaded is a failure condition for this success criterion.

Examples

Note: There are multiple methods by which this failure may be triggered. Two common examples that are supported differently in various versions of user agents are listed as examples below.

Failure Example 1:

The following example is commonly used in HTML 4.01 to open new windows when pages are loaded.

window.onload = showAdvertisement;
 function showAdvertisement()
 {
  window.open('advert.html', '_blank', 'height=200,width=150');
 }
Failure Example 2:

The following example commonly used in XHTML to open new windows when pages are loaded.

if (window.addEventListener) { 
    window.addEventListener("load", showAdvertisement, true);
}
if (window.attachEvent) {
    window.attachEvent("onload", showAdvertisement);
}
function showAdvertisement()
{
window.open('noscript.html', '_blank', 'height=200,width=150');
}

Resources

Tests

Procedure
  1. load a new page

  2. check to see whether a new window has been opened as a result of loading the new page

Expected Results
  • If step 2 is true, then this failure condition applies and content fails the success criterion.


F54: Failure of SC 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function

Applicability

Technologies that have event handlers specific to pointing devices.

User Agent and Assistive Technology Support Notes

  • None listed.

This technique is referenced from:

Description

When pointing device-specific event handlers are the only mechanism available to invoke a function of the content, users with no vision (who cannot use devices such as mice that require eye-hand coordination) as well as users who must use alternate keyboards or input devices that act as keyboard emulators will be unable to access the function of the content.

Examples

Failure Example 1

The following example is of an image that responds to a mouse click to go to another page. This is a failure because the keyboard cannot be used to move to the next page. <p><img onmousedown="nextPage();" src="nextarrow.gif" alt="Go to next page"></p>

Resources

Tests

Procedure
  1. Check to see whether pointing-device-specific event handlers are the only means to invoke scripting functions.

Expected Results
  • If any are found, then this failure condition applies and content fails the success criterion.


F55: Failure of SC 2.1.1 due to using script to remove focus when focus is received

Applicability

Applies to all content that supports script.

User Agent and Assistive Technology Support Notes

  • None listed.

This technique is referenced from:

Description

Content that normally receives focus when the content is accessed by keyboard may have this focus removed by scripting. While this is done to remove an undesired visual focus indicator, it removes the keyboard focus completely. This typically means the content can only be accessed by a pointer device, such as a mouse.

Examples

Failure Example 1
<input type="submit" onFocus="this.blur();"> 
Failure Example 2
<a onFocus="this.blur()" href="Page.html"><img src="myImage.gif"></a> 
Failure Example 3
<a href="link.html" onfocus="if(this.blur)this.blur();">Link Phrase</a> 

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Use the keyboard to verify that you can get to all interactive elements using the keyboard.

  2. Check that when focus is placed on each element, focus remains there until user moves it.

Expected Results
  • If #2 is false then this failure condition applies and content fails the success criterion.


F57: Failure of SC 4.2.1 and 4.2.3 caused by defaulting to non-conforming version as a result of content negotiation

Applicability

Sites that use content negotiation to serve alternate formats of the same content.

This technique is referenced from:

Description

Content negotiation allows Web servers to offer user agents a choice of several versions of the content. A user agent can specify the content formats it can accept. If the user agent does not support content negotiation or does not support any of the formats available, the server is left with only one option - to deliver a default version. If the default version does not conform to WCAG, users may not be able to access the content and may have no means to obtain the WCAG conforming version.

Examples

  • A Web site contains some content that is implemented in a format that does not support conforming to all WCAG requirements at the targeted level. The site provides conforming versions, however, and uses content negotiation with user agents to determine which version to serve. If the user agent does not support content negotiation or does not indicate that it supports any of the offered formats, the server defaults to the nonconforming version of the content.

Resources

Tests

Procedure

On a Web site that uses content negotiation to serve multiple versions of the same content, one that does not conform to WCAG and others that do conform to WCAG:

  1. Turn off content negotiation in the browser by removing the Accept HTTP header or set the Accept header to "*/*".

  2. Determine if the conforming version of the content is delivered.

Expected Results
  • If #2 is false, the site fails the success criterion.


F58: Failure of SC 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out

Applicability

  • Any server-side scripting language

  • Content does not meet the exceptions in the success criterion for permitted time-outs.

This technique is referenced from:

User Agent and Assistive Technology Support Notes

The Refresh header is not defined in HTTP/1.1 or HTTP/1.0, but it is widely supported by browsers (tested in Firefox 1.0 and IE 6 on Windows).

Description

Server-side scripting languages allow developers to set the non-standard HTTP header "Refresh" with a time-out (in seconds) and a URL to which the browser is redirected after the specified time-out. If the time interval is too short, people who are blind will not have enough time to make their screen readers read the page before the page refreshes unexpectedly and causes the screen reader to begin reading at the top. Sighted users may also be disoriented by the unexpected refresh.

The HTTP header that is set is Refresh: {time in seconds}; url={URI of new location}. It is also possible to omit the URL and obtain a periodically refreshing page, which causes the same problem. The HTTP header that is set is Refresh: {time in seconds}.

Examples

Failure Example 1

The following example is a failure because a timed server-side redirect is implemented in Java Servlets or JavaServer Pages (JSP).

public void doGet (HttpServletRequest request, HttpServletResponse response)
      throws IOException, ServletException {
        response.setContentType("text/html");
	PrintWriter out = response.getWriter();
	response.setHeader("Refresh", "10; URL=TargetPage.html");
	out.println("<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"
	 \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">");
	out.println("<html><head><title>Redirect</title></head><body>");
	out.println("<p>This page will redirect you in 10 seconds.</p>");
	out.println("</body></html>");
  }
Failure Example 2

The following example is a failure because a timed server-side redirect is implemented in Active Server Pages (ASP) with VBScript.

 <% @Language = "VBScript" %>
 <% option explicit 
 Response.Clear
 Response.AddHeader "Refresh", "5; URL=TargetPage.htm"
 %><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
 …
 <!--HTML code for content that is shown before the redirect is triggered-->
 

Resources

Tests

Procedure
  1. When a Web unit is rendered, check to see if it automatically redirects to another page after some period of time without the user taking any action.

Expected Results
  • If such a redirect is found then this failure condition applies and content fails the success criterion.


F59: Failure of SC 4.1.2 due to using script to make div or span a user interface control in HTML

Applicability

HTML and scripting

User Agent and Assistive Technology Support Notes

This technique is referenced from:

Description

This failure demonstrates how using generic HTML elements to create user interface controls can make the controls inaccessible to assistive technology. Assistive technologies rely on knowledge of the role and current state of a component in order to provide that information to the user. Many HTML elements have well defined roles, such as links, buttons, text fields, etc. Generic elements such as div and span do not have any predefined roles. When these generic elements are used to create user interface controls in HTML the assistive technology may not have the necessary information to describe and interact with the control.

See the resources section below for links to specifications which describe mechanisms to provide the necessary role and state information to create fully accessible user interface controls.

Examples

Example 1

The following example fails because it creates a checkbox using a span and an image.

  <p> 
  <span  onclick="toggleCheckbox('chkbox')"> 
  <img src="unchecked.gif"  id="chkbox" alt=""> Include Signature 
  </span> 
  </p>
Example 2

Here is the scripting code which changes the image source when the span is clicked with the mouse.

 
  var CHECKED = "check.gif"; 
  var UNCHECKED = "unchecked.gif"; 
  function toggleCheckbox(imgId) { 
  var theImg = document.getElementById(imgId); 
  if ( theImg.src.lastIndexOf(CHECKED)!= -1 ) { 
  theImg.src = UNCHECKED; 
  // additional code to implement unchecked action 
  } 
  else { 
  theImg.src = CHECKED; 
  // additional code to implement checked action 
  } 
  } 

A checkbox created in this manner will not work with assistive technology since there is no information that identifies it as a checkbox. In addition, this example is also not operable from the keyboard and would fail guideline 2.1.

Resources

Tests

Procedure
  1. Examine the source code for elements which have event handlers assigned within the markup or via scripting.

  2. If those elements are acting as user interface controls, check that the role of the control is defined.

Expected Results

If check #2 is false and the created user interface control does not have role information, this failure condition applies.


F60: Failure of SC 3.2.5 due to launching a new window when a user enters text into an input field

Applicability

General

This technique is referenced from:

Description

This document describes a failure that occurs when a new window is created in response to a user filling in a text field for other than error reporting.

Examples

Failure Example 1:

This is a deprecated example showing a failure: A user is filling in his mailing address. When he fills in his postal code, a new window opens containing advertisements for services available in his city.

Example 2:

This example is acceptable: A user is filling in his mailing address in a form. When he fills in the postal code field, a script runs to validate that it is a valid postal code. If the value is not valid, a window opens with instructions on how to fill in the field.

Resources

Tests

Procedure
  1. Find all text input form fields

  2. Change the value in each form field

  3. Check if new windows open

  4. For any new windows that open, check if they contain an error message and a button that closes the window returning focus to the initiating form element.

Expected Results
  • If #3 is true and #4 is false then failure condition applies and the content fails this success criterion.


F61: Failure of SC 3.2.5 due to complete change of main content through an automatic update that the user cannot disable from within the content

Applicability

General

This technique is referenced from:

Description

This document describes a failure that occurs when the content filling the user's entire viewport is automatically updated, and the content does not contain options for disabling this behavior.

Examples

Failure Example 1:

A news site automatically refreshes itself to ensure that it has the newest headlines. There is no option to disable this behavior.

Failure Example 2:

A slideshow fills the entire viewport and advances to the next slide automatically. There is no stop button.

Resources

(none currently listed)

Tests

Procedure
  1. open the content

  2. leave the content open for 24 hours

  3. check if the content changed

  4. check if there are settings within the content to disable automatic changes

Expected Results
  1. If both 3 and 4 are true, then this failure condition applies and the content fails this success criterion.


F62: Failure of SC 4.1.1 due to insufficient information in DOM to determine specific relationships in XML

Applicability

Applies to the Document Object Model (DOM) for XML.

This technique is referenced from:

Description

The objective of this technique is to ensure that Web units can be interpreted consistently by user agents, including assistive technology. If specific relationships in a Web unit are ambiguous, different user agents, including assistive technologies, could present different information to their users. Users of assistive technology, for example, may have different information presented to them than users of other mainstream user agents. Some elements and attributes in markup languages are required to have unique values, and if this requirement is not honored, the result can be irregular or not uniquely resolvable content.

Examples

Failure Example 1
  • An id attribute value that is not unique.

  • An SVG document uses id attributes on title elements (for alternative text) in order to reuse in other locations in the document. However, one of the title elements has an id that is also used elsewhere in the document, so the document is ambiguous.

  • A DAISY document uses the imgref attribute on the caption element to link captions with images. However, imgref attribute value does not refer to the id attribute of the img element to which it belongs, so the user agent cannot find the caption for that image.

Resources

(none currently listed)

Tests

Procedure
  1. Check that all id values within the document (as defined by the schema) are unique.

  2. Check that elements or attributes that refer to unique identifiers inside the same document have a corresponding id value.

Note that for XML document types defined by a DTD, this refers to attributes of type ID, IDREF or IDREFS. For XML document types defined by a W3C XML Schema, this refers to elements or attributes of type ID, IDREF or IDREFS. (For compatibility, the types ID, IDREF and IDREFS should only be used on attributes, but using them for elements is possible, according to XML Schema Part 2: Datatypes Second Edition.) For other schema languages, check the corresponding mechanisms for specifying IDs and references to IDs.

Expected Results
  • If #1 or #2 is false, then this failure condition applies and the content fails the success criterion.


2. Client-side Scripting Techniques


SCR1: Allowing the user to extend the default time-out

Applicability

Time-outs that are controlled by client-side scripting.

This technique is referenced from:

Description

The objective of this technique is to allow user to extend the default time-out by providing a mechanism to extend the time when scripts provide functionality that has default time-outs. In order to allow the user to request a longer than default time-out period, the script can provide a form (for example) allowing the user to enter a larger default time-out value. Making this available as a preference setting allows users to indicate their requirements in advance. If warning the user a time-out is about to expire (see Providing a script that warns the user a time-out is about to expire), this form can be made available from the warning dialog.

Examples

  • A Web unit contains current stock market statistics and is set to refresh periodically. When the user is warned prior to refreshing the first time, the user is provided with an option to extend the time period between refreshes.

  • In an online chess game, each player is given a time limit for completing each move. When the player is warned that time is almost up for this move, the user is provided with an option to increase the time.

Resources

Tests

Procedure
  1. On a Web unit that uses scripts to enforce a time limit, wait until the time-out has expired.

  2. Determine if an option was provided to extend the time-out.

Expected Results
  • #2 is true and more time is provided to complete the interaction.


SCR14: Using scripts to make nonessential alerts optional

Applicability

Scripting technologies which use scripting alerts for non-emergency communication.

This technique is referenced from:

User Agent and Assistive Technology Support Notes

This technique was tested successfully with JAWS 6.2

This technique was tested successfully with WindowEyes 5.5

This technique was tested successfully with HomePage Reader 3.04

Description

The objective of this technique is to display a dialog containing a message (alert) to the user. When the alert is displayed, it receives focus and the user must activate the OK button on the dialog to dismiss it. Since these alerts cause focus to change they may distract the user, especially when used for non-emergency information. Alerts for non-emergency purposes such as displaying a quote of the day, helpful usage tip, or count down to a particular event, are not presented unless the user enables them through an option provided in the Web unit.

This technique assigns a global JavaScript variable to store the user preference for displaying alerts. The default value is false. A wrapper function is created to check the value of this variable before displaying an alert. All calls to display an alert are made to this wrapper function rather than calling the alert() function directly. Early in the page, a button is provided for the user to enable the display of alerts on the page. This technique works on a visit by visit basis. Each time the page is loaded, alerts will be disabled and the user must manually enable them. Alternatively, the author could use cookies to store user preferences across sessions.

Examples

Example 1

The script below will display a quote in an alert box every ten seconds, if the user selects the "Turn Alerts On" button. The user can turn the quotes off again by choosing "Turn Alerts Off".

<script type="text/javascript">
var bDoAlerts = false;  // global variable which specifies whether to 
                                       // display alerts or not
/* function to enable/disable alerts.
 * param boolean bOn - true to enable alerts, false to disable them.
*/
function modifyAlerts(isEnabled) {
   bDoAlerts = isEnabled;
}
/* wrapper function for displaying alerts.  Checks the value of bDoAlerts
*and only calls the alert() function when bDoAlerts is true.
*/
function doAlert(aMessage) {
    if (bDoAlerts) {
       alert(aMessage);
    }
}
// example usage - a loop to display famous quotes.
var gCounter = -1;  // global to store counter
// quotes variable would be initialized with famous quotations
var quotes = new Array("quote 1", "quote 2", "quote 3", "quote 4", "quote 5");
function showQuotes() {
   if (++gCounter >= quotes.length) {
     gCounter = 0;
   }
   doAlert(quotes[gCounter]);
   setTimeout("showQuotes();", 10000);
}
showQuotes();
</script>

Within the body of the page, include a way to turn the alerts on and off. Below is one example:

<body>
<p>Press the button below to enable the display of famous quotes 
using an alert box<br />
<button id="enableBtn" type="button" onclick="modifyAlerts(true);">
Turn Alerts On</button><br />
<button id="disableBtn" type="button" onclick="modifyAlerts(false);">
Turn Alerts Off</button></p>

Here is a working example of this code: Demonstration of Alerts.

Tests

Procedure

For a Web unit that supports non-emergency interruptions using a JavaScript alert:

  1. Load the Web unit and verify that no non-emergency alerts are displayed.

  2. Verify there is a mechanism to activate the non-emergency alerts.

  3. Activate the non-emergency alerts and verify that the alerts are displayed.

Expected Results
  • For a Web unit that supports non-emergency interruptions using a JavaScript alert, checks 1, 2, and 3 above are true.


SCR16: Providing a script that warns the user a time-out is about to expire

Applicability

Time-outs exist that are controlled by script.

This technique is referenced from:

Description

The objective of this technique is to notify users that they are almost out of time to complete an interaction. When scripts provide functionality that has time-outs, the script can include functionality to warn the user of imminent time-outs and provide a mechanism to request more time. 20 seconds or more before the time-out occurs, the script provides a confirm dialog that states that a time-out is imminent and asks if the user needs more time. If the user answers "yes" then the time-out is reset. If the user answers "no" or does not respond, the time-out is allowed to expire.

This technique involves time-outs set with the window.setTimeout() method. If, for example, the time-out is set to expire in 60 seconds, you can set the time-out for 40 seconds and provide the confirm dialog. When the confirm dialog appears, a new time-out is set for the remaining 20 seconds. Upon expiry of the "grace period time-out" the action that would have been taken at the expiry of the 60 second time-out in the original design is taken.

Examples

Example 1

A page of stock market quotes uses script to refresh the page every five minutes in order to ensure the latest statistics remain available. 20 seconds before the five minute period expires, a confirm dialog appears asking if the user needs more time before the page refreshes. This allows the user to be aware of the impending refresh and to avoid it if desired.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"<url>http://www.w3.org/TR/html4/loose.dtd">http://www.w3.org/TR/html4/loose.dtd</title>">
<html lang="en">
<head>
<title>Stock Market Quotes</title>
<script type="text/javascript">
<!--
function timeControl() {
	// set timer for 4 min 40 sec, then ask user to confirm.
	setTimeout('userCheck()', 280000);
}
function userCheck() {
	// set page refresh for 20 sec
	var id=setTimeout('pageReload()', 20000);
	// If user selects "OK" the timer is reset 
	// else the page will refresh from the server.
	if (confirm("This page is set to refresh in 20 seconds. 
	Would you like more time?"))
	{
	clearTimeout(id);
	timeControl();
	}
}
function pageReload() {
	window.location.reload(true);
}
timeControl();
-->
</script>
</head>
<body>
<h1>Stock Market Quotes</h1>
...etc...
</body>
</html>

Tests

Procedure

On a Web unit that has a time-out controlled by a script:

  1. load the page and start a timer that is 20 seconds less than the time-out.

  2. when the timer expires, check that a confirmation dialog is displayed warning of the impending time-out.

Expected Results
  • #2 is true.


SCR18: Providing client-side validation and alert

Applicability

Content that validates user input.

This technique is referenced from:

Description

The objective of this technique is to validate user input as values are entered for each field, by means of client-side scripting. If errors are found, an alert dialog describes the nature of the error in text. Once the user dismisses the alert dialog, it is helpful if the script positions the keyboard focus on the field where the error occurred.

Examples

Example 1

The following script will check that a valid date has been entered in the form control.

<label for="date">Date:</label>
<input type="text" name="date" id="date" 
onchange="if(isNaN(Date.parse(this.value))) 
<pre>alert('This control is not a valid date. 
Please re-enter the value.');" /></pre>

Tests

Procedure

For form fields that require specific input:

  1. enter invalid data

  2. determine if an alert describing the error is provided.

Expected Results
  • #2 is true


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

Applicability

(X)HTML with support for scripting. This technique uses the try/catch construct of JavaScript 1.4.

User Agent and Assistive Technology Support Notes

This technique has been tested on Windows XP using JAWS 7.0 and WindowEyes 5.5 with both Firefox 1.5 and IE 6. This also works with Home Page Reader 3.04. Note that JavaScript must be enabled in the browser.

This technique is referenced from:

Description

The objective of this technique is to demonstrate how to correctly use an onchange event with a select element to update other elements on the Web unit. This technique will not cause a change of context. When there are one or more select elements on the Web unit, an onchange event on one, can update the options in another select element on the Web unit. All of the data required by the select elements is included within the Web unit.

It is important to note that the select item which is modified is after the trigger select element in the reading order of the Web unit. This ensures that assistive technologies will pick up the change and users will encounter the new data when the modified element receives focus. This technique relies on JavaScript support in the user agent.

Examples

Example 1

This example contains two select elements. When an item is selected in the first select, the choices in the other select are updated appropriately. The first select element contains a list of continents. The second select element will contain a partial list of countries located in the selected continent. There is an onchange event associated with the continent select. When the continent selection changes, the items in the country select are modified using JavaScript via the Document Object Model (DOM). All of the data required, the list of countries and continents, is included within the Web unit.

Overview of the code below

  • countryLists array variable which contains the list of countries for each continent in the trigger select element.

  • countryChange() function which is called by the onchange event of the continent select element.

  • The XHTML code to create the select elements in the body of the Web unit.

<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> 
  <head> 
    <meta http-equiv="content-type" content="text/xhtml; charset=utf-8" /> 
    <title>Dynamic Select Statements</title> 
<script type="text/javascript">
 //<![CDATA[ 
 // array of possible countries in the same order as they appear in the country selection list 
 var countryLists = new Array(4) 
 countryLists["empty"] = ["Select a Country"]; 
 countryLists["North America"] = ["Canada", "United States", "Mexico"]; 
 countryLists["South America"] = ["Brazil", "Argentina", "Chile", "Ecuador"]; 
 countryLists["Asia"] = ["Russia", "China", "Japan"]; 
 countryLists["Europe"]= ["Britain", "France", "Spain", "Germany"]; 
 /* CountryChange() is called from the onchange event of a select element. 
 * param selectObj - the select object which fired the on change event. 
 */ 
 function countryChange(selectObj) { 
 // get the index of the selected option 
 var idx = selectObj.selectedIndex; 
 // get the value of the selected option 
 var which = selectObj.options[idx].value; 
 // use the selected option value to retrieve the list of items from the coutnryLists array 
 cList = countryLists[which]; 
 // get the country select element via its known id 
 var cSelect = document.getElementById("country"); 
 // remove the current options from the country select 
 var len=cSelect.options.length; 
 while (cSelect.options.length > 0) { 
 cSelect.remove(0); 
 } 
 var newOption; 
 // create new options 
 for (var i=0; i<cList.length; i++) { 
 newOption = document.createElement("option"); 
 newOption.value = cList[i];  // assumes option string and value are the same 
 newOption.text=cList[i]; 
 // add the new option 
 try { 
 cSelect.add(newOption);  // this will fail in DOM browsers but is needed for IE 
 } 
 catch (e) { 
 cSelect.appendChild(newOption); 
 } 
 } 
 } 
//]]>
</script>
</head>
<body>
  <noscript>This page requires JavaScript be available and enabled to function properly</noscript>
  <h1>Dynamic Select Statements</h1>
  <label for="continent">Select Continent</label>
  <select id="continent" onchange="countryChange(this);">
    <option value="empty">Select a Continent</option>
    <option value="North America">North America</option>
    <option value="South America">South America</option>
    <option value="Asia">Asia</option>
    <option value="Europe">Europe</option>
  </select>
  <br/>
  <label for="country">Select a country</label>
  <select id="country">
    <option value="0">Select a country</option>
  </select>
</body>
 </html>

Here is a working example: Dynamic Select

Resources

(none currently listed)

Tests

Procedure
  1. Navigate to the trigger select element (in this example, the one to select continents) and change the value of the select.

  2. Navigate to the select element that is updated by the trigger (in this example, the one to select countries).

  3. Check that the matching option values are displayed in the other select element.

  4. Navigate to the trigger select element, navigate through the options but do not change the value.

  5. Check that the matching option values are still displayed in the associated element.

It is recommended that the select elements are tested with an assistive technology to verify that the changes to the associated element are recognized.

Expected Results
  • Step #3 and #5 are true.


SCR20: Using both keyboard and other device-specific functions

Applicability

Applies to all content that uses Script to implement functionality.

This technique is referenced from:

Description

The objective of this technique is to illustrate the use of both keyboard-specific and mouse-specific events with code that has a scripting function associated with an event. Using both keyboard-specific and mouse-specific events together ensures that content can be operated by a wide range of devices. For example, a script may perform the same action when a keypress is detected that is performed when a mouse button is clicked. This technique goes beyond the SC requirement for keyboard access by including not only keyboard access but access using other devices as well.

In JavaScript, commonly used event handlers include, onblur, onchange, onclick, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onload, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup, onreset, onselect, onsubmit, onunload. Some mouse-specific functions have a logical corresponding keyboard-specific function (such as 'onmouseover' and 'onfocus'). The keyboard event handler should be provided, that executes the same function as the mouse event handler.

The following table suggests keyboard event handlers to pair mouse event handlers.

Device Handler Correspondences
Use... ...with
mousedown keydown
mouseup keyup
click [1] keypress [2]
mouseover focus
mouseout blur

1 Although click is in principle a mouse event handler, most HTML user agents process this event when the control is activated, regardless of whether it was activated with the mouse or the keyboard. In practice, therefore, it is not necessary to duplicate this event. It is included here for completeness since non-HTML user agents do have this issue.

2 Since the keypress event handler reacts to any key, the event handler function should check first to ensure the Enter key was pressed before proceeding to handle the event. Otherwise, the event handler will run each time the user presses any key, even the tab key to leave the control, and this is usually not desirable.

Some mouse-specific functions (such as dblclick and mousemove) do not have a corresponding keyboard-specific function. This means that some functions may need to be implemented differently for each device (for example, including a series of buttons to execute, via keyboard, the equivalent mouse-specific functions implemented).

Examples

Example 1

In this example of an image link, the image is changed when the user positions the pointer over the image. To provide keyboard users with a similar experience, the image is also changed when the user tabs to it.

<a href="menu.php" onmouseover="swapImageOn('menu')" onfocus="swapImageOn('menu')" 
onmouseout="swapImageOff('menu')" onblur="swapImageOff('menu')"> 
<img id="menu" src="menu_off.gif" alt="Menu" /> 
</a>
Example 2

This example shows an image for which the keyboard can be used to activate the function. The mouse event onclick is duplicated by an appropriate keyboard event onkeypress. The tabindex attribute ensures that the keyboard will have a tab stop on the image. Note that in this example, the nextPage() function should check that the keyboard key pressed was Enter, otherwise it will respond to all keyboard actions while the image has focus, which is not the desired behavior.

<img onclick="nextPage();" onkeypress="nextPage();" tabindex="0" src="arrow.gif" 
alt="Go to next page"> 

Note: This example uses tabindex on an img element. Even though this is currently invalid, it is provided as a transitional technique to make this function work.

Resources

Tests

Procedure
  1. Find all interactive functionality

  2. Check that all interactive functionality can be accessed using the keyboard alone

Expected Results
  • #2 is true


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

Applicability

ECMAScript used inside HTML 4.x or XHTML 1.x

This technique is referenced from:

User Agent and Assistive Technology Support Notes

This example was successfully tested on Windows XP with IE 6 and Firefox 1.5.0.1 using both JAWS 7 and WindowEyes 5.5. This technique will not work with Home Page Reader. Note that when adding new content onto a page, the screen readers may not automatically speak the new content. In order to insure that new content is spoken, set focus to the new element or make certain that it is added below the current location and will be encountered as the user continues to traverse the page.

Description

The objective of this technique is to demonstrate how to use functions of the Document Object Model (DOM) to add content to a page instead of using document.write or object.innerHTML. The document.write() method does not work with XHTML when served with the correct MIME type (application/xhtml+xml), and the innerHTML property is not part of the DOM specification and thus should be avoided. If the DOM functions are used to add the content, user agents can access the DOM to retrieve the content. The createElement() function can be used to create elements within the DOM. The createTextNode() is used to create text associated with elements. The appendChild(), removeChild(), insertBefore() and replaceChild() functions are used to add and remove elements and nodes. Other DOM functions are used to assign attributes to the created elements.

Note: When adding focusable elements into the document, do not add tabindex attributes to explicitly set the tab order as this can cause problems when adding focusable elements into the middle of a document. Let the default tab order be assigned to the new element by not explicitly setting a tabindex attribute.

Examples

Example 1

This example demonstrates use of client-side scripting to validate a form. If errors are found appropriate error messages are displayed. The example uses the DOM functions to add error notification consisting of a title, a short paragraph explaining that an error has occurred, and a list of errors in an ordered list. The content of the title is written as a link so that it can be used to draw the user's attention to the error using the focus method. Each item in the list is also written as a link that places the focus onto the form field in error when the link is followed.

For simplicity, the example just validates two text fields, but can easily be extended to become a generic form handler. Client-side validation should not be the sole means of validation , and should be backed up with server-side validation. The benefit of client-side validation is that you can provide immediate feedback to the user to save them waiting for the errors to come back from the server, and it helps reduce unnecessary traffic to the server.

Here is the script that adds the event handlers to the form. If scripting is enabled, the validateNumbers() function will be called to perform client-side validation before the form is submitted to the server. If scripting is not enabled, the form will be immediately submitted to the server and validation will occur on the server.

 window.onload = initialise;
 function initialise()
 {
    // Ensure we're working with a relatively standards compliant user agent
    if (!document.getElementById || !document.createElement || !document.createTextNode)
        return;
    // Add an event handler for the number form
    var objForm = document.getElementById('numberform');
    objForm.onsubmit= function(){return validateNumbers(this);};
 }

Here is the validation function. Note the use of the createElement(), createTextNode(), and appendChild() DOM functions to create the error message elements.

function validateNumbers(objForm)
 {
   // Test whether fields are valid
   var bFirst = isNumber(document.getElementById('num1').value);
   var bSecond = isNumber(document.getElementById('num2').value);
   // If not valid, display errors
   if (!bFirst || !bSecond)
   {
      var objExisting = document.getElementById('validationerrors');
      var objNew = document.createElement('div');
      var objTitle = document.createElement('h2');
      var objParagraph = document.createElement('p');
      var objList = document.createElement('ol');
      var objAnchor = document.createElement('a');
      var strID = 'firsterror';
      var strError;
      // The heading element will contain a link so that screen readers
      // can use it to place focus - the desitination for the link is 
      // the first error contained in a list
      objAnchor.appendChild(document.createTextNode('Errors in Submission'));
      objAnchor.setAttribute('href', '#firsterror');
      objTitle.appendChild(objAnchor);
      objParagraph.appendChild(document.createTextNode('Please review the following'));
      objNew.setAttribute('id', 'validationerrors');
      objNew.appendChild(objTitle);
      objNew.appendChild(objParagraph);
      // Add each error found to the list of errors
      if (!bFirst)
      {
         strError = 'Please provide a numeric value for the first number';
         objList.appendChild(addError(strError, '#num1', objForm, strID));
         strID = '';
      }
      if (!bSecond)
      {
         strError = 'Please provide a numeric value for the second number';
         objList.appendChild(addError(strError, '#num2', objForm, strID));
         strID = '';
      }
      // Add the list to the error information
      objNew.appendChild(objList);
      // If there were existing errors, replace them with the new lot,
      // otherwise add the new errors to the start of the form
      if (objExisting)
         objExisting.parentNode.replaceChild(objNew, objExisting);
      else
      {
         var objPosition = objForm.firstChild;
         objForm.insertBefore(objNew, objPosition);
      }
      // Place focus on the anchor in the heading to alert
      // screen readers that the submission is in error
      objAnchor.focus();
      // Do not submit the form
      objForm.submitAllowed = false;
      return false;
   }
 }
 // Function to validate a number
 function isNumber(strValue)
 {
   return (!isNaN(strValue) && strValue.replace(/^\s+|\s+$/, '') !== '');
 } 

Below are the helper functions to create the error message and to set focus to the associated form field.

  // Function to create a list item containing a link describing the error
 // that points to the appropriate form field
 function addError(strError, strFragment, objForm, strID)
 {
   var objAnchor = document.createElement('a');
   var objListItem = document.createElement('li');
   objAnchor.appendChild(document.createTextNode(strError));
   objAnchor.setAttribute('href', strFragment);
   objAnchor.onclick = function(event){return focusFormField(this, event, objForm);};
   objAnchor.onkeypress = function(event){return focusFormField(this, event, objForm);};
   // If strID has a value, this is the first error in the list
   if (strID.length > 0)
      objAnchor.setAttribute('id', strID);
      objListItem.appendChild(objAnchor);
      return objListItem;
   }
 }

 // Function to place focus to the form field in error
 function focusFormField(objAnchor, objEvent, objForm)
 {
   // Allow keyboard navigation over links
   if (objEvent && objEvent.type == 'keypress')
      if (objEvent.keyCode != 13 && objEvent.keyCode != 32)
         return true;
   // set focus to the form control
   var strFormField = objAnchor.href.match(/[^#]\w*$/);
   objForm[strFormField].focus();
   return false;
 }

Here is the HTML for the example form.

<h1>Form Validation</h1>
 <form id="numberform" method="post" action="form.php">
 <fieldset>
 <legend>Numeric Fields</legend>
 <p>
 <label for="num1">Enter first number</label> 
 <input type="text" size="20" name="num1" id="num1">
 </p>
 <p>
 <label for="num2">Enter second number</label> 
 <input type="text" size="20" name="num2" id="num2">
 </p>
 </fieldset>
 <p>
 <input type="submit" name="submit" value="Submit Form">
 </p>
 </form>

Note that the sample form will not submit. This example only demonstrates the creation of error messages when client side validation fails.

Resources

(none currently listed)

Tests

Procedure

For pages that dynamically create new content:

  1. Examine the source code and check that the new content is not created using document.write(), innerHTML, outerHTML, innerText or outerText.

Expected Results
  • Check #1 is true.


SCR22: Using scripts to control blinking and stop it in three seconds or less

Applicability

Technologies that support script-controlled blinking of content.

This technique is referenced from:

Description

The objective of this technique is to control blinking with script so it can be set to stop in less than three seconds by the script. Script is used to start the blinking effect of content, control the toggle between visible and hidden states, and also stop the effect at three seconds or less. The setTimeout() function can be used to toggle blinking content between visible and hidden states, and stop when the number of iterations by the time between them adds up to nearly three seconds.

Examples

Example 1

This example uses Javascript to control blinking of some (X)HTML content. Javascript creates the blinking effect by changing the visibility status of the content. It controls the start of the effect and stops it within three seconds.

...
<div id="blink1" class="highlight">New item!</div>
<script type="text/javascript">
<!--
// blink "on" state
function show()
{
	if (document.getElementById)
	document.getElementById("blink1").style.visibility = "visible";
}
// blink "off" state
function hide()
{
	if (document.getElementById)
	document.getElementById("blink1").style.visibility = "hidden";
}
// toggle "on" and "off" states every 450 ms to achieve a blink effect
// end after 2700 ms (less than three seconds)
for(var i=900; i < 2700; i=i+900)
{
	setTimeout("hide()",i);
	setTimeout("show()",i+450);
}
-->
</script>
...

Tests

Procedure

For each instance of blinking content:

  1. Start a timer for 3 seconds at the start of the blink effect.

  2. When the timer expires, determine if the blinking has stopped.

Expected Results
  • For each instance of blinking content, #2 is true.


SCR24: Using script to open a new window

Applicability

HTML 4.01 and XHTML 1.0

This technique is referenced from:

Description

The objective of this technique is to avoid confusion that may be caused by the appearance of new windows that were not requested by the user. Suddenly opening new windows can disorientate or be missed completely by some users. If the document type does not allow the target attribute (it does not exist in HTML 4.01 Strict or XHTML 1.0 Strict) or if the developer prefers not to use it, new windows can be opened with ECMAScript. The example below demonstrates how to open new windows with script: it adds an event handler to a link (a element) and warns the user that the content will open in a new window.

Examples

Example 1:

Markup:

The script is included in the head of the document, and the link has an id that can be used as a hook by the script.

<script type="text/javascript" src="popup.js"></script>
…
<a href="help.html" id="newwin">Show Help</a

Script:

 
// Use traditional event model whilst support for event registration
// amongst browsers is poor.
window.onload = addHandlers;

function addHandlers()
{
  var objAnchor = document.getElementById('newwin');

  if (objAnchor)
  {
    objAnchor.firstChild.data = objAnchor.firstChild.data + ' (opens in a new window)';
    objAnchor.onclick = function(event){return launchWindow(this, event);}
    // UAAG requires that user agents handle events in a device-independent manner
    // but only some browsers do this, so add keyboard event to be sure
    objAnchor.onkeypress = function(event){return launchWindow(this, event);}
  }
}

function launchWindow(objAnchor, objEvent)
{
  var iKeyCode, bSuccess=false;

  // If the event is from a keyboard, we only want to open the
  // new window if the user requested the link (return or space)
  if (objEvent && objEvent.type == 'keypress')
  {
    if (objEvent.keyCode)
      iKeyCode = objEvent.keyCode;
    else if (objEvent.which)
      iKeyCode = objEvent.which;

    // If not carriage return or space, return true so that the user agent
    // continues to process the action
    if (iKeyCode != 13 && iKeyCode != 32)
      return true;
  }

  bSuccess = window.open(objAnchor.href);

  // If the window did not open, allow the browser to continue the default
  // action of opening in the same window
  if (!bSuccess)
    return true;

  // The window was opened, so stop the browser processing further
  return false;
}

Resources

Tests

Procedure
  1. Activate each link in the document to check if it opens a new window.

  2. For each link that opens a new window, check that it uses script.

Expected Results
  • #2 is true.


3. CSS Techniques


C6: Positioning content based on structural markup

Applicability

All technologies that support CSS

This technique is referenced from:

Description

The objective of this technique is to demonstrate how visual appearance may be enhanced via style sheets while still maintaining a meaningful presentation when style sheets are not applied. Using the positioning properties of CSS2, content may be displayed at any position on the user's viewport. Using structural elements ensures that the meaning of the content can still be determined when styling is not available.

Examples

Example 1

In this example structural markup (definition lists) have been applied to the content. CSS has been used to style the content into columnar form. Each class absolutely positions the content into columns and the margins have been set to 0 to override the default behavior of user agents to display HTML definition lists with the DD element indented.

Here is the content to be displayed:

 <div class="box">
  <dl>
    <dt class="menu1">Products</dt>
    <dd class="item1">Telephones</dd>
    <dd class="item2">Computers</dd>
    <dd class="item3">Portable MP3 Players</dd>
    <dt class="menu2">Locations</dt>
    <dd class="item4">Idaho</dd>
    <dd class="item5">Wisconsin</dd>
    </dt>
  </dl>
 </div>
Example 2

Here is the CSS which positions and styles the above elements:

 .item1 {
   left: 0em;
   margin: 0px;
   position: absolute;
   top: 7em;
 }
 .item2 {
   left: 0em;
   margin: 0px;
   position: absolute;
   top: 8em;
 }
 .item3 {
   left: 0em;
   margin: 0px;
   position: absolute;
   top: 9em;
 }
 .item4 {
   left: 14em;
   margin: 0px;
   position: absolute;
   top: 7em;
 }
 .item5 {
   left: 14em;
   margin: 0px;
   position: absolute;
   top: 8em;
 }
 .menu1 {
   background-color: #FFFFFF;
   color: #FF0000;
   font-family: sans-serif;
   font-size: 120%;
   left: 0em;
   margin: 0px;
   position: absolute;
   top: 3em;
 }
 .menu2 {
   background-color: #FFFFFF;
   color: #FF0000;
   font-family: sans-serif;
   font-size: 120%;
   left: 10em;
   margin: 0px;
   position: absolute;
   top: 3em;
 }
 #box {
   left: 5em;
   position: absolute;
   top: 5em;
 }

Example 3

When style sheets are applied, the data are displayed in two columns of "Products" and "Locations." When the style sheets are not applied, the text appears in a definition list which maintains the structure and reading order.

Resources

Tests

Procedure

For content which uses CSS for positioning

  1. Remove the style information from the document or turn off use of style sheets in the user agent.

  2. Check that the structural relations and the meaning of the content are preserved.

Expected Results
  • Check #2 is true.


C9: Using CSS to include decorative images

Applicability

Any technology that can use CSS to include images.

This technique is referenced from:

Description

The objective of this technique is to provide a mechanism to add purely decorative images and images used for visual formatting to Web content without requiring additional markup within the content. This makes it possible for assistive technologies to ignore the non-text content. Some user agents can ignore or turn off CSS at the user's request, so that background images included with CSS simply "disappear" and do not interfere with display settings such as enlarged fonts or high contrast settings.

Background images can be included with the following CSS properties:

  • background,

  • background-image,

  • content, combined with the :before and :after pseudo-elements,

  • list-style-image.

Note: This technique is not appropriate for any image that conveys information or provides functionality, or for any image primarily intended to create a specific sensory experience.

Examples

Example 1: Background image for an HTML page

The stylesheet for a Web page specifies a background image for the whole page.

 …
<style type="text/css">
body { background: #ffe url('/images/home-bg.jpg') repeat; }
</style>
</head>
<body>
…
Example 2: Background image with CSS for image rollovers

The stylesheet for a Web page uses the CSS background property to create a decorative rollover effects when a user hovers the mouse pointer over a link.

a:hover { background: #ffe url('/images/hover.gif') repeat; color: #000;
   text-decoration: none;
}
Example 3: Background images with CSS to create rounded corners on tabs or other elements

The styleseet for a Web page uses the CSS background property to create rounded corners on elements.

…
<style type="text/css">
 div#theComments { width:600px; }
 div.aComment { background: url('images/middle.gif') repeat-y left top; 
 margin:0 0 30px 0; }
 div.aComment blockquote { background: url('images/top.gif') no-repeat left top; 
 margin:0; padding:8px 16px; }
 div.aComment div.submitter { background:#fff url('images/bottom.gif') no-repeat left top; 
 margin:0; padding-top:30px; }
</style>
</head>
<body>
<div id="theComments">
 <div class="aComment">
  <blockquote>
   <p>Hi John, I really like this technique and I'm gonna use it on my own website!</p>
  </blockquote>
  <div class="submitter">
   <p class="cite"><a href="http://example.com/">anonymous coward</a> from Elbonia</p>
  </div>
 </div>
 <div class="aComment">
 …
 </div>
</div>
…

Resources

Tests

Procedure
  1. Check for the presence of decorative images

  2. Check that they are included with CSS

Expected Results
  • If #1 is true, then #2 is true.


C7: Supplementing link text with hidden text

Applicability

All technologies that support CSS .

This technique is referenced from:

Description

The objective of this technique is to supplement the link text by adding additional text that describes the unique function of the link but styling the additional text so that it is not rendered on the screen by user agents that support CSS. When information in the surrounding context is needed to interpret the displayed link text, this technique provides a complete description of the link unique function while permitting the less complete text to be displayed.

This technique works by creating a CSS selector to target text that is to be hidden. The rule-set for the selector places the text to be hidden in a 1-pixel box with overflow hidden, and positions the text outside of the viewport. This ensures the text does not display on screen but remains accessible to assistive technologies such as screen readers and braille displays. Note that the technique does not use visibility:hidden or display:none properties, since these can have the unintentional effect of hiding the text from assistive technology in addition to preventing on-screen display.

Examples

The following examples use the CSS selector and rule-set below:

a span { height: 1px; width: 1px; position: absolute; overflow: hidden; top: -10px; }
Example 1

This example describes a news site that has a series of short synopsis of stories followed by a link that says "full story". Hidden link text describes the purpose of the link.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> 
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> 
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=UTF-8" /> 
<link href="access.css" rel="stylesheet" type="text/css" />
<title>Hidden Link Text</title>
</head>
<body> 
<p>Washington has announced plans to stimulate economic growth.
  <a href="#"> <span>Washington stimulates economic growth </span>
  Full Story</a></p>
</body>
</html>
Example 2

This example describes a resource that has electronic books in different formats. The title of each book is followed by links that say "HTML" and "PDF." Hidden text describes the purpose of each link.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> 
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> 
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=UTF-8" /> 
<link href="access.css" rel="stylesheet" type="text/css" />
<title>Hidden Link Text </title>
</head>
<body>
<dl>
<dt>Winnie the Pooh </dt>
   <dd><a href="winnie_the_pooh.html">
      <span>Winnie the Pooh </span>HTML</a></dd>
   <dd><a href="winnie_the_pooh.pdf">
         <span>Winnie the Pooh </span>PDF</a></dd>
<dt>War and Peace</dt>
    <dd><a href="war_and_peace.html">
      <span>War and Peace </span>HTML</a></dd> 
    <dd><a href="war_and_peace.pdf">
      <span>War and Peace </span>PDF</a></dd>
</dl>
</body>
</html>

Resources

No resources available for this technique.

Tests

Procedure

For each anchor element using this technique:

  1. Check that an element has been defined that confines its display to a pixel and positions text outside the display with overflow hidden

  2. Check that the element of that class is included in the content of the anchor

  3. Check that the combined content of the anchor describes the purpose of the link

Expected Results
  • All checks above are true.


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

Applicability

All technologies that support CSS.

This technique is referenced from:

Description

The objective of this technique is to demonstrate how the visual appearance of spacing in text may be enhanced via style sheets while still maintaining meaningful text sequencing. The CSS letter-spacing property helps developers control the amount of white space between characters. This is recommended over adding blank characters to control the spacing, since the blank characters can change the meaning and pronunciation of the word.

Examples

Example 1: Separating characters in a word

The following CSS would add the equivalent of a space between each character in a level-2 heading:

h2
{
	letter-spacing: 1em;
}

So for the markup:

<h2>Museum</h2>

the rendered result might look something like:

M u s e u m

Resources

Tests

Procedure

For each word that appears to have non-standard spacing between characters:

  1. Check whether the CSS letter-spacing property was used to control spacing.

Expected Results
  • Check #1 is true.


4. General Techniques


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

Applicability

All technology that contains links

This technique is referenced from:

Description

The objective of this technique is to provide a mechanism to bypass blocks of material that are repeated on multiple Web units. The first interactive item in the Web unit is a link to the beginning of the main content. Activating the link sets focus beyond the other content to the main content.

Examples

Example 1: An online newspaper

An on-line newspaper contains many sections of information: a search function, a corporate banner, sidebars, minor stories, how to contact the newspaper, etc. The lead story is located in the middle of the page. The first link that the user reaches when tabbing through the page is titled "Skip to Lead Story". Activating the link moves visual focus to the story. Pressing tab again takes the user to the first link in the main story.

Example 2: A "Skip to main content" link

A Web page includes a variety of navigation techniques on each page: a bread crumb trail, a search tool, a site map, and a list of related resources. The first link on the page is titled "Skip to Main Content". A user activates the link to skip over the navigation tools.

Resources

(none currently listed)

Tests

Procedure
  1. Check that a link is the first focusable control on the Web unit.

  2. Check that the description of the link communicates that it links to the main content.

  3. Check that activating the link moves the focus to the main content.

  4. Check that after activating the link, the keyboard focus has moved to the main content

Expected Results
  • All checks above are true.


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

Applicability

Any technology that includes moving or scrolling content.

This technique is referenced from:

Description

The objective of this technique is to provide a way to pause movement or scrolling of content. If the user needs to pause the movement, to reduce distraction or to have time to read it, they can do so, and then restart it as needed. This mechanism can be provided either through interactive controls that conform to WCAG or through keyboard shortcuts. If keyboard shortcuts are used, they are documented.

Examples

  • A site contains a scrolling news banner at the top of the page. Users who need more time to read it can press the Escape key to pause the scrolling. Pressing Escape again restarts it.

  • A Web page contains a link labeled "How to tie a shoe" which links to a Flash animation. Text immediately preceding the link informs the user that pressing the spacebar will pause the animation and restart it again.

Tests

Procedure

On a page with moving or scrolling content,

  1. Use the mechanism provided in the Web unit or by the user agent to pause the moving or scrolling content.

  2. Check that the moving or scrolling has stopped and does not restart by itself.

  3. Use the mechanism provided to restart the moving content.

  4. Check that the movement or scrolling has resumed from the point where it was stopped.

Expected Results
  • #2 and #4 are true.


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

Applicability

This technique applies to any technologies or methods supporting the implementation of an activity which does not require timed interaction for its functionality.

This technique is referenced from:

Description

The objective of this technique is to provide users with all the time they need to complete an activity. This technique involves providing a specified activity which does not require timed interaction. Users are allowed as much time as they need to interact with the activity.

Examples

  • An interactive exam for a course provides all questions on one Web unit. Users can take as much time as they need to complete it.

  • In an interactive game, users can take as much time as they like on their turn instead of having to complete their move within a limited amount of time.

  • In an online auction, each bidder can submit only one bid rather than submitting multiple competitive bids based on timing. The bidding is open for a full day, providing enough time for anyone to complete the simple bid form. Once bidding is closed, the best bid wins.

Resources

Tests

Procedure
  1. Determine if any timed interactions are present.

Expected Results
  • #1 is false.


G7: Associating a title with a Web page

Applicability

All technologies

This technique is referenced from:

Description

The objective of this technique is to ensure that all Web pages have titles associated with them that define in a simple phrase the purpose of the Web page. This helps users to orient themselves quickly within a set of Web pages without having to search for orientation information in the content of the Web pages themselves.

Examples

Example 1: Web Content

The title of Web Content Accessibility Guidelines 2.0 is "Web Content Accessibility Guidelines 2.0".

  • The introduction has the title "Introduction

  • The main body has the title "WCAG 2.0 Guidelines"

  • Appendix A has the title "Glossary"

  • Appendix B has the title "WCAG 2.0 Checklist"

  • Appendix C has the title "Acknowledgements"

  • Appendix D has the title "The differences between WCAG 1.0 and WCAG 2.0"

  • Appendix E has the title "References"

Example 2: An audio file

A podcast is associated with the title "Today's Tech Tips" by setting the id3 property of the .mp3 file.

Example 3: A video clip

A video clip is associated with a title using the meta element in SMIL 1.0 or SMIL 2.0, plus the title attribute of the main par element in the SMIL file.

Example 4: An image

A .JPEG image is associated with a title using EXIF metadata stored in the image file.

Note: Current user agents do not read this metadata.

Resources

No resources available for this technique.

Tests

Procedure
  1. Examine each Web page in the set

  2. Check whether each Web page is associated with a title

Expected Results
  • #2 is true.


G8: Creating an extended audio description for the multimedia content

Applicability

Any audio multimedia technology

This technique is referenced from:

Description

The objective of this technique is to all additional audio description to be inserted into a multimedia presentation when there is not enough time in the gaps int the dialog. This is done by simply freezing the image so that additional audio description of the video can be played. When the description is finished, the multimedia continues.

This technique provides people who are blind or who otherwise would miss information presented visually with additional audio description beyond that which can be provided by standard audio descriptions. Often the gaps in dialog are insufficient to allow enough audio description to be inserted to cover all the important visual information being presented. This technique freezes the multimedia presentation to allow additional audio description to be played. The multimedia presentation is then resumed.

Because it disrupts viewing for those who do not need the additional description, techniques that allow you to turn the feature on and off are often provided. Alternately, versions with and without the additional description can be provided.

Examples

Example 1

Example 1: A Training film has narrative that runs almost continuously throughout. An alternative version is available for people who have difficulty viewing the video portion. The alternative version freezes the video and provides audio description of key information.

Resources

Tests

Procedure
  1. Play multimedia with extended audio description enabled

  2. Check to see if multimedia freezes from time to time to allow audio description to convey important information regarding visual content

Expected Results
  • #2 is true


G9: Creating captions for live multimedia

Applicability

Applies to all technologies that present Audio Visual information

This technique is referenced from:

Description

The objective of this technique is to allow users who cannot hear to be able to access real-time multimedia broadcasts. It is more difficult to create accurate real-time captions because there is little time to correct mistakes or to listen a second time or consult someone to be sure the words are accurately reproduced. It is also harder to simplify or paraphrase information if it is flowing too quickly.

Real-time typing text entry techniques exist using stenographic and rapid typing technologies. Re-voicing speech-to-text (where a person listens to speech and then carefully re-voices it into a computer trained to their speech) is used today for telephone relay services and may be used in the future for captioning. Eventually speech-to-text with correction will be possible.

Examples

Example 1

Example 1: A television studio uses a real-time captioning service to create captions for its evening news online.

Resources

(none)

Tests

Procedure
  1. a procedure and policy are in place to ensure that captions are delivered in real-time

Expected Results
  • #1 is true


G10: Creating components using a technology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow user-settable properties to be directly set, and provide notification of changes

Applicability

programming technologies that have standard components that are programmed to interface with accessibility APIs

This technique is referenced from:

Description

The objective of this technique is to allow assistive technology to understand Web content so that it can convey equivalent information to the user through an alternate user interface.

Sometimes content is not created using markup language but rather using a programming language or tools. In many cases, these technologies have interface components that are already programmed to interface with accessibility APIs. If and author uses these components and fills in the properties (e.g. name, etc) the resulting user interface components in the content will be accessible to assistive technology.

However, if an author wants to create a user interface component that is new and they cannot use standard components, then they need to be sure to add the accessibility provisions themselves - and implement them in a way that is compatible with the accessibility API.

Examples

Example 1

Example 1: A Web unit uses java to create an applet. A group of authors wants to create an entirely new type of interface component so they can not use existing Java objects. They use Java swing classes to create their component because the Java swing classes already have provisions for connecting to different accessibility APIs. Using the Java swing classes they are able to create an interface component that exposes its name and role, is able to be set by AT and alerts AT to any updates.

Example 2: A Web unit uses an original ActiveX control that is written in the C++ programming language. The control is written to expliticly support the Microsoft Active Accessibility (MSAA) API to expose information about accept commands. The control then interacts directly with assistive technology running the user agent on systems that support MSAA.

Resources

(none currently listed)

Tests

Procedure
  1. Render content using an accessible User Agent

  2. Use an Accessibility Tool designed for the Accessibility API of the User agent to evaluate each user interface component

  3. Check that name and role for each user interface component is found by the tool.

  4. Change the values on the component

  5. Check that the Accessibility tool is alerted.

Expected Results
  • Step #3 and #5 are true for each user interface component


G11: Creating content that blinks for less than 3 seconds

Applicability

Technologies that support blinking content.

This technique is referenced from:

Description

The objective of this technique is to minimize the distraction caused by blinking content and enable users to re-focus on the other content on the page.

Blinking content can be created using a variety of technologies, many of which include options to loop blinking content continuously or to otherwise specify the amount of time the blinking content is displayed. Limiting the blinking of content to three seconds minimizes the distraction that blinking can cause. This will benefit people with certain types of learning disabilities and people with low vision.

Examples

  • An animated image is used to highlight items on sale. Within a list of items for purchase, an image of a red tag followed by the phrase "On sale" is used to indicate items being offered at a reduced price. The image of the red tag blinks on loading of the page and stops within three seconds.

Tests

Procedure
  1. Find all items that blink.

  2. For each item that blinks, determine if the interval between the start and end of the blinking is less than three seconds.

Expected Results
  • #2 is true.


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

Applicability

Applies to content that includes forms.

User Agent and Assistive Technology Support Notes

(none listed)

This technique is referenced from:

Description

The objective of this technique is to provide information to users about what will happen when a change to a form control results in a change of context. Because changing the value of a form control does not typically result in a change of context, it is important that authors provide instructions that make the user aware of the behavior in advance. Where possible, it is a good idea to programmatically associate the instructions describing the change with the form control itself.

Examples

Example 1
  1. A series of radio buttons at the top of a page include options for German, French and Spanish. Instructions precede the buttons that instruct the user that the language will be changed upon selecting an option.

  2. A 50 question online survey displays one question at a time. Instructions appear at the beginning of the survey that explain that users will be taken to the next question of the survey upon selecting an answer to each question.

Resources

(none currently listed)

Tests

Procedure
  • locate content where changing the setting of a form control results in a change of context

  • check to see that an explanation of what will happen when the control is changed is available prior to the controls activation

Expected Results
  • #2 is true.


G14: Ensuring that color encoded information is also available in text

Applicability

All technologies that support color.

This technique is referenced from:

Description

The objective of this technique is to ensure that when color is used to convey information, such as required form fields, the information conveyed by the color is also conveyed explicitly in text.

Examples

Example 1: A color-coded schedule

The schedule for sessions at a technology conference is organized into three tracks. Sessions for Track 1 are displayed over a blue background. Sessions in Track 2 are displayed over a yellow background. Sessions in Track 3 are displayed on a green background. After the name of each session is a code identifying the track in text: T1 for Track 1, T2 for Track 2, and T3 for Track 3.

Example 2: A color-coded schedule with icons

The schedule for sessions at a technology conference is organized into three tracks. Next to the title of each session is a colored icon showing what track it belongs to: blue icons represent track 1, yellow icons represent Track 2, and green icons represent Track 3. Each icon is associated with a text alternative reading "Track 1," "Track 2," or "Track 3," as appropriate.

Example 3: A table showing the conference schedule

The schedule for sessions at a technology conference is organized into three tracks. The schedule for each day is shown in a data table with headers for Time, Title, and Track . Sessions for Track 1 are displayed over a blue background. Sessions in Track 2 are displayed over a yellow background. Sessions in Track 3 are displayed on a green background

Example 4: A form with required fields

A form contains several required fields. The labels for the required fields are displayed in red. In addition, at the end of each label is an asterisk character, *. The instructions for completing the form indicate that "all required fields are displayed in red and marked with an asterisk *", followed by an example.

Example 5: A form with a green submit button

An on-line loan application explains that green buttons advance in the process and red buttons cancel the process. A form contains a green button containing the text Go. The instructions say "Press the button labeled Go to submit your results and proceed to the next step."

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure

For each item where color is used to convey information:

  1. Check that the information conveyed is also available in text and that the text is not conditional content.

Expected Results
  • Check #1 is true.


G15: Ensuring that content does not violate the general flash threshold or red flash threshold

Applicability

Applies to any technology

This technique is referenced from:

Description

The purpose of this technique is to allow people who have photosensitive seizures to view Web sites without encountering material that is likely to cause a seizure. Warnings can be provided but people may miss them and children may not be able to read or understand them. With this technique all material is checked and if it violates flash or red flash thresholds it is either not put on the site or it is modified so that it does not violate the thresholds.

Examples

  • An animation of a thunderstorm shows six flashes of lightning. The flashes are so fast that the general flash threshold is violated. The animation is modified to create a short pause after each pair of lightning flashes. After the changes are made, the animation does not violate the general flash threshold.

Resources

(none currently listed)

Tests

Procedure
  1. Check to see if content violates the flash and/or red flash thresholds by either

    • visually checking that there are no more than 2 flashes of any kind in a row OR

    • using a tool that will check for General Flash or Red Flash thresholds automatically

Expected Results
  • Step 1 is false


G17: Ensuring that luminosity contrast of at least 10:1 exists between text and background behind the text

Applicability

Any technology that produces visual output.

This technique is referenced from:

Description

The objective of this technique is to make sure that users can read text that is presented over a background. This technique goes beyond the 5:1 contrast technique to provide a higher level of contrast to make it easier for people with low vision to read.

If the background is a solid color (or all black or all white) then the luminosity contrast of the text can be maintained by making sure that each of the text letters have 10:1 luminosity contrast with the background.

If the background or the letters vary in luminosity (or are patterned) then the background around the letters can be chosen or shaded so that the letters maintain 10:1 luminosity contrast with the background behind them even if they do not have that luminosity contrast with the entire background.

The luminosity contrast can sometimes be maintained by changing the luminosity of the letters as the luminosity of the background changes across the page.

Another method is to provide a halo around the text that provides the necessary luminosity contrast if the background image or color would not normally be sufficiently different in luminosity.

Examples

Example 1

Example 1: A black background is chosen so that light colored letters that match the company’s logo can be use.

Example 2

Example 2: Text is placed over a picture of the college campus. Since a wide variety of colors and darknesses appear in the picture the area behind the text is fogged white so that the picture is very faint and the maximum darkness is still light enough to maintain a 10:1 luminosity with the black text written over the picture.

Resources

(none currently listed)

Tests

Procedure
  1. Measure the luminosity of each letter (unless they are all uniform) using the formula:

    • Luminosity = 0.2126 * ((R / FS) ^ 2.2) + 0.7152 * ((G / FS) ^ 2.2) + 0.0722 * ((B / FS) ^ 2.2)

    • where R, G, and B are the Red, Green, and Blue RGB values of the color, and FS is the maximum possible full scale RGB value for R, G, and B (255 for eight bit color channels).

    • For aliased letters use luminosity two pixels in from the edge of the letter.

    Measure the luminosity of the background pixels immediately next to the letter using same formula.

  2. Calculate the luminosity contrast ratio using the following formula.

    • Luminosity Contrast Ratio = (L1+.05) / (L2+.05).

    • where L1 is the higher value (of text or background) and L2 is the lower value.

    Check that the luminosity contrast ratio is equal to or greater than 10:1

Expected Results
  • #4 is true


G18: Ensuring that luminosity contrast of at least 5:1 exists between text and background behind the text

Applicability

Any technology that produces visual output.

This technique is referenced from:

Description

The objective of this technique is to make sure that users can read text that is presented over a background. This technique uses a lower threshold for contrast to allow more flexibility by authors in color choices.

If the background is a solid color (or all black or all white) then the luminosity contrast of the text can be maintained by making sure that each of the text letters have 5:1 luminosity contrast with the background.

If the background or the letters vary in luminosity (or are patterned) then the background around the letters can be chosen or shaded so that the letters maintain 5:1 luminosity contrast with the background behind them even if they do not have that luminosity contrast with the entire background.

The luminosity contrast can sometimes be maintained by changing the luminosity of the letters as the luminosity of the background changes across the page.

Another method is to provide a halo around the text that provides the necessary luminosity contrast if the background image or color would not normally be sufficiently different in luminosity.

Examples

Example 1

Example 1: A black background is chosen so that light colored letters that match the companies logo can be use.

Example 2

Example 2: Text is placed over a picture of the college campus. Since a wide variety of colors and darknesses appear in the picture the area behind the text is fogged white so that the picture is very faint and the maximum darkness is still light enough to maintain a 5:1 luminosity with the black text written over the picture.

See also the contrast samples at the bottom of the page.

Resources

(none currently listed)

Tests

Procedure
  1. Measure the luminosity of each letter (unless they are all uniform) using the formula:

    • Luminosity = 0.2126 * ((R / FS) ^ 2.2) + 0.7152 * ((G / FS) ^ 2.2) + 0.0722 * ((B / FS) ^ 2.2)

    • where R, G, and B are the Red, Green, and Blue RGB values of the color, and FS is the maximum possible full scale RGB value for R, G, and B (255 for eight bit color channels).

    • For aliased letters use luminosity two pixels in from the edge of the letter.

    Measure the luminosity of the background pixels immediately next to the letter using same formula.

  2. Calculate the luminosity contrast ratio using the following formula.

    • Luminosity Contrast Ratio = (L1+.05) / (L2+.05).

    • where L1 is the higher value (of text or background) and L2 is the lower value.

    Check that the luminosity contrast ratio is equal to or greater than 5:1

Expected Results

The luminosity contrast ratio is equal to or greater than 5:1

  • #4 is true


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

Applicability

Applies to any technology

This technique is referenced from:

Description

The objective of this technique is to avoid flashing at rates that are known to cause seizures if the flashes are bright and large enough. Since some users may be using screen enlargers, this technique limits the flashing of any size content to no more than three flashes in any 1-second period.

Note 1: This technique is stricter than the Level 1 success criterion but is easier to test and can be used to meet the Level 1 success criterion because all failure thresholds in the Level 1 success criterion involve flashing 3.5 flashes or more within one second. Most content does not flash at all and even content that blinks does not blink this fast except on rare occasions. Therefore, in order to avoid having to carry out the more complex testing specified by the success criterion, one could follow this technique to ensure that content only flashes one, two, or at most three times in any 1-second period.

Note 2: Regarding 3.5 Flashes; if there are seven transitions from dark to light or light to dark, it would be 3.5 flashes, which is more than the allowed 3 flashes (6 transitions).

Examples of 3.5 flashes or 7 transitions:

  • STARTING DARK-LIGHT-DARK-LIGHT-DARK-LIGHT-DARK-LIGHT or

  • STARTING LIGHT-DARK-LIGHT-DARK-LIGHT-DARK-LIGHT-DARK.

Examples

  • Content has lightning flashes. Content is designed so that lightning only flashes two or three times without a pause in flashing.

Resources

Tests

Procedure
  1. Check that there are no more than three flashes during any 1-second period.

  2. If there are three flashes, check that the Light/Dark status at the end of the 1 second period is the same as at the start.

Expected Results
  • Both Step one and Step 2 are true.


G20: Ensuring that the only way to get to an inaccessible version is from a link from the accessible version

Applicability

Content where a nonconforming and conforming version are provided as alternatives to each other.

This technique is referenced from:

Description

The objective of this technique is to ensure that users can always access an accessible version of the content. When content is provided in a format that does not conform to WCAG, the site as a whole can still conform if alternate versions of the inaccessible content are provided. The success criterion requires that alternate versions are available "from the same URI" as the nonconforming version. It is the intent of that wording that it can be sufficient to provide a link to conforming content from the nonconforming content (see Providing a link at the top of the nonconforming content that points to an alternate version that does meet WCAG 2.0 Level 1 success criteria (future link)).

In order for the link to alternate content to fulfill its intent, the link needs to conform to WCAG requirements, that is, be accessible. In some technologies, even though the content as a whole may not conform, a link can be provided that does conform. In other technologies, however, it is not even possible to provide a link to alternate content within that technology that conforms. Users may be unable to find the alternate content if the only pointer is in an inaccessible technology.

This technique describes how to provide alternate content in such a situation. In this technique, the WCAG conforming version contains a link to the nonconforming version. This way users access the conforming content, and only access the nonconforming content if they wish, via a link. In order to ensure users do not accidentally get "stuck" in inaccessible content, the nonconforming version is excluded from search engine results, site maps (unless the conforming version is also included), etc.

Examples

  • An online physics course uses a proprietary modeling language to provide interactive demonstrations of physical processes. Because the technology is new and not widely used, it does not provide accessibility features supported by user agents. Students in the course access a WCAG conforming description of the processes and models, but that is not interactive. A link is provided to the nonconforming enhanced interactive version. Students may choose to access the interactive version, but those who do not are still able to learn about the process.

Tests

Procedure

Where WCAG conforming alternatives are provided for nonconforming content:

  1. Check that there is a link to the nonconforming content from the conforming content.

  2. Check that the nonconforming content does not appear in search engine results, site maps, and the site's regular navigation.

Expected Results
  • #1 and #2 are true.


G21: Ensuring that users are not trapped in content

Applicability

All technologies which support interactive operation.

This technique is referenced from:

Description

The objective of this technique is to ensure that keyboard users do not become trapped in a subset of the content that can only be exited using a mouse or pointing device. A common example is content rendered by plug-ins. Plug-ins are user agents that render content inside the user agent host window and respond to all user actions that takes place while the plug-in has the focus. If the plug-in does not provide a keyboard mechanism to return focus to the parent window, users who must use the keyboard may become trapped in the plug-in content.

This problem can be avoided by using one of the following mechanisms to provide a way for users to escape the subset of the content:

  • Ensuring that the keyboard function for advancing focus within content (commonly the tab key) exits the subset of the content after it reaches the final navigation location.

  • Providing a keyboard function to move the focus out of the subset of the content. Be sure to document the feature in an accessible manner within the subset.

  • If the subset of the content does natively provide a "move to parent" keyboard command, documenting that command before the user enters the plug-in so they know how to get out again.

Examples

  • Once a user tabs into an applet, further tabs are handled by the applet preventing the person from tabbing out. However, the applet is designed so that it returns keyboard focus back to the parent window when the person finishes tabbing through the tab sequence in the applet.

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. tab through content from start to finish.

  2. check to see if keyboard focus is trapped in any of the content such that the person cannot move out of any part of the content and continue through the rest of the content.

Expected Results
  • #2 is false


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

Applicability

All technologies that contain links.

This technique is referenced from:

Description

The objective of this technique is to identify the purpose of a link from the link and its context. This is done by associating the link with its text and with text that is associated with the immediately enclosing structural unit of the content. The purpose of the link is identified by interpreting the link in the context of the text associated with its enclosing structure unit. The description lets a user distinguish this link from links in the Web unit that lead to other destinations and helps the user determine whether to follow the link. The URI of the destination is generally not sufficiently descriptive.

Note that only the text associated with the immediately enclosing structural unit of the link is used to provide the context for the link. The definition of the immediately enclosing structural unit is technology-specific. It may not be possible to represent complex content in a way that includes all the necessary context for a link in this unit, but still represent other important relationships in the content. In this situation, another technique must be used to identify the purpose of the link.

Examples

Example 1: A list of books

A list of book titles are followed by PDF, Audible, E-book to indicate the versions available. The book title is a link to information about the book. Each version type is a link to that version of the book. Because the books are formatted as a list, each list item contains the information about a book and provides the context to understand the purpose of the book version links.

Resources

No resources available for this technique.

Tests

Procedure

For each link in the content that uses this technique:

  1. Check that text of the link combined with the text associated with the enclosing structural unit of content describes the purpose of the link

Expected Results
  • The above check is true.


G54: Including a sign language interpreter in the corner of the video stream

Applicability

Applies to all technologies that present multimedia information

This technique is referenced from:

Description

The objective of this technique is to allow users who cannot hear or read text rapidly to be able to access multimedia material.

For those who communicate primarily in sign language it is sometimes less preferable and sometimes not possible for them to read and understand text at the rate it is presented in captions. For these latter individuals it is important to provide sign language presentation of the audio information.

One universally compatible way of doing this is to simply embed a video of the sign language interpreter in the corner of the video stream. This has the disadvantage of providing a lower resolution image that cannot be easily enlarged without enlarging the entire image.

Note: Since sign language is not usually a signed version of the printed language, the author has to decide which sign language to include. Usually the sign language of the primary audience would be used. If intended for multiple audiences, multiple sign languages may be used. Refer to advisory techniques for multiple sign languages.

Examples

  • Example 1: A television station provides a sign language interpreter in the corner of its on-line news video.

Resources

  • Guidelines for the Production of Signing Books

    • "Sign Language presentation" gives a broad overview of issues to consider when filming sign language interpreters. Includes discussion of signing both written and spoken originals.

    • Techniques for filming are discussed in chapter 12, “Filming the Signer(s)”.

    • Useful information about how to display the sign language interpreter in relation to the original multimedia content is provided in Chapter 13, "Editing"

      Note: These techniques may need to be adapted for Web-based presentation.

(none currently listed)

Tests

Procedure
  1. Have someone watch the program who can hear and is familiar with the sign language being used.

  2. Check to see if there is a sign language interpreter on screen.

  3. Check to see that dialog and important sounds are being conveyed by the interpreter visible on screen.

Expected Results
  • #2 and #3 are true


G55: Linking to definitions

Applicability

All technologies that include links.

This technique is referenced from:

Description

The objective of this technique is to make the definition of a word, phrase, or abbreviation available by providing the definition, either within the same Web unit or in a different Web unit, and establishing a link between the item and its definition.

Links are a powerful option for providing access to the definition of a word, phrase, or abbreviation. A user can use the link to find the definition quickly and easily, and then return to his place in the content via the user agent's Back button.

Examples

Example 1

Technical terms and abbreviations in an article about sports injuries are linked to definitions in a medical dictionary.

Example 2

A textbook contains a glossary of new vocabulary words introduced in each chapter. The first occurrence of each of these words is linked to its definition in the glossary.

Example 3

A general glossary of abbreviations is provided. All occurrences of abbreviations are linked directly to the appropriate definition within that glossary.

Example 4

The word jargon is linked to its definition in the WCAG2 Glossary.

Example 5

The word "modulo" is jargon used in Web content about mathematics. A definition for modulo is included within the Web unit. Each occurrence of the word modulo is linked to its definition.

Example 6

A Japanese idiom is linked to its definition. This example uses a link within the page to navigate to the definition of an idiomatic expression.

<p><a href="#definition">さじを投げる</a></p>

<h3><a id="definition" name="definition">脚注:</a></h3>
<dl>
<dt>さじを投げる</dt>
<dd>どうすることもできなくなり、あきらめること。</dd>
</dl>
</p>						

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure

For each word, phrase, or abbreviation to be defined:

  1. Check that at least the first instance of the item is a link.

  2. Check that each link navigates to the definition of the item.

Expected Results
  • The checks above all pass.


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

Applicability

Any technology

This technique is referenced from:

Description

The objective of this technique is to allow authors to include sound behind speech without making it too hard for people with hearing problems to understand the speech. Making sure that the speech is 20 db louder than the backgound sound makes the speech 4 times louder than the background sounds. For information on Decibels (dB) see About Decibels

Examples

Example 1: An announcer speaking over a riot scene
  • A narrator is describing a riot scene. The volume of the riot scene is adjusted so that it is 20 db lower than the announcers volume before the scene is mixed with the narrator.

Example 2: Sufficient audio contrast between a narrator and background music

The following is a link to an mp3 file. It is an audio track that has been mixed so that there is sufficient contrast between the foreground and background. When it is listend to, the forground is heard clearly above the background.

Example of good audio contrast (MP3)

Here is a transcript of the speaking voice on this good contrast example:

"Usually the foreground refers to a voice that is speaking and should be understood. My speaking voice right now is 20 decibels above the background which is the music. This is an example of how it should be done."

Example 3 (failure): Insuficient Audio Contrast between a narrator and background music

The the following is a link to an MP3 audio example of insufficient contrast between a narrator and background music:

Example of bad audio contrast (MP3)

Here is the transcript of the voice on the insufficient contrast example:

"This is an example of a voice that is not loud enough against the background. The voice which is the foreground is only about 2 decibels above the background. Therefore is difficult to understand for a person who is hard of hearing. It is hard to discern one word from the next. This is an example of what not to do."

Example 4: Audio track that has been mixed with sufficient contrast between the foreground and background as seen in a popular audio editing program.

After the foreground and the background tracks have been mixed to one single file, that single file can be opened in any popular audio editing software package and viewed in an editing window that renders a visual representation of the audio content. This can be used to help determine the contrast level between the foreground and background of an audio track.

The graphic below (figure 1) is a visual representation of the mp3 audio file above that has sufficient contrast between the foreground and the background. Both the foreground and the background are in the selected portion of the wave file.

Figure 1
Figure 1: visual representation of sufficient contrast both foreground and background are selected.

The selected region of the wave file in figure 1 above which contains both the foreground and background sound is a very large wave. The selected region of Figure 2 below which contains only background sound is a much smaller wave.

Figure 2
Figure 2: visual representation of sufficient contrast where only the background is selected.

Resources

(none currently listed)

Tests

Procedure
  1. Locate loud values of background content between forground speech

  2. Measure the volume in dB(A) SPL

  3. Measure the volume of the forground speech in dB(A) SPL

  4. Subtract the values

  5. Check that the result is 20 or greater.

Expected Results
  • #5 is true


G57: Ordering the content in a meaningful sequence

Applicability

All technologies.

This technique is referenced from:

Description

The objective of this technique is to ensure that the order of content presented to assistive technologies allows the user to make sense of the content. Some techniques permit the content to be rendered visually in a meaningful sequence even if the underlying order of the content is confusing.

For example, when mixing languages with different directionality in HTML, the bidirectional algorithm may place punctuation in the wrong place. Correctly ordered content maintains the punctuation in the correct sequence in the content stream and uses markup to override the bidirectional algorithm, rather than moving the punctuation in the content stream so that the default rendering positions it correctly.

When rendered visually, white space characters such a space or tab may not appear to be part of the content. However, when inserted into the content to control visual formatting, they may interfere with the meaning of the content.

At a larger granularity, controlling the placement of blocks of content in an HTML document using layout tables may produce a rendering in which related information is positioned together visually, but separated in the content stream. Since layout tables are read row by row, if the caption of an illustration is placed in the row following the illustration, it may be impossible to associate the caption with the image.

Examples

Example 1

A Web page from a museum exhibition contains a navigation bar containing a long list of links. The page also contains an image of one of the pictures from the exhibition, a heading for the picture, and a detailed description of the picture. The links in the navigation bar form a meaningful sequence. The heading, image, and text of the description also form a meaningful sequence. CSS is used to position the elements on the page.

Markup:

<h1>My Museum Page</h1>
<ul id="nav">
	<li><a href="#">Link 1</a></li>
	...
	<li><a href="#">Link 10</a></li>
</ul>
<div id="description">
<h2>Mona Lisa</h2>
<p>
<img src="img.png" alt="Mona Lisa">
</p>
<p>...detailed description of the picture...</p>
</div>

CSS:

ul#nav
{
	float: left;
	width: 9em;
	list-style-type: none;
	margin: 0;
	padding: 0.5em;
	color: #fff;
	background-color: #063;
}

ul#nav a
{
	display: block;
	width: 100%;
	text-decoration: none;
	color: #fff;
	background-color: #063;
}

div#description
{
	margin-left: 11em;
}

Resources

No resources available for this technique.

Tests

Procedure
  1. Identify meaningful sequences in the source document.

  2. Check that the elements of each meaningful sequence are in consecutive order in the content.

Expected Results
  • Check #2 is true.


G58: Placing a link to the transcript immediately next to the non-text content

Applicability

This technique is not technology specific and can be used in any technology that supports links.

This technique is referenced from:

Description

With this technique, a link to the collated document of captions and audio descriptions is provided. The collated document could be at another location on the same Web unit or at another URI. A link to the collated document is immediately adjacent to the non-text content. The link can be immediately before or after the multimedia content. If the collated document is on the same Web unit as other content then put "End of document" at the end so that they know when to stop reading and return to their previous place. If a "Back" button will not take the person back to the point from which they jumped, then a link back to the non-text content location is provided.

Examples

Example 1: An .MOV Document in an HTML Document

Code on a page called "Olympic_Sports.htm"

<a name="Olympic_Wrestling"></a>
<p><a href="http://www.example.com/movies/olympic_wrestling.mov">Olympic Wrestling movie</a>, 
<a href="http://www.example.com/transcripts/olympic_wrestling_transcript.htm>Olympic 
Wrestling collated Transcript</a></p>
Example 2: The link back to the .MOV Document in an HTML Document

Code on the page olympic_wrestling_transcript.htm

<p>Sports announcer 1: This is a great battle tonight between England's "Will Johnson" and 
"Theodore Derringo" from Argentina</p>

<p>Scenery: There is a mat set out in the middle of the stadium with 500 people in the 
stands...</p>

<p> ...more dialogue ...<p>

<p> ...more scenery...</p>

<p> ...etc...</p>

<p>Sports announcer 2: And that is all for tonight, thank you for joining us tonight where 
Will Johnson is the new Gold Medalist. 
<a href="../movies/Olympic_Sports.htm#Olympic_Wrestling>Return to Movie page</a> </p>

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Check for the presence of a link immediately before or after the non-text content

  2. Check that it is a valid link that points directly to the collated document of this particular multimedia.

  3. Check for the availability of a link or back function to get the user back to the original location of the multimedia content

Expected Results
  • Items #1 through 3 are all true.


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

Applicability

All technologies that contain interactive elements and define a default tab order for interactive elements.

This technique is referenced from:

Description

The objective of this technique is to ensure that interactive elements receive focus in an order that follows sequences and relationships in the content. When designing the content, the interactive elements such as links and form controls are placed in the content so that the default tab order follows the sequences and relationships in the content. Each technology defines its default tab order, so the mechanism for placing the controls in the content will depend on the technology used.

As an example, in HTML, the default focus order follows the order in which elements appear in the content source. When the order of the HTML source matches the visual order of the Web unit, tabbing through the content follows the visual layout of the content. When the source order does not match the visual order, the tab order through the content must reflect the logical relationships in the content that are displayed visually.

Examples

  • A form contains two text input fields that are to be filled in sequentially. The first text input field is placed first in the content, the second input field is placed second.

  • A form contains two, side-by-side sections of information. One section contains information about an applicant; the other section contains information about the applicant's spouse. All the interactive elements in the applicant section receive focus before any of the elements in the spouse section. The elements in each section receive focus in the reading order of that section.

Resources

No resources available for this technique.

Tests

Procedure
  1. Determine the order of interactive elements in the content.

  2. Determine the logical order of interactive elements.

  3. Check that the order of the interactive elements in the content is the same as the logical order.

Expected Results
  • Check #3 is true.


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

Applicability

Applies to all technologies except those for spoken interaction.

This technique is referenced from:

Description

The purpose of this technique is to allow authors to play a sound on their page but avoid the problem of users not being able to use their screen readers due to interference by the content sound. It also allows the author to avoid putting controls on the page to control the sound - and the problem faced by consumers with screen readers in finding the control (when unable to hear their screen reader).

The technique is simple. The sound plays for 3 or less seconds and stops automatically.

Examples

  • Example 1: A page opens with a trumpet fanfare and then goes silent

  • Example 2: A homepage opens with a short greeting by the chairman and then goes silent.

  • Example 3: A page opens with instructions on how to use the page.

  • Example 4: A page opens with a warning and then goes silent.

Resources

(none)

(none currently listed)

Tests

Procedure
  1. open the URI

  2. check that all sound that plays automatically stops in 3 seconds or less

Expected Results
  • #2 is true


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

Applicability

Any technologies.

This technique is referenced from:

Description

The objective of this technique is to make content easier to use by making the placement of repeated components more predictable. This technique helps maintain consistent layout or presentation between Web units by presenting components that are repeated in these Web units in the same relative order each time they appear. Other components can be inserted between them, but their relative order is not changed.

This technique also applies to navigational components that are repeated. Web units often contain a navigation menu or other navigational component that allows the user to jump to other Web units. This technique makes the placement of navigational components more predictable by presenting the links or programmatic references inside a navigational component in the same relative order each time the navigational component is repeated. Other links can be removed or inserted between the existing ones, for example to allow navigation inside a subsection of a set of Web units, but the relative order is not changed.

Examples

  • A Web site has a logo, a title, a search form and a navigation bar at the top of each page; these appear in the same relative order on each page where they are repeated. On one page the search form is missing but the other items are still in the same order.

  • A Web site has a left-hand navigation menu with links to the major sections of the site. When the user follows a link to another section of the site, the links to the major sections appear in the same relative order in the next page. Sometime links are dropped and other links are added, but the other links always stay in the same relative order. For example, on a Web site of a company that sells products and offers training, when a user moves from the section on products to the section on training, the links to individual products are removed from the navigation list, while links to training offerings are added.

Resources

(none currently listed)

Tests

Procedure
  1. List components that are repeated on each Web unit in a set of Web units (for example, on each page in a Web site).

  2. For each component, check that it appears in the same relative order with regard to other repeated components on each Web unit where it appears.

  3. For each navigational component, check that the links or programmatic references are always in the same relative order.

Expected Results
  • #2 is true.

  • #3 is true.


G62: Providing a Glossary

Applicability

Any technology containing text.

This technique is referenced from:

Description

The objective of this technique is to make the definition of a word, phrase, or abbreviation available by providing the definition in a glossary. A glossary is an alphabetical list of words, phrases, and abbreviations with their definitions. Glossaries are most appropriate when the words, phrases, and abbreviations used within the content relate to a specific discipline or technology area.

The glossary is included at the end of the Web unit or the glossary is located via one of the mechanisms for locating content within a set of Web units. (See How to Meet Success Criterion 2.4.2.)

If the glossary contains several definitions for the same word, phrase, or abbreviation, simply providing the glossary is not sufficient to satisfy this success criterion. A different technique should be used to find the correct definition. This is especially important if the uses of the word, phrase, or abbreviation are not unique within the Web unit, that is, if different occurrences of the item have different definitions.

Examples

Example 1

Users of on line chat forums have created several acronyms and abbreviations to speed up typing conversations on the computer. For example, LOL refers to "laughing out loud" and FWIW abbreviates "for what it's worth". The site provides a glossary page that lists the expansions for the commonly used acronyms and abbreviations.

Example 2

A Web unit discussing mathematical theory includes a glossary of commonly used mathematical terms, abbreviations and acronyms.

Example 3

A textbook contains a glossary of new vocabulary words introduced in each chapter.

Example 4

Dutch text uses the phrase 'Hij ging met de kippen op stok' (He went to roost with the chickens). The glossary explains that this phrase means 'Hij ging vroeg naar bed' (He went to bed early).

Example 5: A glossary of idiomatic expressions

The American novel "The Adventures of Huckleberry Finn" includes many idiomatic expressions that were used in the southwestern United States in the 1840s. In an online edition designed for students, each idiomatic expression is linked to an item in the glossary.

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure

Check that either

  1. The glossary is included in the Web unit, or

  2. A mechanism is available to locate the glossary.

For each word, phrase, or abbreviation to be defined,

  1. Check that the item is defined in the glossary, and

  2. Check that the glossary contains only one definition for each item.

Expected Results
  • All checks above pass.


G63: Providing a Site Map

Applicability

All technologies.

This technique is referenced from:

Description

A site map is a Web page that provides links to different sections of the site. To make the site map available within the site, at a minimum every page that is listed in the site map contains a link to the site map.

The site map serves several purposes.

  • It provides an overview of the entire site.

  • It helps users understand what the site contains and how the content is organized.

  • It offers an alternative to complex navigation bars that may be different at different parts of the site.

There are different types of site maps. The simplest and most common kind of site map is an outline that shows links to each section or sub-site. Such outline views do not show more complex relationships within the site, such as links between pages in different sections of the site. The site maps for some large sites use headings that expand to show additional detail about each section.

A site map describes the contents and organization of a site. It is important that site maps be updated whenever the site is updated. A Web page that does not link to all the sections of a site, that presents an organization that is different from the site's organization, or that contains links that are no longer valid is not a valid site map.

Examples

Example 1

The Web Accessibility Initiative provides a WAI site map that lists different sections of its Web site. The site map shows the different sections of the Web site, and shows some of the substructure within those sections.

Example 2

The site map for an on-line magazine lists all the sections of the magazine and the subsections in each section. It also include links for Help, How to Contact Us, Privacy Policy, Employment Opportunities, How to Subscribe, and the home page for the magazine.

Resources

  • Graphic Organizers page at the National Center for Accessible Curriculum provides a useful overview of different kinds of graphic organizers and their uses, plus a summary of relevant research on the effectiveness of graphical organizers for students with learning disabilities.

  • Usability Glossary: sitemap

Tests

Procedure
  1. Check that the site contains a site map

  2. Check that the links in the site map lead to the corresponding sections of the site

  3. For each link in the site map, check that the target page contains a link to the site map

  4. For each page in the site, check that the page can be reached by following some set of links that start at the site map.

Expected Results
  • All of the checks above are true.


G64: Providing a Table of Contents

Applicability

All technologies.

This technique is referenced from:

Description

A table of contents provides links to section headings and sub-headings within the hierarchical structure of a document.

The table of contents serves two purposes:

  • It gives users an overview of the document's contents and organization.

  • It allows readers to go directly to a specific section of an on-line document.

The table of contents typically includes only major sections of the document, though in some cases an expanded table of contents that provides a more detailed view of a complex document may be desirable.

Examples

Example 1

The Web Content Accessibility Guidelines 2.0 contains a table of contents that is a hierarchical list of links to the sections and subsections of the document. The hierarchy of the table of contents reflects the organization of the sections, and each item in the table of contents is a link that takes the user directly to that section.

Example 2

The first page of Using Accessible PDF Documents with Adobe Reader 7.0: A Guide for People with Disabilities contains a table of contents that lists the sections of the guide. The PDF version of the Guide for People with Disabilities contains a more detailed table of contents for the entire document on page 3.

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure
  1. Check that a Table of Contents or a link to a Table of Contents exists in the document.

  2. Check that the values and order of the entries in the Table of Contents correspond to the names and order of the sections of the document.

  3. Check that the entries in the Table of Contents link to the correct sections of the document.

Expected Results
  • All checks above are true.


G65: Providing a breadcrumb trail

Applicability

All technologies.

This technique is referenced from:

Description

A breadcrumb trail helps the user to visualize how content has been structured and how to navigate back to previous Web units, and may identify the current location within a series of Web units. A breadcrumb trail either displays locations in the path the user took to reach the Web unit, or it displays the location of the current Web unit within the organization of the site.

Breadcrumb trails are implemented using links to the Web units that have been accessed in the process of navigating to the current Web unit. They are placed in the same location within each Web unit in the set.

It can be helpful to users to separate the items in the breakcrumb trailing with a visible separator. Examples of separators include >, |, /, and ::.

Examples

Example 1

A developer searches within the Web site of an authoring tool manufacturer to find out how to create hyperlinks. The search results bring him to a Web unit with specific instructions for creating hyperlinks using the authoring tool. It contains the following links to create a breadcrumb trail:

Home :: Developer Center :: How To Center 

In this example the breadcrumb trail does not contain the title of the current Web unit, "How to create hyperlinks". That information is available as the title of the Web unit.

Example 2

A photographer’s portfolio Web site has been organized into different galleries and each gallery has further been divided into categories. A user who navigates through the site to a Web unit containing a photo of a Gentoo penguin would see the following breadcrumb trail at the top of the Web unit:

Home / Galleries / Antarctica / Penguins / Gentoo Penguin 

All of the items except "Gentoo Penguin" are implemented as links. The current location, Gentoo Penguin, is included in the breadcrumb trail but it is not implemented as a link.

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure

When breadcrumb trails have been implemented in a set of Web units:

  1. Navigate to a Web unit .

  2. Check that a breadcrumb trail is displayed.

  3. Check that the breadcrumb trail displays the correct navigational sequence to reach the current location or the correct hierarchical path to the current location within the site structure.

  4. For a breadcrumb trail that does not include the current location:

    1. Check that all elements in the breadcrumb trail are implemented as links.

  5. For a breadcrumb trail that does include the current location:

    1. Check that all elements except for the current location are implemented as links.

    2. Check that the current location is not implemented as a link.

  6. Check that all links navigate to the correct Web unit as specified by the breadcrumb trail.

Expected Results
  • For all Web units in the set using breadcrumb trails,

    • Checks #2, #3, and #6 are true.

    • Either check #4 or #5 is true.


G68: Providing a descriptive label that describes the purpose of live audio-only and live video-only content

Applicability

Applies to all technologies

This technique is referenced from:

Description

This technique provides a descriptive label for Live audio-only and live video-only content. This label may be used in combination with a full text transcript of the audio or a full text or audio description of the video. Those alternative however are not part of this technique. The purpose of this technique is to ensure that the user can determine what the non-text content is - even if they cannot access it. NOTE: Even if full alternatives are also available, it is important that users be able to identify the non-text content when they encounter it so that they are not confused, and so that they can associate it with the full alternative when they encounter it.

Examples

Example 1
  • A live video feed of the east coast highway has the following descriptive label "Live video picture of East Coast Highway just south of the I-81 interchange showing current traffic conditions."

  • A live audio feed of the Mississippi House of Representatives has the following descriptive label "Live audio from the microphones in the Mississippi House of Representatives."

Resources

(none currently listed)

Tests

Procedure
  1. remove, hide, or mask the non-text content

  2. display the text alternative(s)

  3. check that the purpose of the non-text content is clear - even if content is lost.

Expected Results
  • #3 is true.


G69: Providing a full multimedia text alternative including any interaction

Applicability

General technique. Applies to all technologies

This technique is referenced from:

Description

The purpose of this technique is to provide an accessible alternative way of presenting the information in a multimedia presentation.

In a multimedia presentation, information is presented in a variety of ways including

  • dialogue,

  • sounds (natural and artificial),

  • the setting and background,

  • the actions and expressions of people, animals, etc.,

  • text or graphics,

  • and more.

In order to present the same information in accessible form, this technique involves creating a document that tells the same story and presents the same information as the multimedia. Such a document is sometimes called a screenplay. It includes all the important dialogue and actions as well as descriptions of backgrounds etc. that are part of the story.

If an actual screenplay was used to create the multimedia in the first place, this can be a good place to start. In production and editing however, the multimedia usually changes from the screenplay. For this technique, the original screenplay would be corrected to match the dialogue and what actually happens in the final edited form of the multimedia.

In addition, some special types of multimedia include interaction that has to occur at particular places in the playing of the multimedia. Sometimes it may result in an action taking place (e.g. something is purchased, sent, done, etc.). Sometimes it may change the course of the multimedia (e.g. the multimedia has multiple paths that are determined by user input). In those cases links or some other mechanism would be used in the full multimedia text alternative to allow people using the alternative to be able to have the same options and abilities as those using the multimedia.

Examples

  • A training film shows employees how to use a new piece of equipment. It involves a person talking throughout while they demonstrate the operation. The screenplay used to create the training film is used as a starting point. It is then edited and corrected to match the dialogue etc. The film and the resulting full multimedia text alternative are then made available on the company Web site. Employees can then use either or both to learn how to use the machine.

  • An interactive shopping environment is created that allows users to steer themselves around in a virtual store and shop. A full multimedia text alternative allows the users to access the same shopping in text with links to choose aisles and to purchase things instead of dragging them into a virtual shopping basket.

Resources

No resources available for this technique.

Tests

Procedure
  1. View the multimedia presentation with the full multimedia text alternative in hand.

  2. Check that the dialogue in the full multimedia text alternative matches the dialogue in the multimedia presentation

  3. Check that full multimedia text alternative has descriptions of sounds.

  4. Check that full multimedia text alternative has descriptions of setting and setting changes.

  5. Check that full multimedia text alternative has descriptions of actions and expressions of any 'actors' (people, animals etc).

Expected Results
  • #2, 3, 4, 5 are true.


G70: Providing a function to search an on-line dictionary

Applicability

All technologies

This technique is referenced from:

Description

The objective of this technique is to provide the definition of words, phrases, jargon, or abbreviation expansions by adding a mechanism to access an on-line dictionary to the Web unit. This technique uses existing resources on the Web to provide the definition rather than requiring the author to create a glossary or other mechanism within the site. By providing access from within the Web unit, a user can easily locate the desired definition.

Examples

Example 1

A site that describes how a computer works would include a search form on each Web unit. The search would be performed against an on-line dictionary of computer terms, acronyms, and abbreviations. Since the dictionary is specialized for computer terms, the acronym expansion found should be more accurate than with a general dictionary.

Example 2

An on-line course in English grammar provides a paragraph of text which introduces new vocabulary words. Each of the vocabulary words is a link to an on-line dictionary to find the definition of the word. Activating a link will open up a new window to an on-line dictionary site with the specific vocabulary word defined.

An on-line course in English grammar provides a paragraph of text which introduces new vocabulary words. Each of the vocabulary words is a link to an on-line dictionary to find the definition of the word. Activating a link will open up a new window to an on-line dictionary site with the specific vocabulary word defined.

Resources

No resources available for this technique.

Tests

Procedure

For each word, phrase, or abbreviation to be defined:

  1. Check that a mechanism exists within the Web unit to search for the word, phrase, or abbreviation via an on-line dictionary.

  2. Check that a search of the dictionary for the word, phrase, or abbreviation finds the correct definition.

Expected Results
  • Checks #1 and #2 are true.


G71: Providing a help link on every Web unit

Applicability

All technologies.

This technique is referenced from:

User Agent and Assistive Technology Support Notes

The example following does not work with JAWS—implicit labels are poorly supported, and JAWS does not read the Help link as part of the label before announcing the control (as required by the SC).

Description

The objective of this technique is to provide context sensitive help for users as they enter data in forms by providing at least one link to the help information on each Web unit. The link targets a help page with information specific to that Web unit. Another approach is to provide a help link for every interactive control. Positioning this link immediately before or after the control allows users to easily tab to it if they have problems in the control. Displaying the help information in a new browser window ensures that any data that has already been entered into the form will not be lost. NOTE: A link is not the only means to provide help.

Examples

Example 1

The example below shows a label element enclosing both an input form control, and a help link following the "input" in sequence. Including the help link within the label element allows screen reader users to have access to the help link when interacting with the input form control.

<form action="test.html">
	<label for="test">Test control
	<input type="text" name="test" id="test" />
	<a href="help.html" target="_blank">Help</a></label>
</form>

Tests

Procedure
  1. Identify a Web unit that contains forms.

  2. Determine if there is at least one link to help information specific to completing the form on this Web unit or other resource.

  3. Determine if there are links either before or after each interactive control to help information specific to that control.

Expected Results
  • Either #2 or #3 are true.


G73: Providing a long description in another location with a link to it that is immediately adjacent to the non-text content

Applicability

Applies to all technologies

This technique is referenced from:

Description

The objective of this technique is to provide a way to link to remote long descriptions in technologies that do not have a long description feature built directly into them (e.g. longdesc) or where the feature is known to not be supported.

With this technique, the long description is provided in another location than the non-text content. This could be at another location within the same URI or at another URI. A link to that long description is provided that is immediately adjacent to the non-text content. The link can be immediately before or after the non-text content. If the description is located along with other text then put "End of description" at the end so that they know when to stop reading and return to the main content. If a "Back" button will not take the person back to the point from which they jumped, then a link back to the non-text content location is provided.

This technique was commonly used in HTML before 'longdesc' was added to the specification. In HTML it was called a D-Link because it was usually implemented b