Techniques for WCAG 2.0

Skip to Content (Press Enter)

This document is a draft, and is designed to show changes from a previous version. It is presently showing added text,changed text,deleted text,[start]/[end] markers,and Issue Numbers.

Hide All Edits   |   Toggle Deletions  |   Toggle Issue Numbers   |   Toggle [start]/[end] Markers   |   Show All Edits

Changes are displayed as follows:


F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to using null alt on an image where the image is the only content in a link


Content that contains links.

This failure relates to:

User Agent and Assistive Technology Support Notes

Different assistive technologies employ different repair strategies when dealing with links that lack text alternatives. For HTML, they may use the title attribute of the anchor, if present, or they may use the value of the src attribute of the img element.


This failure condition occurs when a link contains only non-text content, such as an image, and the non-text content has been implemented in a way that it can be ignored by assistive technology. Because a link is an interactive control, the user can tab to it and activate it. Since there is no text content within the link to be used as the name, assistive technology employs a variety of repair techniques to find some name to use for the link.

Often, both text and images are used on a page to link to the same target. This introduces a "stuttering" effect when two [begin change]adjacent[end change] links have the same name, and authors attempt to eliminate the redundancy by providing a null alt attribute for the image. Unfortunately, this often makes the problem worse. H2: Combining adjacent image and text links for the same resource (HTML) is the recommended approach to reduce the number of separate links and the undesirable redundancy.


Failure Example 1: HTML Search Results

A search site returns search results that include both a text link and an image link to the match site. The image has a null alt attribute, since the result already contains a link with a text description. However, the screen reader does not ignore the image link but uses heuristics to find some text that might describe the purpose of the link. For example, the screen reader might announce, "football dot gif Football Scorecard."

Example Code:

 <a href="scores.html">
   <img src="football.gif" alt="" />
 <a href="scores.html">
   Football Scoreboard


Resources are for information purposes only, no endorsement implied.



  1. Check whether the link contains only non-text content.

  2. Check whether the non-text content has been implemented in a way that it can be ignored by assistive technology.

Expected Results