CINXE.COM
Understanding Success Criterion 1.1.1 | Understanding WCAG 2.0
<?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" lang="en-US" xml:lang="en-US"><head><title> Understanding Success Criterion 1.1.1 | Understanding WCAG 2.0 </title><link rel="canonical" href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html" /><link media="print" type="text/css" rel="stylesheet" href="print.css"/><link rel="stylesheet" type="text/css" href="additional.css"/><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/2021/W3C-NOTE"/><link rel="stylesheet" type="text/css" href="slicenav.css"/><meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"/></head><body class="slices toc-inline"><div id="masthead"><p class="logo"><a href="https://www.w3.org/"><img width="72" height="48" alt="W3C" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C"/></a></p><p class="collectiontitle"><a href="Overview.html">Understanding WCAG 2.0</a></p></div><div id="skipnav"><p class="skipnav"><a href="#maincontent">Skip to Content (Press Enter)</a></p></div><div class="mainbody"><a name="top"> </a><!-- TOP NAVIGATION BAR --><ul id="navigation"><li><strong><a href="Overview.html#contents" title="Table of Contents">Contents</a></strong></li><li><strong><a href="intro.html" title="Introduction to Understanding WCAG 2.0"><abbr title="Introduction">Intro</abbr></a></strong></li><li><a title="Understanding Guideline 1.1 [Text Alternatives]" href="text-equiv.html"><strong>Previous: </strong>Guideline 1.1 [Text Alternatives]</a></li><li><a title="Understanding Guideline 1.2 [Time-based Media]" href="media-equiv.html"><strong>Next: </strong>Guideline 1.2 [Time-based Media]</a></li></ul><div class="navtoc"><p>On this page:</p><ul id="navbar"><li><a href="#text-equiv-all-intent-head">Intent</a></li><li><a href="#text-equiv-all-examples-head">Examples</a></li><li><a href="#text-equiv-all-resources-head">Related Resources</a></li><li><a href="#text-equiv-all-techniques-head">Techniques & Failures</a></li><li><a href="#key-terms">Key terms</a></li></ul></div> <div class="skiptarget"><a id="maincontent">-</a></div><h1><a name="text-equiv-all" id="text-equiv-all"> </a><strong>Non-text Content</strong><span class="screenreader">:</span><br/>Understanding <abbr title="Success Criterion">SC</abbr> 1.1.1</h1><blockquote class="scquote"><div> <p class="sctxt"><strong class="sc-handle"><a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#text-equiv-all">1.1.1</a> Non-text Content:</strong> All <a href="#non-text-contentdef" class="termref">non-text content</a> that is presented to the user has a <a href="#text-altdef" class="termref">text alternative</a> that serves the equivalent purpose, except for the situations listed below. (Level A) </p><ul><li><p> <strong class="sc-handle">Controls, Input: </strong> If non-text content is a control or accepts user input, then it has a <a href="#namedef" class="termref">name</a> that describes its purpose. (Refer to <em><a href="ensure-compat.html">Guideline 4.1</a></em> for additional requirements for controls and content that accepts user input.) </p></li><li><p> <strong class="sc-handle">Time-Based Media: </strong> If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to <em><a href="media-equiv.html">Guideline 1.2</a></em> for additional requirements for media.) </p></li><li><p> <strong class="sc-handle">Test: </strong> If non-text content is a test or exercise that would be invalid if presented in <a href="#textdef" class="termref">text</a>, then text alternatives at least provide descriptive identification of the non-text content. </p></li><li><p> <strong class="sc-handle">Sensory: </strong> If non-text content is primarily intended to create a <a href="#sensoryexpdef" class="termref">specific sensory experience</a>, then text alternatives at least provide descriptive identification of the non-text content. </p></li><li><p> <strong class="sc-handle"> <a href="#CAPTCHAdef" class="termref">CAPTCHA</a>: </strong>If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.</p></li><li><p> <strong class="sc-handle">Decoration, Formatting, Invisible: </strong>If non-text content is <a href="#puredecdef" class="termref">pure decoration</a>, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by <a href="#atdef" class="termref">assistive technology</a>.</p></li></ul></div></blockquote><div class="intent"><h2 id="text-equiv-all-intent-head" class="section"> Intent of this Success Criterion </h2><p>The intent of this Success Criterion is to make information conveyed by non-text content accessible through the use of a text alternative. Text alternatives are a primary way for making information accessible because they can be rendered through any sensory modality (for example, visual, auditory or tactile) to match the needs of the user. Providing text alternatives allows the information to be rendered in a variety of ways by a variety of user agents. For example, a person who cannot see a picture can have the text alternative read aloud using synthesized speech. A person who cannot hear an audio file can have the text alternative displayed so that he or she can read it. In the future, text alternatives will also allow information to be more easily translated into sign language or into a simpler form of the same language.</p><h3 id="text-equiv-all-8-head" class="div3head"> Note on CAPTCHA </h3><p> <acronym title="Completely Automated Public Turing test to tell Computers and Humans Apart">CAPTCHAs</acronym> are a controversial topic in the accessibility community. As is described in the paper <a href="https://www.w3.org/TR/turingtest/">Inaccessibility of CAPTCHA</a>, CAPTCHAs intrinsically push the edges of human abilities in an attempt to defeat automated processes. Every type of CAPTCHA will be unsolvable by users with certain disabilities. However, they are widely used, and the Web Content Accessibility Guidelines Working Group believes that if CAPTCHAs were forbidden outright, Web sites would choose not to conform to WCAG rather than abandon CAPTCHA. This would create barriers for a great many more users with disabilities. For this reason the Working Group has chosen to structure the requirement about CAPTCHA in a way that meets the needs of most people with disabilities, yet is also considered adoptable by sites. Requiring two different forms of CAPTCHA on a given site ensures that most people with disabilities will find a form they can use.</p><p>Because some users with disabilities will still not be able to access sites that meet the minimum requirements, the Working Group provides recommendations for additional steps. Organizations motivated to conform to WCAG should be aware of the importance of this topic and should go as far beyond the minimum requirements of the guidelines as possible. Additional recommended steps include:</p><ul><li><p>Providing more than two modalities of CAPTCHAs</p></li><li><p>Providing access to a human customer service representative who can bypass CAPTCHA</p></li><li><p>Not requiring CAPTCHAs for authorized users</p></li></ul><h3 id="text-equiv-all-9-head" class="div3head">Additional information</h3><p>Non-text content can take a number of forms, and this Success Criterion specifies how each is to be handled.</p><p> <strong> For non-text content that is not covered by one of the other situations listed below,</strong> such as charts, diagrams, audio recordings, pictures, and animations, text alternatives can make the same information available in a form that can be rendered through any modality (for example, visual, auditory or tactile). Short and long text alternatives can be used as needed to convey the information in the non-text content. Note that <strong> prerecorded audio-only</strong> and <strong> prerecorded video-only</strong> files are covered here. <strong> Live-audio-only</strong> and <strong> Live-video-only</strong> files are covered below (see 3rd paragraph following this one). </p><p> <strong> For non-text content that is a control or accepts user input</strong>, such as images used as submit buttons, image maps or complex animations, a name is provided to describe the purpose of the non-text content so that the person at least knows what the non-text content is and why it is there.</p><p> <strong> Non-text content that is time-based media</strong> is made accessible through <em><a href="media-equiv.html">1.2</a></em>. However, it is important that users know what it is when they encounter it on a page so they can decide what action if any they want to take with it. A text alternative that describes the time-based media and/or gives its title is therefore provided. </p><p> <strong> For Live Audio-only and live video-only content</strong>, it can be much more difficult to provide text alternatives that provide equivalent information as live audio-only and live video-only content. For these types of non-text content, text alternatives provide a descriptive label. </p><p> <strong> Sometimes a test or exercise must be partially or completely presented in non-text format.</strong> Audio or visual information is provided that cannot be changed to text because the test or exercise must be conducted using that sense. For example, a hearing test would be invalid if a text alternative were provided. A visual skill development exercise would similarly make no sense in text form. And a spelling test with text alternatives would not be very effective. For these cases, text alternatives should be provided to describe the purpose of the non-text content; of course, the text alternatives would not provide the same information needed to pass the test. </p><p> <strong> Sometimes content is primarily intended to create a specific sensory experience</strong> that words cannot fully capture. Examples include a symphony performance, works of visual art etc. For such content, text alternatives at least identify the non-text content with a descriptive label and where possible, additional descriptive text. If the reason for including the content in the page is known and can be described it is helpful to include that information. </p><p> <strong>Sometimes there are non-text exercises that are used to prove you are human.</strong> To avoid spam robots and other software from gaining access to a site a device called a CAPTCHA is used. These usually involve visual or auditory tasks that are beyond the current capabilities of Web robots. Providing a text alternative to them would however make them operable by Robots, thus defeating their purpose. In this case a text alternative would describe the purpose of the CAPTCHA, and alternate forms using different modalities would be provided to address the needs of people with different disabilities.</p><p> <strong> Sometimes there is non-text content that really is not meant to be seen or understood by the user.</strong> Transparent images used to move text over on a page; an invisible image that is used to track usage statistics; and a swirl in the corner that conveys no information but just fills up a blank space to create an aesthetic effect are all examples of this. Putting alternative text on such items just distracts people using screen readers from the content on the page. Not marking the content in any way, though, leaves users guessing what the non-text content is and what information they may have missed (even though they have not missed anything in reality). This type of non-text content, therefore, is marked or implemented in a way that assistive technologies (AT) will ignore it and not present anything to the user.</p><div class="benefits"><h3 id="text-equiv-all-10-head" class="div3head"> Specific Benefits of Success Criterion 1.1.1: </h3><ul><li><p>This Success Criterion helps people who have difficulty perceiving visual content. Assistive technology can read text aloud, present it visually, or convert it to braille.</p></li><li><p>Text alternatives may help some people who have difficulty understanding the meaning of photographs, drawings, and other images (e.g., line drawings, graphic designs, paintings, three-dimensional representations), graphs, charts, animations, etc. </p></li><li><p> People who are deaf, are hard of hearing, or who are having trouble understanding audio information for any reason can read the text presentation. Research is ongoing regarding automatic translation of text into sign language. </p></li><li><p> People who are deaf-blind can read the text in braille. </p></li><li><p> Additionally, text alternatives support the ability to search for non-text content and to repurpose content in a variety of ways. </p></li></ul></div></div><div class="div3"><h2 id="text-equiv-all-examples-head" class="section"> Examples of Success Criterion 1.1.1</h2><ol class="enumar"><li><p> <strong>A data chart</strong> </p><p>A bar chart compares how many widgets were sold in June, July, and August. The short label says, "Figure one - Sales in June, July and August." The longer description identifies the type of chart, provides a high-level summary of the data, trends and implications comparable to those available from the chart. Where possible and practical, the actual data is provided in a table. </p></li><li><p> <strong>An audio recording of a speech</strong> </p><p>The link to an audio clip says, "Chairman's speech to the assembly." A link to a text transcript is provided immediately after the link to the audio clip. </p></li><li><p> <strong>An animation that illustrates how a car engine works</strong> </p><p>An animation shows how a car engine works. There is no audio and the animation is part of a tutorial that describes how an engine works. Since the text of the tutorial already provides a full explanation, the image is an alternative for text and the text alternative includes only a brief description of the animation and refers to the tutorial text for more information. </p></li><li><p> <strong>A traffic Web camera</strong> </p><p>A Web site allows users to select from a variety of Web cameras positioned throughout a major city. After a camera is selected, the image updates every two minutes. A short text alternative identifies the Web camera as "traffic Web camera." The site also provides a table of travel times for each of the routes covered by the Web cameras. The table is also updated every two minutes. </p></li><li><p> <strong>A photograph of an historic event in a news story</strong> </p><p>A photograph of two world leaders shaking hands accompanies a news story about an international summit meeting. The text alternative says, "President X of Country X shakes hands with Prime Minister Y of country Y." </p></li><li><p> <strong>A photograph of a historic event in content discussing diplomatic relationships</strong> </p><p> The same image is used in a different context intended to explain nuances in diplomatic encounters. The image of the president shaking hands with the prime minister appears on a Web site discussing intricate diplomatic relationships. The first text alternative reads, "President X of country X shakes hands with Prime Minister Y of country Y on January 2, 2009." An additional text alternative describes the room where the leaders are standing as well as the expressions on the leaders' faces, and identifies the other people in the room. The additional description might be included on the same page as the photograph or in a separate file associated with the image through a link or other standard programmatic mechanism. </p></li><li><p> <strong>An audio recording of a press conference </strong> </p><p>A Web page includes a link to an audio recording of a press conference. The link text identifies the audio recording. The page also links to a text transcript of the press conference. The transcript includes a verbatim record of everything the speakers say. It identifies who is speaking as well as noting other significant sounds that are part of the recording, such as applause, laughter, questions from the audience, and so on. </p></li><li><p> <strong> An e-learning application </strong> </p><p> An e-learning application uses sound effects to indicate whether or not the answers are correct. The chime sound indicates that the answer is correct and the beep sound indicates that the answer is incorrect. A text description is also included so that people who can't hear or understand the sound understand whether the answer is correct or incorrect. </p></li><li><p> <strong> A linked thumbnail image </strong> </p><p>A thumbnail image of the front page of a newspaper links to the home page of the "Smallville Times". The text alternative says "Smallville Times". </p></li><li><p> <strong> The same image used on different sites </strong> </p><p>Different alternatives for an image of the world: An image of the world that is used on a travel site as a link to the International Travel section has the text alternative "International Travel". The same image is used as a link on a university Web site with the text alternative "International Campuses". </p></li><li><p> <strong> An image map </strong> </p><p>An image of a building floor plan is interactive, allowing the user to select a particular room and navigate to a page containing information about that room. The short text alternative describes the image and its interactive purpose: "Building floor plan. Select a room for more information."</p></li></ol></div><div class="resources"><h2 id="text-equiv-all-resources-head" class="section"> Related Resources </h2><p>Resources are for information purposes only, no endorsement implied.</p><ul><li><p> <a href="https://www.w3.org/2000/08/nba-manual/Overview.html">Excerpts from the NBA Tape Recording Manual, Third Edition</a> </p></li><li><p> <a href="https://www.w3.org/TR/turingtest/">Inaccessibility of CAPTCHA</a> </p></li><li><p> <a href="https://stuffandnonsense.co.uk/archives/accessible_alternatives.html">All That Malarkey: Accessible Alternatives</a> </p></li><li><p> <a href="http://www.456bereastreet.com/archive/200412/the_alt_and_title_attributes/">456 Berea Street: The Alt and Title Attributes</a> </p></li><li><p> <a href="http://green-beast.com/blog/?p=81">The Alt and Accessibility</a> </p></li><li><p> <a href="http://www.accessibilitynews.ca/cwdo/resources/resources.php?resources=187">Better Connected, Better Results: Alt Text</a> </p></li></ul></div><div class="div3"><h2 id="text-equiv-all-techniques-head" class="section"> Techniques and Failures for Success Criterion 1.1.1 - Non-text Content</h2><p>Each numbered item in this section represents a technique or combination of techniques that the <acronym title="Web Content Accessibility Guidelines">WCAG</acronym> Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques. For information on using other techniques, see <a href="https://www.w3.org/TR/2023/NOTE-UNDERSTANDING-WCAG20-20230921/understanding-techniques.html">Understanding Techniques for WCAG Success Criteria</a>, particularly the "Other Techniques" section.</p><div class="boxed"><h3 id="text-equiv-all-11-head" class="div3head"> Sufficient Techniques </h3><p class="instructions"><strong>Instructions:</strong> Select the situation below that matches your content. Each situation includes techniques or combinations of techniques that are known and documented to be sufficient for that situation. </p><div><h4><a name="text-equiv-all-situation-1-head" id="text-equiv-all-situation-1-head"> </a>Situation A: If a short description can serve the same purpose and present the same information as the non-text content:</h4> <ol class="enumar"><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G94" class="tech-ref">G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content</a> using one of the following <strong> <a href="#text-equiv-all-situation-a-shorttext">Short text alternative techniques for Situation A</a> </strong>:</p></li></ol><p id="text-equiv-all-situation-a-shorttext"> <strong>Short text alternative techniques for Situation A</strong>:</p><ul><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA6" class="tech-ref">ARIA6: Using aria-label to provide labels for objects</a> (ARIA) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA10" class="tech-ref">ARIA10: Using aria-labelledby to provide a text alternative for non-text content</a> (ARIA) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G196" class="tech-ref">G196: Using a text alternative on one item within a group of images that describes all items in the group</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH1" class="tech-ref">FLASH1: Setting the name property for a non-text object</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH5" class="tech-ref">FLASH5: Combining adjacent image and text buttons for the same resource</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH28" class="tech-ref">FLASH28: Providing text alternatives for ASCII art, emoticons, and leetspeak in Flash</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H2" class="tech-ref">H2: Combining adjacent image and text links for the same resource</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H35" class="tech-ref">H35: Providing text alternatives on applet elements </a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H37" class="tech-ref">H37: Using alt attributes on img elements</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H53" class="tech-ref">H53: Using the body of the object element</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H86" class="tech-ref">H86: Providing text alternatives for ASCII art, emoticons, and leetspeak</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/PDF1" class="tech-ref">PDF1: Applying text alternatives to images with the Alt entry in PDF documents</a> (PDF) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/SL5" class="tech-ref">SL5: Defining a Focusable Image Class for Silverlight</a> (Silverlight) </p></li></ul></div><div><h4><a name="text-equiv-all-situation-2-head" id="text-equiv-all-situation-2-head"> </a>Situation B: If a short description can <strong>not</strong> serve the same purpose and present the same information as the non-text content (e.g., a chart or diagram):</h4> <ol class="enumar"><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G95" class="tech-ref">G95: Providing short text alternatives that provide a brief description of the non-text content</a> using one of the following <strong> <a href="#text-equiv-all-situation-b-shorttext">Short text alternative techniques for Situation B</a> </strong> <strong>AND</strong> one of the following <strong> <a href="#text-equiv-all-situation-b-longtext">Long text alternative techniques for Situation B</a> </strong>:</p></li></ol><p id="text-equiv-all-situation-b-shorttext"> <strong>Short text alternative techniques for Situation B</strong>:</p><ul><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA6" class="tech-ref">ARIA6: Using aria-label to provide labels for objects</a> (ARIA) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA10" class="tech-ref">ARIA10: Using aria-labelledby to provide a text alternative for non-text content</a> (ARIA) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G196" class="tech-ref">G196: Using a text alternative on one item within a group of images that describes all items in the group</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH1" class="tech-ref">FLASH1: Setting the name property for a non-text object</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH5" class="tech-ref">FLASH5: Combining adjacent image and text buttons for the same resource</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH28" class="tech-ref">FLASH28: Providing text alternatives for ASCII art, emoticons, and leetspeak in Flash</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H2" class="tech-ref">H2: Combining adjacent image and text links for the same resource</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H35" class="tech-ref">H35: Providing text alternatives on applet elements </a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H37" class="tech-ref">H37: Using alt attributes on img elements</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H53" class="tech-ref">H53: Using the body of the object element</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H86" class="tech-ref">H86: Providing text alternatives for ASCII art, emoticons, and leetspeak</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/PDF1" class="tech-ref">PDF1: Applying text alternatives to images with the Alt entry in PDF documents</a> (PDF) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/SL5" class="tech-ref">SL5: Defining a Focusable Image Class for Silverlight</a> (Silverlight) </p></li></ul><p id="text-equiv-all-situation-b-longtext"> <strong>Long text alternative techniques for Situation B</strong>:</p><ul><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA15" class="tech-ref">ARIA15: Using aria-describedby to provide descriptions of images</a> (ARIA) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G73" class="tech-ref">G73: Providing a long description in another location with a link to it that is immediately adjacent to the non-text content</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G74" class="tech-ref">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</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G92" class="tech-ref">G92: Providing long description for non-text content that serves the same purpose and presents the same information</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH2" class="tech-ref">FLASH2: Setting the description property for a non-text object in Flash</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH11" class="tech-ref">FLASH11: Providing a longer text description of an object</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H45" class="tech-ref">H45: Using longdesc</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H53" class="tech-ref">H53: Using the body of the object element</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/SL8" class="tech-ref">SL8: Displaying HelpText in Silverlight User Interfaces</a> (Silverlight) </p></li></ul></div><div><h4><a name="text-equiv-all-situation-3-head" id="text-equiv-all-situation-3-head"> </a>Situation C: If non-text content is a control or accepts user input:</h4> <ol class="enumar"><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G82" class="tech-ref">G82: Providing a text alternative that identifies the purpose of the non-text content</a> using one of the following <strong> <a href="#text-equiv-all-situation-c-controls">Text alternative techniques for controls and input for Situation C</a> </strong>:</p></li></ol><p id="text-equiv-all-situation-c-controls"> <strong>Text alternative techniques for controls and input for Situation C</strong>:</p><ul><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA6" class="tech-ref">ARIA6: Using aria-label to provide labels for objects</a> (ARIA) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA9" class="tech-ref">ARIA9: Using aria-labelledby to concatenate a label from several text nodes</a> (ARIA) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH6" class="tech-ref">FLASH6: Creating accessible hotspots using invisible buttons</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH25" class="tech-ref">FLASH25: Labeling a form control by setting its accessible name</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH27" class="tech-ref">FLASH27: Providing button labels that describe the purpose of a button</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH29" class="tech-ref">FLASH29: Setting the label property for form components</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH30" class="tech-ref">FLASH30: Specifying accessible names for image buttons</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH32" class="tech-ref">FLASH32: Using auto labeling to associate text labels with form controls</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H24" class="tech-ref">H24: Providing text alternatives for the area elements of image maps </a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H30" class="tech-ref">H30: Providing link text that describes the purpose of a link for anchor elements</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H36" class="tech-ref">H36: Using alt attributes on images used as submit buttons</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H44" class="tech-ref">H44: Using label elements to associate text labels with form controls</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H65" class="tech-ref">H65: Using the title attribute to identify form controls when the label element cannot be used</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/SL18" class="tech-ref">SL18: Providing Text Equivalent for Nontext Silverlight Controls With AutomationProperties.Name</a> (Silverlight) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/SL26" class="tech-ref">SL26: Using LabeledBy to Associate Labels and Targets in Silverlight</a> (Silverlight) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/SL30" class="tech-ref">SL30: Using Silverlight Control Compositing and AutomationProperties.Name</a> (Silverlight) </p></li></ul></div><div><h4><a name="text-equiv-all-situation-4-head" id="text-equiv-all-situation-4-head"> </a>Situation D: If non-text content is time-based media (including live video-only and live audio-only); a test or exercise that would be invalid if presented in text; or primarily intended to create a specific sensory experience:</h4> <ol class="enumar"><li><p>Providing a descriptive label using one of the following <strong> <a href="#text-equiv-all-situation-d-shorttext">Short text alternative techniques for Situation D</a> </strong>:</p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G68" class="tech-ref">G68: Providing a short text alternative that describes the purpose of live audio-only and live video-only content</a> using one of the following <strong> <a href="#text-equiv-all-situation-d-shorttext">Short text alternative techniques for Situation D</a> </strong>:</p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G100" class="tech-ref">G100: Providing a short text alternative which is the accepted name or a descriptive name of the non-text content</a> using one of the following <strong> <a href="#text-equiv-all-situation-d-shorttext">Short text alternative techniques for Situation D</a> </strong>:</p></li></ol><p id="text-equiv-all-situation-d-shorttext"> <strong>Short text alternative techniques for Situation D</strong>:</p><ul><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA6" class="tech-ref">ARIA6: Using aria-label to provide labels for objects</a> (ARIA) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA10" class="tech-ref">ARIA10: Using aria-labelledby to provide a text alternative for non-text content</a> (ARIA) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G196" class="tech-ref">G196: Using a text alternative on one item within a group of images that describes all items in the group</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH1" class="tech-ref">FLASH1: Setting the name property for a non-text object</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH5" class="tech-ref">FLASH5: Combining adjacent image and text buttons for the same resource</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH28" class="tech-ref">FLASH28: Providing text alternatives for ASCII art, emoticons, and leetspeak in Flash</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H2" class="tech-ref">H2: Combining adjacent image and text links for the same resource</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H35" class="tech-ref">H35: Providing text alternatives on applet elements </a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H37" class="tech-ref">H37: Using alt attributes on img elements</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H53" class="tech-ref">H53: Using the body of the object element</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H86" class="tech-ref">H86: Providing text alternatives for ASCII art, emoticons, and leetspeak</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/PDF1" class="tech-ref">PDF1: Applying text alternatives to images with the Alt entry in PDF documents</a> (PDF) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/SL5" class="tech-ref">SL5: Defining a Focusable Image Class for Silverlight</a> (Silverlight) </p></li></ul></div><div><h4><a name="text-equiv-all-situation-5-head" id="text-equiv-all-situation-5-head"> </a>Situation E: If non-text content is a CAPTCHA:</h4> <ol class="enumar"><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G143" class="tech-ref">G143: Providing a text alternative that describes the purpose of the CAPTCHA</a> <strong>AND</strong> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G144" class="tech-ref">G144: Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality</a> </p></li></ol></div><div><h4><a name="text-equiv-all-situation-6-head" id="text-equiv-all-situation-6-head"> </a>Situation F: If the non-text content should be ignored by assistive technology:</h4> <ol class="enumar"><li><p>Implementing or marking the non-text content so that it will be ignored by assistive technology using one of the following <strong> <a href="#text-equiv-all-situation-f-notrequired">Techniques to indicate that text alternatives are not required for Situation F</a> </strong>:</p></li></ol><p id="text-equiv-all-situation-f-notrequired"> <strong>Techniques to indicate that text alternatives are not required for Situation F</strong>:</p><ul><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/C9" class="tech-ref">C9: Using CSS to include decorative images</a> (CSS) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/FLASH3" class="tech-ref">FLASH3: Marking objects in Flash so that they can be ignored by AT</a> (Flash) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H67" class="tech-ref">H67: Using null alt text and no title attribute on img elements for images that AT should ignore</a> (HTML) </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/PDF4" class="tech-ref">PDF4: Hiding decorative images with the Artifact tag in PDF documents</a> (PDF) </p></li></ul></div></div><div class="boxed"><h3 id="text-equiv-all-12-head" class="div3head"> Additional Techniques (Advisory) for 1.1.1</h3><p>Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.</p><div><h4><a name="text-equiv-all-section-7-head" id="text-equiv-all-section-7-head"> </a>General Techniques for Informative Non-Text Content (Advisory)</h4> <ul><li><p>Identifying informative non-text content (future link)</p></li><li><p>Keeping short descriptions short (future link)</p></li><li><p>Describing images that include text (future link)</p></li><li><p>Providing a longer description of the non-text content where only a descriptive label is required using a technology-specific technique (for an accessibility-supported content technology) for long description listed above (future link)</p></li><li><p>Providing different sizes for non-text content when it cannot have an equivalent accessible alternative (future link)</p></li><li><p>Using server-side scripts to resize images of text (future link)</p></li></ul></div><div><h4><a name="text-equiv-all-section-8-head" id="text-equiv-all-section-8-head"> </a>General Techniques for Live Non-Text Content (Advisory)</h4> <ul><li><p>Linking to textual information that provides comparable information (e.g., for a traffic Webcam, a municipality could provide a link to the text traffic report.) (future link)</p></li></ul></div><div><h4><a name="text-equiv-all-section-9-head" id="text-equiv-all-section-9-head"> </a>General techniques to minimize the barrier of CAPTCHAs</h4> <ul><li><p>Providing more than two modalities of CAPTCHAs (future link)</p></li><li><p>Providing access to a human customer service representative who can bypass CAPTCHA (future link)</p></li><li><p>Not requiring CAPTCHAs for authorized users (future link)</p></li></ul></div><div><h4><a name="text-equiv-all-section-10-head" id="text-equiv-all-section-10-head"> </a>HTML Techniques (Advisory)</h4> <ul><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H46" class="tech-ref">H46: Using noembed with embed </a> (HTML) </p></li><li><p> Writing for browsers that do not support frame (future link) </p></li><li><p> Providing alternative content for iframe (future link) </p></li><li><p> Not using long descriptions for iframe (future link) </p></li><li><p> Providing redundant text links for client-side image maps (future link) </p></li></ul></div><div><h4><a name="text-equiv-all-section-11-head" id="text-equiv-all-section-11-head"> </a>CSS Techniques (Advisory)</h4> <ul><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/C18" class="tech-ref">C18: Using CSS margin and padding rules instead of spacer images for layout design</a> (CSS) </p></li><li><p> Using CSS background, :before or :after rules for decorative images instead of img elements (future link) </p></li><li><p>Displaying empty table cells (future link)</p></li></ul></div><div><h4><a name="text-equiv-all-section-12-head" id="text-equiv-all-section-12-head"> </a>WAI-ARIA Techniques (Advisory)</h4> <ul><li><p>Using the ARIA presentation role to indicate elements are purely presentational (future link) </p></li></ul></div><div><h4><a name="text-equiv-all-section-13-head" id="text-equiv-all-section-13-head"> </a>Silverlight Techniques (Advisory)</h4> <ul><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/SL19" class="tech-ref">SL19: Providing User Instructions With AutomationProperties.HelpText in Silverlight</a> (Silverlight) </p></li></ul></div><div><h4><a name="text-equiv-all-section-14-head" id="text-equiv-all-section-14-head"> </a>Metadata Techniques (Advisory)</h4> <ul><li><p> Using metadata to associate text transcriptions with a video (future link) </p></li><li><p> Using metadata to associate text transcriptions with audio-only content (future link)</p><ul><li><p> EXAMPLE: Providing, in metadata, URI(s) that points to an audio description and a text transcript of a video. </p></li><li><p> EXAMPLE: Providing, in metadata, URI(s) that point to several text transcripts (English, French, Dutch) of an audio file. </p></li></ul></li></ul></div></div><div class="boxed"><h3 id="text-equiv-all-13-head" class="div3head"> Common Failures for <abbr title="Success Criterion">SC</abbr> 1.1.1</h3><p>The following are common mistakes that are considered failures of Success Criterion 1.1.1 by the <acronym title="Web Content Accessibility Guidelines">WCAG</acronym> Working Group.</p><ul><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F3" class="tech-ref">F3: Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F13" class="tech-ref">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</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F20" class="tech-ref">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</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F30" class="tech-ref">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)</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F38" class="tech-ref">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</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F39" class="tech-ref">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</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F65" class="tech-ref">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"</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F67" class="tech-ref">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</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F71" class="tech-ref">F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative</a> </p></li><li><p> <a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F72" class="tech-ref">F72: Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative</a> </p></li></ul></div></div><div class="div3"><h2 id="key-terms" class="terms">Key Terms</h2><dl class="keyterms"><dt class="label"><a name="CAPTCHAdef" id="CAPTCHAdef"> </a>CAPTCHA</dt><dd><p>initialism for "Completely Automated Public Turing test to tell Computers and Humans Apart"</p><div class="note"><p class="prefix"><em>Note 1: </em>CAPTCHA tests often involve asking the user to type in text that is displayed in an obscured image or audio file.</p><p class="prefix"><em>Note 2: </em>A Turing test is any system of tests designed to differentiate a human from a computer. It is named after famed computer scientist Alan Turing. The term was coined by researchers at Carnegie Mellon University. <a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#CAPTCHA">[CAPTCHA]</a> </p></div></dd><dt class="label"><a name="atdef" id="atdef"> </a>assistive technology (as used in this document)</dt><dd><p>hardware and/or software that acts as a <a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#useragentdef" class="termref">user agent</a>, or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents </p><div class="note"><p class="prefix"><em>Note 1: </em> functionality provided by assistive technology includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation mechanisms, and content transformations (e.g., to make tables more accessible). </p><p class="prefix"><em>Note 2: </em>Assistive technologies often communicate data and messages with mainstream user agents by using and monitoring <acronym title="Application Programming Interfaces">APIs</acronym>. </p><p class="prefix"><em>Note 3: </em>The distinction between mainstream user agents and assistive technologies is not absolute. Many mainstream user agents provide some features to assist individuals with disabilities. The basic difference is that mainstream user agents target broad and diverse audiences that usually include people with and without disabilities. Assistive technologies target narrowly defined populations of users with specific disabilities. The assistance provided by an assistive technology is more specific and appropriate to the needs of its target users. The mainstream user agent may provide important functionality to assistive technologies like retrieving Web content from program objects or parsing markup into identifiable bundles. </p></div><div class="example"><p class="prefix"><em>Example: </em>Assistive technologies that are important in the context of this document include the following:</p><ul><li><p>screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order to improve the visual readability of rendered text and images;</p></li><li><p>screen readers, which are used by people who are blind to read textual information through synthesized speech or braille;</p></li><li><p>text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech;</p></li><li><p>speech recognition software, which may be used by people who have some physical disabilities;</p></li><li><p>alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices.);</p></li><li><p>alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations.</p></li></ul></div></dd><dt class="label"><a name="namedef" id="namedef"> </a>name</dt><dd><p>text by which software can identify a component within Web content to the user</p><div class="note"><p class="prefix"><em>Note 1: </em>The name may be hidden and only exposed by assistive technology, whereas a <a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#labeldef" class="termref">label</a> is presented to all users. In many (but not all) cases, the label and the name are the same. </p><p class="prefix"><em>Note 2: </em>This is unrelated to the name attribute in HTML.</p></div></dd><dt class="label"><a name="non-text-contentdef" id="non-text-contentdef"> </a>non-text content</dt><dd><p>any content that is not a sequence of characters that can be <a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#programmaticallydetermineddef" class="termref">programmatically determined</a> or where the sequence is not expressing something in <a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#human-langdef" class="termref">human language</a> </p><div class="note"><p class="prefix"><em>Note: </em>This includes <a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#asciiartdef" class="termref">ASCII Art</a> (which is a pattern of characters), emoticons, leetspeak (which uses character substitution), and images representing text</p></div></dd><dt class="label"><a name="puredecdef" id="puredecdef"> </a>pure decoration</dt><dd><p>serving only an aesthetic purpose, providing no information, and having no functionality</p><div class="note"><p class="prefix"><em>Note: </em>Text is only purely decorative if the words can be rearranged or substituted without changing their purpose.</p></div><div class="example"><p class="prefix"><em>Example: </em>The cover page of a dictionary has random words in very light text in the background.</p></div></dd><dt class="label"><a name="sensoryexpdef" id="sensoryexpdef"> </a>specific sensory experience</dt><dd><p>a sensory experience that is not purely decorative and does not primarily convey important information or perform a function</p><div class="example"><p class="prefix"><em>Example: </em> Examples include a performance of a flute solo, works of visual art etc. </p></div></dd><dt class="label"><a name="textdef" id="textdef"> </a>text</dt><dd><p>sequence of characters that can be <a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#programmaticallydetermineddef" class="termref">programmatically determined</a>, where the sequence is expressing something in <a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#human-langdef" class="termref">human language</a> </p></dd><dt class="label"><a name="text-altdef" id="text-altdef"> </a>text alternative</dt><dd><p><a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#textdef" class="termref">Text</a> that is programmatically associated with <a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#non-text-contentdef" class="termref">non-text content</a> or referred to from text that is programmatically associated with non-text content. Programmatically associated text is text whose location can be programmatically determined from the non-text content.</p><div class="example"><p class="prefix"><em>Example: </em>An image of a chart is described in text in the paragraph after the chart. The short text alternative for the chart indicates that a description follows. </p></div><div class="note"><p class="prefix"><em>Note: </em>Refer to <a href="conformance.html#uc-text-alternatives-head" class="understanding-ref">Understanding Text Alternatives</a> for more information.</p></div></dd></dl></div><!-- BOTTOM NAVIGATION BAR --><ul id="navigationbottom"><li><strong><a href="#top">Top</a></strong></li><li><strong><a href="Overview.html#contents" title="Table of Contents">Contents</a></strong></li><li><strong><a href="intro.html" title="Introduction to Understanding WCAG 2.0"><abbr title="Introduction">Intro</abbr></a></strong></li><li><a title="Understanding Guideline 1.1 [Text Alternatives]" href="text-equiv.html"><strong>Previous: </strong>Guideline 1.1 [Text Alternatives]</a></li><li><a title="Understanding Guideline 1.2 [Time-based Media]" href="media-equiv.html"><strong>Next: </strong>Guideline 1.2 [Time-based Media]</a></li></ul></div><div class="footer"><p class="copyright">This Web page is part of <a href="Overview.html">Understanding WCAG 2.0: A guide to understanding and implementing WCAG 2.0</a> (see the <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html">latest version of this document</a>). The entire document is also available as a <a href="complete.html">single HTML file</a>. See the <a href="https://www.w3.org/WAI/intro/wcag20">The WCAG 2.0 Documents</a> for an explanation of how this document fits in with other Web Content Accessibility Guidelines (WCAG) 2.0 documents. To send public comments, please follow the <a href="https://www.w3.org/WAI/WCAG20/comments/">Instructions for Commenting on WCAG 2.0 Documents</a>. </p><p class="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> 漏 2023 <a href="https://www.w3.org/">World Wide Web Consortium</a>. <abbr title="World Wide Web Consortium">W3C</abbr><sup>庐</sup> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div></body></html>