CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>WebAIM: Alt text and linked images</title> <link rel="shortcut icon" href="/media/favicon.ico"> <link rel="home" href="/"> <link rel="search" href="/search/"> <link rel="alternate" href="https://webaim.org/blog/feed" type="application/rss+xml" title="WebAIM Blog"> <script async src="https://www.googletagmanager.com/gtag/js?id=G-Y41PF8WV9X"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'G-Y41PF8WV9X'); </script> <link href="/styles/main.css" rel="stylesheet" type="text/css"> <link href="/styles/print.css" rel="stylesheet" type="text/css" media="print"> <script src="/media/scripts/jquery.js"></script> <script src="/media/scripts/main.js"></script> <link href='https://fonts.googleapis.com/css?family=Roboto:400' rel='stylesheet' type='text/css'> <link href='https://fonts.googleapis.com/css?family=Kameron:400,700' rel='stylesheet' type='text/css'> <link href="/styles/documents.css?ver=2" rel="stylesheet"> <link href="https://fonts.googleapis.com/css?family=Open+Sans:400,400i,700" rel="stylesheet">  </head> <body> <div id="headcontainer" class="clearfix" style="background-image: url(/media/banners/community.jpg)"> <header> <div id="skiptocontent"><a href="#maincontent">skip to main content</a></div> <h2><a href="/"><img src="/media/logo.png" width="315" height="83" alt="WebAIM - Web Accessibility In Mind"></a></h2> <nav> <h2 class="hidden">Main Navigation</h2> <ul> <li><a href="/services/">Services</a></li> <li><a href="/articles/">Articles</a></li> <li><a href="/resources/">Resources</a></li> <li><a href="/projects/">Projects</a></li> <li class="current"><a href="/community/">Community</a></li> </ul> </nav> <div id="search"> <form method="get" role="search" action="/search/" id="sitesearch"> <p class="search"><span><label for="q">Search:</label> <input type="text" name="q" id="q"><input type="image" src="/media/template/search.svg" alt="Submit Search"></span></p> </form> <p class="intro"><a href="/intro">Introduction to Web Accessibility</a></p> <p class="training"><a href="/services/training">WebAIM Training</a></p> </div> </header> </div> <main id="maincontainer" class="clearfix"> <article id="maincontent"> <h1>Alt text and linked images</h1> <p id="breadcrumbs"><span class="hidden">You are here: </span><a href="/">Home</a> > <a href="/blog/">Blog</a> > Alt text and linked images</p> <div class="section post" id="post-46"> <div class="entry"> <p>Alternative text for images is rule number one of web accessibility. While the lack of <a href="https://webaim.org/techniques/alttext/">appropriate alternative text</a> is perhaps the biggest barrier to accessibility for screen reader users, I have noticed a tremendous increase in the use of alternative text and thus, general web accessibility, in recent years. However, I am now noticing a very alarming trend of missing or inappropriate alternative text for images within links.</p> <p>When an image has no alt attribute or if the alt attribute is empty or null (alt=””), screen readers essentially ignore those images. Decorative images should be given empty or null alt text. When the content presented in an image is conveyed elsewhere, such as in a caption, the image may also be given empty alt text. <strong>However, any time an image is the only content within a link, the image <em>MUST</em> be given alternative text that presents the function of that link.</strong></p> <p>Consider the following, examples that may be found in an online photo album.</p> <div class="example" style="text-align:center; padding:4px;"> <img decoding="async" src="https://webaim.org/blog/media/lightning.jpg" alt="" /><br /> Photo of an amazing lightning storm </div> <p>In this case, the content of the image is presented in the caption, so the image may be given empty alt text.</p> <div class="example" style="text-align:center; padding:4px;"> <a href="https://flickr.com/photos/jaredsmith/216180272/"><img decoding="async" src="https://webaim.org/blog/media/lightning.jpg" alt="" /></a><br /> Photo of an amazing lightning storm </div> <p>In the above example, the image itself is a link. When a screen reader encounters a link, it must present <em>something</em> to the user. For text links, it would typically identify that a link is present and then read the text within the anchor element. When the content of the link is an image that does not have alternative text, the screen reader has no content to identify for the link. As a result, screen readers will typically read either the image file name or the URL of the page being linked to. In most cases, this is of little or no value to the user – or even worse, it makes the page even more inaccessible than if the link and image had been ignored altogether.</p> <p>Presentation of linked images are becoming more prevalent, yet they rarely have appropriate alternative text. </p> <p>In the situation above, one solution would be to duplicate the caption within the alternative text of the image. This will result in redundancy – the screen reader would read something like, “Link. Photo of an amazing lightning storm. Photo of an amazing lightning storm.” An even better solution is to place both the image AND the caption within the link.</p> <div class="example" style="text-align:center; padding:4px;"> <a href="http://flickr.com/photos/jaredsmith/216180272/" style="text-decoration:none;"><img decoding="async" src="https://webaim.org/blog/media/lightning.jpg" alt="" /><br /> <span style="text-decoration:underline;">Photo of an amazing lightning storm</span></a> </div> <p>In the above example, because text within the link provides the content of the image and the function of the link, the image itself can be given an empty alt value.</p> <p>The HTML 5 working group is currently proposing that the alt attribute be made optional for images. The argument is that screen readers ignore images that have no alt attribute, so there is little justification in requiring the attribute for images that do not need it. This argument is quite sound, although I believe that this would promote a much more lax approach to accessibility and will result in more content-conveying images that do not have appropriate alternative text. But when an image is the only element within a link, it must have alternative text so that the function of the link is provided to all users. Unless the HTML 5 specification explicitly requires this, their proposal that the alt attribute be made optional will certainly cultivate an environment where accessibility is decreased.</p> </div> </div> <div class="navigation"> <div class="floatleft"></div> <div class="floatright"></div> </div>  <div id="blogcomments"> <h2 id="comments">Comments</h2> <div class="navigation"> <div class="alignleft"></div> <div class="alignright"></div> </div> <ol class="commentlist"> <li class="comment even thread-even depth-1" id="comment-49668"> <img alt='' src='https://secure.gravatar.com/avatar/b240f20619cf16e63297242f8f01908b?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/b240f20619cf16e63297242f8f01908b?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn"><a href="http://curbcut.net" class="url" rel="ugc external nofollow">Christopher Phillips</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-49668"> November 12, 2007</a></div> <div class="comment-content"><p>Alt text is often mentioned as a simple technique to make make content more accessible for developers unfamiliar with accessibility issues. The reality it can be complicated- use alt text, unless it is decorative except where the decorative image is a link. </p> <p>If the working group decides to forgo the waive the requirement for alt text, then it will be imperative on accessibility community to promote a better awareness of the different between decorative images vs images that add contain meaningful content.</p> </div> </li> </li> <li class="comment odd alt thread-odd thread-alt depth-1" id="comment-49669"> <img alt='' src='https://secure.gravatar.com/avatar/46567274cbadbd9ce47d1d02d7ea23e6?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/46567274cbadbd9ce47d1d02d7ea23e6?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn">Frederick Yocum</cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-49669"> November 12, 2007</a></div> <div class="comment-content"><p>What happens if the enclosing link tag has a title tag?<br /> <a href="somefile.htm" title="Link to some file" rel="nofollow"></a><br /> Is the title tag on the link read by screen readers?</p> </div> </li> </li> <li class="comment even thread-even depth-1" id="comment-49677"> <img alt='' src='https://secure.gravatar.com/avatar/5375b1b830a01f1b6a894eea985ce7b8?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/5375b1b830a01f1b6a894eea985ce7b8?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn"><a href="http://www.fairytells.net" class="url" rel="ugc external nofollow">goetsu</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-49677"> November 14, 2007</a></div> <div class="comment-content"><p>no frederick the title is not read with the default configuration in most of the screenreader (even with text link)</p> </div> </li> </li> <li class="comment odd alt thread-odd thread-alt depth-1" id="comment-49678"> <img alt='' src='https://secure.gravatar.com/avatar/5375b1b830a01f1b6a894eea985ce7b8?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/5375b1b830a01f1b6a894eea985ce7b8?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn"><a href="http://www.fairytells.net" class="url" rel="ugc external nofollow">goetsu</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-49678"> November 14, 2007</a></div> <div class="comment-content"><p>“When the content presented in an image is conveyed elsewhere, such as in a caption, the image may also be given empty alt text.”</p> <p>For information I have done a comment on this case during the wcag 2 period and their response is that I can’t do such thing even if the caption is just after the image. The image need to have at minimum an alt to say “the description is just after this image” otherwise if I use an empty alt the image is not announced so it can be tricky to know from what is the description</p> </div> </li> </li> <li class="comment even thread-even depth-1" id="comment-49696"> <img alt='' src='https://secure.gravatar.com/avatar/7c46dd6b44baea63f84bea00e8b213d2?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/7c46dd6b44baea63f84bea00e8b213d2?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn">Mr. Peabody</cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-49696"> November 19, 2007</a></div> <div class="comment-content"><p>It is inane that by default screenreaders do not read link titles! Even Lynx reads the link “title” attribute!</p> </div> </li> </li> <li class="comment byuser comment-author-admin bypostauthor odd alt thread-odd thread-alt depth-1" id="comment-49702"> <img alt='' src='https://secure.gravatar.com/avatar/68d5820d7821cc80ba38185a650995f7?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/68d5820d7821cc80ba38185a650995f7?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn"><a href="http://webaim.org" class="url" rel="ugc">Jared Smith</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-49702"> November 21, 2007</a></div> <div class="comment-content"><p>Mr. Peabody-</p> <p>I think it’s a good thing that screen readers do not read the title values for links. Title is intended to provide supplementary information. If title is necessary for accessibility, then it is therefor NOT supplementary. Because of the vast misuse of title for links (primarily for search engine optimization), it’s no wonder most users prefer to not hear them read.</p> <p>However, there is an argument for having screen readers read the title for links when the content of the link is an image that has no alt text.</p> <p>Still, you should never rely on title to provide accessibility, because if it is inaccessible when title is ignored, you are naturally abusing the purpose for having the title attribute in the first place.</p> </div> </li> </li> <li class="comment even thread-even depth-1" id="comment-49818"> <img alt='' src='https://secure.gravatar.com/avatar/31ad88aec20bb7151e93cb7c452a095d?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/31ad88aec20bb7151e93cb7c452a095d?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn"><a href="http://webaxe.blogspot.com" class="url" rel="ugc external nofollow">Dennis at WebAxe</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-49818"> December 3, 2007</a></div> <div class="comment-content"><p>I don’t believe the alt attribute should be made optional for images. As stated, for decorative images, we leave the alt blank–simple and consistent. In the example above, I don’t see a problem with the caption and alternative text having “redundant text”. This is a very minor issue. Besides, a sighted user would also digest the content twice, just once with an image and once with text (rather than twice with text). PS: Mr. Peabody, I agree that the title attribute should be treated more importantly by not only screen readers, but Safari as well!</p> </div> </li> </li> <li class="comment odd alt thread-odd thread-alt depth-1" id="comment-49890"> <img alt='' src='https://secure.gravatar.com/avatar/ec21041c62a2aded1cdcc7b77d96b4de?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/ec21041c62a2aded1cdcc7b77d96b4de?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn"><a href="http://access-matters.com" class="url" rel="ugc external nofollow">Bob Easton</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-49890"> December 7, 2007</a></div> <div class="comment-content"><p>Regarding the HTML 5 controversy, you said “The argument is that screen readers ignore images that have no alt attribute.” </p> <p>Well, that simply isn’t true. The default settings for today’s screen readers is to try to inform the user about every image. The first place they look is the industry standard place, the ALT attribute. If there’s not alt attribute, they do NOT ignore the image but announce the file name as an attempt to inform the user. The ONLY time screen readers outright ignore an image is when they find alt=”” which serves as an explicit signal to ignore the image.</p> <p>Screen readers -can- be configured to also look for the title attribute, but they are not by default. The reasons are exactly as stated earlier. Title is intended, by the standards, as supplemental information and should not be depended upon to convey critical primary information. The overuse of titles for search engine placement is yet another reason to have them remain unannounced.</p> </div> </li> </li> <li class="comment byuser comment-author-admin bypostauthor even thread-even depth-1" id="comment-49891"> <img alt='' src='https://secure.gravatar.com/avatar/68d5820d7821cc80ba38185a650995f7?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/68d5820d7821cc80ba38185a650995f7?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn"><a href="http://webaim.org" class="url" rel="ugc">Jared Smith</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-49891"> December 7, 2007</a></div> <div class="comment-content"><p>Bob, what you describe regarding screen readers identifying images without an alt attribute is only true if the image is within a link. If you place only an image that has no alt attribute on a page, both JAWS and Window Eyes will ignore it by default, as they should.</p> </div> </li> </li> <li class="comment odd alt thread-odd thread-alt depth-1" id="comment-49978"> <img alt='' src='https://secure.gravatar.com/avatar/0a0b09166b23e9b246b42132170d517d?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/0a0b09166b23e9b246b42132170d517d?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn"><a href="http://dotjay.co.uk/" class="url" rel="ugc external nofollow">dotjay</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-49978"> December 12, 2007</a></div> <div class="comment-content"><p>Thought it was worth noting that some voice recognition software (Dragon Naturally Speaking, I believe) uses the alt text as implied link text where an image is a link, which serves as a convenient trigger phrase for activating the link.</p> </div> </li> </li> <li class="comment even thread-even depth-1" id="comment-49999"> <img alt='' src='https://secure.gravatar.com/avatar/7bf98a3aabf9025d8446c7f662c7585c?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/7bf98a3aabf9025d8446c7f662c7585c?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn"><a href="http://webaim.org" class="url" rel="ugc">Dave</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-49999"> December 13, 2007</a></div> <div class="comment-content"><p>So is it better to use the empty alt=”” tag so all images are ignored and therefore a huge time-saver for users with visual impairments using programs to read the content? Seems it would make it much quicker to just ignore useless images/graphics, no?</p> </div> </li> </li> <li class="comment odd alt thread-odd thread-alt depth-1" id="comment-55793"> <img alt='' src='https://secure.gravatar.com/avatar/da16fe31dba51a44c58a85298a0a9a4b?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/da16fe31dba51a44c58a85298a0a9a4b?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn"><a href="http://uninstallme.com" class="url" rel="ugc external nofollow">Kcmr</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-55793"> October 1, 2008</a></div> <div class="comment-content"><p>What about linked icons? E.g: An icon that represents “open this link in a new window” or “expand/colapse information”. The alt attribute is necessary in this case, but if the image information is not enough clear by itself, the title attribute is necessary for the vast majority of users (those who don’t use a screen reader) supposing that their user agent doesn’t display alt attribute as a tooltip, like Firefox.<br /> Wich is the best option in this kind of linked images?</p> </div> </li> </li> <li class="comment even thread-even depth-1" id="comment-57542"> <img alt='' src='https://secure.gravatar.com/avatar/58c67ef14b8ce7d1070427ce3d63df48?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/58c67ef14b8ce7d1070427ce3d63df48?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn"><a href="http://none" class="url" rel="ugc external nofollow">chad</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-57542"> January 13, 2009</a></div> <div class="comment-content"><p>Not sure if this is the right spot to post this but it’s worth mentioning that at my work we are required to meet all W3C Checkpoints 1 & 2 but we have even more strict requirements developed in house as we have 45K employees and many staff who have a disability of some sort (visual, dexterity, cognitive etc).</p> <p>Anyhow, an effective photo gallery solution was something that we were on the hunt for and stumbled upon this: <a href="http://highslide.com/" rel="nofollow ugc">http://highslide.com/</a></p> <p>It met all our needs (was accessible to users who don’t use a mouse and use their keyboard only, works when Javascript is turned off, we tested is on a JAWS user and they found it easy to navigate, images are alt taggable, the enlarged image has an alt tag etc etc). Anyhow, on this site there are 6 different versions of the way a photo gallery could work, so we took the barn photo example (as the navigation instructions were below the enlarged image) but removed the black out feature on the screen.</p> <p>So, if you are on the hunt for a fully accessible photo gallery solution, then I’d recommend this.</p> <p>C</p> </div> </li> </li> <li class="comment odd alt thread-odd thread-alt depth-1" id="comment-60093"> <img alt='' src='https://secure.gravatar.com/avatar/02269c9935d7af6c6e7b8635ad937418?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/02269c9935d7af6c6e7b8635ad937418?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn">Rick</cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-60093"> July 20, 2009</a></div> <div class="comment-content"><p>Note that there are accessibility issues with HighSlide JS. Some are identified and possible solutions addressed at:</p> <p><a href="http://www.lessfussdesign.com/blog/2008/08/highslide-accessibility/" rel="nofollow ugc">http://www.lessfussdesign.com/blog/2008/08/highslide-accessibility/</a></p> </div> </li> </li> <li class="comment even thread-even depth-1" id="comment-114576"> <img alt='' src='https://secure.gravatar.com/avatar/ea676f36f46f9bfc09e43a690ccc833d?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/ea676f36f46f9bfc09e43a690ccc833d?s=140&d=mm&r=r 2x' class='avatar avatar-70 photo' height='70' width='70' loading='lazy' decoding='async'/> <cite class="fn">Mai</cite> <div class="commentdate"><a href="https://webaim.org/blog/alt-text-and-linked-images/#comment-114576"> December 12, 2012</a></div> <div class="comment-content"><p>Jared “In the situation above, one solution would be to duplicate the caption within the alternative text of the image. This will result in redundancy — the screen reader would read something like, “Link. Photo of an amazing lightning storm. Photo of an amazing lightning storm.” An even better solution is to place both the image AND the caption within the link.”<br /> Can you please clarify – do you mean the image and caption should be in the alt text attribute. If it is in the link in “title” there is a risk the screenreader will not read it?</p> </div> </li> </li> </ol> <div class="navigation"> <div class="alignleft"></div> <div class="alignright"></div> </div> </div> </article>  <aside id="articlemeta"> <div id="updated">November 12, 2007<br><br> <img src="/blog/authors/1.jpg" alt="" /><br>Jared Smith<br><br> <a href="https://webaim.org/blog/alt-text-and-linked-images/#comments"><span class="comments">22 Comments</span><br /></a> </div> <div class="sidebox"> <h2>Search the blog</h2> <form role="search" method="get" id="searchform" class="searchform" action="https://webaim.org/blog/"> <div> <label class="screen-reader-text" for="s">Search for:</label> <input type="text" value="" name="s" id="s" /> <input type="submit" id="searchsubmit" value="Search" /> </div> </form> </div> <div class="sidebox"> <h2>Blog Archives</h2> <ul> <li><a href='https://webaim.org/blog/2024/11/'>November 2024</a></li> <li><a href='https://webaim.org/blog/2024/10/'>October 2024</a></li> <li><a href='https://webaim.org/blog/2024/09/'>September 2024</a></li> <li><a href='https://webaim.org/blog/2024/07/'>July 2024</a></li> <li><a href='https://webaim.org/blog/2024/05/'>May 2024</a></li> <li><a href='https://webaim.org/blog/2024/'>2024</a></li> <li><a href='https://webaim.org/blog/2023/'>2023</a></li> <li><a href='https://webaim.org/blog/2022/'>2022</a></li> <li><a href='https://webaim.org/blog/2021/'>2021</a></li> <li><a href='https://webaim.org/blog/2020/'>2020</a></li> <li><a href='https://webaim.org/blog/2019/'>2019</a></li> <li><a href='https://webaim.org/blog/2018/'>2018</a></li> <li><a href='https://webaim.org/blog/2017/'>2017</a></li> <li><a href='https://webaim.org/blog/2016/'>2016</a></li> <li><a href='https://webaim.org/blog/2015/'>2015</a></li> <li><a href='https://webaim.org/blog/2014/'>2014</a></li> <li><a href='https://webaim.org/blog/2013/'>2013</a></li> <li><a href='https://webaim.org/blog/2012/'>2012</a></li> <li><a href='https://webaim.org/blog/2011/'>2011</a></li> <li><a href='https://webaim.org/blog/2010/'>2010</a></li> <li><a href='https://webaim.org/blog/2009/'>2009</a></li> <li><a href='https://webaim.org/blog/2008/'>2008</a></li> <li><a href='https://webaim.org/blog/2007/'>2007</a></li> <li><a href='https://webaim.org/blog/2006/'>2006</a></li> </ul> <p><a href="/community/rss">RSS Feeds</a></p> </div> </aside> </main> <footer> <div id="footerresources"> <div class="footerblock"> <h2 id="copyright">©2024 WebAIM</h2> <p id="contact">Institute for Disability Research, Policy, and Practice<br> Utah State University<br> 6807 Old Main Hill<br> Logan, UT 84322-6807<br> <a class="phone" href="tel:4357977024">435.797.7024</a></p> <div id="checkpage"> <h2>Check Your Accessibility</h2> <form action="https://wave.webaim.org/report" novalidate> <label for="waveurl">Web site address:</label> <input type="url" id="waveurl" name="url" title="Web site address"> <input type="submit" value="WAVE"> </form> </div> </div> <div class="footerblock"> <h2 id="blog">From the Blog</h2> <ul><li><a href="/blog/severity-ratings/">Using Severity Ratings to Prioritize Web Accessibility Remediation</a></li><li><a href="/blog/25-tips/">25 Accessibility Tips to Celebrate 25 Years</a></li><li><a href="/blog/celebrating-webaims-25th-anniversary/">Celebrating WebAIM's 25th Anniversary</a></li><li><a href="/blog/introducing-ncademi/">Introducing NCADEMI: The National Center on Accessible Digital Educational Materials & Instruction </a></li></ul> </div> <div class="footerblock"> <h2 id="popular">Popular Resources</h2> <ul> <li><a href="/training/virtual">WebAIM Training</a></li> <li><a href="/standards/wcag/checklist">WCAG 2 Checklist</a></li> <li><a href="/newsletter">WebAIM Monthly Newsletter</a></li> <li><a href="/resources/contrastchecker">Color Contrast Checker</a></li> <li><a href="/resources/designers/">Web Accessibility for Designers</a></li> <li><a href="http://wave.webaim.org/">WAVE Web Accessibility Evaluation Tool</a></li> </ul> </div> <div id="footerlinks"> <ul> <li><a id="footercontact" href="/contact">Contact</a></li> <li><a id="footerabout" href="/about">About</a></li> <li><a id="footerrss" href="/community/rss">RSS Feeds</a></li> <li><a id="footertwit" href="http://twitter.com/webaim">Twitter</a></li> <li><a id="footercopyright" href="/copyright">Copyright & Terms of Use</a></li> </ul> </div> <div class="clear"></div> </div> </footer> </body> </html>