Perceivable / 1.1 Text Alternatives
1.1.1Non-text Content
Level ANon-text content such as images, icons, and diagrams needs a text alternative that serves the same purpose. It lets text-based assistive technologies, like screen readers and braille displays, convey the same information, while purely decorative elements should instead be hidden from assistive technology. For cases like CAPTCHAs or tests where a full alternative would defeat the purpose, a short identifying description is enough.
Note
A detailed commentary for this success criterion is not yet available. In the meantime, this page lists related patterns, techniques, and links to the normative sources.
Related Techniques
Specific implementation techniques for meeting this success criterion. This site doesn't include the full text, so follow the links to the original W3C documents.
Sufficient Techniques(28)
Show all (28)
- ARIA6: Using aria-label to provide labels for objects(opens in a new tab)waic.jp(opens in a new tab)
- ARIA9: Using aria-labelledby to concatenate a name from several text nodes(opens in a new tab)waic.jp(opens in a new tab)
- ARIA10: Using aria-labelledby to provide a text alternative for non-text content(opens in a new tab)waic.jp(opens in a new tab)
- ARIA15: Using aria-describedby to provide descriptions of images(opens in a new tab)waic.jp(opens in a new tab)
- C9: Using CSS to include decorative images(opens in a new tab)waic.jp(opens in a new tab)
- G68: Providing a short text alternative that describes the purpose of live audio-only and live video-only content(opens in a new tab)waic.jp(opens in a new tab)
- G73: Providing a long description in another location with a link to it that is immediately adjacent to the non-text content(opens in a new tab)waic.jp(opens in a new tab)
- G74: Providing a long description in text near the non-text content, with a reference to the location of the long description in the short description(opens in a new tab)waic.jp(opens in a new tab)
- G82: Providing a text alternative that identifies the purpose of interactive non-text content(opens in a new tab)waic.jp(opens in a new tab)
- G92: Providing long description for non-text content that serves the same purpose and presents the same information(opens in a new tab)waic.jp(opens in a new tab)
- G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content(opens in a new tab)waic.jp(opens in a new tab)
- G95: Providing short text alternatives that provide a brief description of the non-text content(opens in a new tab)waic.jp(opens in a new tab)
- G100: Providing a short text alternative which is the accepted name or a descriptive name of the non-text content(opens in a new tab)waic.jp(opens in a new tab)
- G143: Providing a text alternative that describes the purpose of the CAPTCHA(opens in a new tab)waic.jp(opens in a new tab)
- G144: Ensuring that the web page contains another CAPTCHA serving the same purpose using a different modality(opens in a new tab)waic.jp(opens in a new tab)
- G196: Using a text alternative on one item within a group of images that describes all items in the group(opens in a new tab)waic.jp(opens in a new tab)
- H2: Combining adjacent image and text links for the same resource(opens in a new tab)waic.jp(opens in a new tab)
- H24: Providing text alternatives for the area elements of image maps(opens in a new tab)waic.jp(opens in a new tab)
- H30: Providing link text that describes the purpose of a link for anchor elements(opens in a new tab)waic.jp(opens in a new tab)
- H36: Using alt attributes on images used as submit buttons(opens in a new tab)waic.jp(opens in a new tab)
- H37: Using alt attributes on img elements(opens in a new tab)waic.jp(opens in a new tab)
- H44: Using label elements to associate text labels with form controls(opens in a new tab)waic.jp(opens in a new tab)
- H53: Using the body of the object element(opens in a new tab)waic.jp(opens in a new tab)
- H65: Using the title attribute to identify form controls when the label element cannot be used(opens in a new tab)waic.jp(opens in a new tab)
- H67: Using null alt text and no title attribute on img elements for images that assistive technology should ignore(opens in a new tab)waic.jp(opens in a new tab)
- H86: Providing text alternatives for emojis, emoticons, ASCII art, and leetspeak(opens in a new tab)waic.jp(opens in a new tab)
- PDF1: Applying text alternatives to images with the Alt entry in PDF documents(opens in a new tab)waic.jp(opens in a new tab)
- PDF4: Hiding decorative images with the Artifact tag in PDF documents(opens in a new tab)waic.jp(opens in a new tab)
Advisory Techniques(1)
Failures(10)
Show all (10)
- F3: Failure of Success Criterion 1.1.1 due to conveying information exclusively using CSS background images(opens in a new tab)waic.jp(opens in a new tab)
- F13: Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alternative that does not include information that is conveyed by color differences in the image(opens in a new tab)waic.jp(opens in a new tab)
- F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur(opens in a new tab)waic.jp(opens in a new tab)
- F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text)(opens in a new tab)waic.jp(opens in a new tab)
- F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows assistive technology to ignore them(opens in a new tab)waic.jp(opens in a new tab)
- F39: Failure of Success Criterion 1.1.1 due to providing a text alternative that is not null (e.g., alt="spacer" or alt="image") for images that should be ignored by assistive technology(opens in a new tab)waic.jp(opens in a new tab)
- F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image"(opens in a new tab)waic.jp(opens in a new tab)
- F67: Failure of Success Criterion 1.1.1 and 1.2.1 due to providing long descriptions for non-text content that does not serve the same purpose or does not present the same information(opens in a new tab)waic.jp(opens in a new tab)
- F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative(opens in a new tab)waic.jp(opens in a new tab)
- F72: Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative(opens in a new tab)waic.jp(opens in a new tab)
Normative References
- Success Criterion 1.1.1 Non-text Content — WCAG 2.2(opens in a new tab)The normative requirement text.
- Understanding Non-text Content — W3C(opens in a new tab)Official guidance on intent, examples, and techniques.