CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>WebAIM: Web Accessibility Among Nonprofits</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>Web Accessibility Among Nonprofits</h1> <p id="breadcrumbs"><span class="hidden">You are here: </span><a href="/">Home</a> > <a href="/blog/">Blog</a> > Web Accessibility Among Nonprofits</p> <div class="section post" id="post-2200"> <div class="entry"> <h2 class="wp-block-heading">Introduction</h2> <p>As we digest what the <a href="https://webaim.org/projects/million/">WebAIM Million</a> means for disability equity in a largely digital world, WebAIM has been asking if we would expect to see differences across sectors. I believe that awareness drives action, so those in a disability field and those with roots in civil justice or diversity should have better web accessibility. However, WebAIM has performed some sector evaluations where this was found to not always be the case.</p> <p>For example, WebAIM collected 3 years of longitudinal research on the websites of the national network of University Centers for Excellence in Developmental Disability (<a href="https://www.aucd.org/template/page.cfm?id=667">UCEDD</a>), along with their host universities, and their state governments. In this research we hypothesized that the disability network sites would fare better than the others, because of their stated mission that includes disability. They did not. We have presented on some of these data elsewhere (e.g., <a href="https://www.3playmedia.com/resources/recorded-webinars/where-do-we-go-from-here-web-accessibility-across-3-national-systems/">3PlayMedia Webinar</a>; <a href="http://bit.ly/3yeara11yevalCSUN19">CSUN 2019</a>). </p> <p>This made me think about the nonprofit sector, where many organizations are very aware of social issues and work hard to be inclusive, if for no other reason than to make sure patrons have access to online content and donation opportunities. So, should we expect the nonprofit world to have a greater degree of sensitivity, awareness, and action to include those with disabilities? In 2018, <a href="https://2019ict.org/wp-content/uploads/2019/05/Proceedings-of-the-2018-ICT-Accessibility-Testing-Symposium.pdf">Washington & Feng published research</a> showing that inaccessibility was pervasive among the 48 nonprofit websites in their sample. </p> <p>WebAIM has completed 2 rounds of research taking a peek at the accessibility of homepages in the nonprofit space. In the spirit of adding to a developing research base, we want to share those findings here. I will share the most recent (2019) findings, whose methodology aligned with the WebAIM Million.</p> <h2 class="wp-block-heading">What we did</h2> <p>We first needed to identify a sample from the thousands of nonprofits throughout the country. The nonprofit world is certainly diverse. There are some very large nonprofits that have dedicated internal web resources, and others that take on a mom-and-pop persona for the work they accomplish in their community. </p> <p>We decided to look at nonprofits that had some heft, and those that were viewed within the nonprofit community as getting some traction regardless of the size of their web presence. Because of this we used the <a href="https://topnonprofits.com/">TopNonProfits</a> website list for the <a href="https://topnonprofits.com/lists/best-nonprofits-on-the-web/">Top 100 Nonprofits On the Web</a>. In April of 2019 we used the <a href="https://wave.webaim.org/standalone">WAVE stand-alone API</a> to analyze only the homepages of these 100 organizations. We looked only at automatically detectable errors, which we realize returns a conservative result; in other words, the actual accessibility issues are likely much more prevalent than what is found here because we did not perform any manual testing. It is very important to note that the absence of errors on a site in this research does not mean that a site is accessible. It only means it did not contain the types of errors WAVE detects automatically. We used the same <a href="https://webaim.org/projects/million/#method">method</a> described in the WebAIM Million. The same caveats regarding only the <a href="https://webaim.org/projects/million/#homepages">home pages</a> also apply.</p> <h2 class="wp-block-heading">What we found </h2> <h3 class="wp-block-heading">WCAG 2 Conformance</h3> <p>In our sample, 98 of the 100 nonprofit homepages contained WCAG conformance failures that WAVE automatically detected. Tools like WAVE can only detect about a quarter of possible WCAG 2 errors, but can provide a broad measure of inaccessibility. This also means that the actual WCAG conformance rate for these pages is well below 2%.</p> <h3 class="wp-block-heading">Error Counts</h3> <p>The number of errors that a user encounters on a single page is important. In this sample, WAVE automatically detected 4,965 errors, with a range of 0-174 errors on a page. The median number of errors in this sample was 43 on a homepage (i.e., number of errors on the 50<sup>th</sup> page in the sample) while the mean was 49 per page. One would expect to find a detectable error on one of every 18 elements on a home page. The 49 average errors per page was better in this sample of 100 nonprofits than in the <a href="https://webaim.org/projects/million/#errors">WebAIM Million</a> where there was an average of nearly 60 errors per page. Both samples show that around 98% of the pages themselves have detectable WCAG 2 failures.</p> <h3 class="wp-block-heading">Error types</h3> <p>By far, most errors occurred across 5 types:</p> <table class="wp-block-table"><tbody><tr><th>WCAG Failure</th><th>Average errors per home page</th></tr><tr><td>Low contrast text</td><td>31.1</td></tr><tr><td>Missing alternative text</td><td>6.6</td></tr><tr><td>Empty link</td><td>5.6</td></tr><tr><td>Missing input label</td><td>2.6</td></tr><tr><td>Empty button</td><td>2.0</td></tr></tbody></table> <h2 class="wp-block-heading">Where to go from here?</h2> <p>This research underscores the need for nonprofits to pay attention to web accessibility. The result is disappointing when 98 of 100 pages have automatically detectable errors; these are the low hanging fruit of the web accessibility world. With that said, having data on error types is useful. If effort was put into fixing only these five types, a tremendous positive outcome would be likely.</p> <p>As I reflect on this research, I am reminded of Jared Smith’s call to action after the publication of the WebAIM Million report – “So, what are YOU going to do about it?” At WebAIM, we are working now with the MacArthur Foundation to assist nonprofits. We are writing an action paper to motivate nonprofits to act, and to describe techniques they can use to improve web accessibility. So, what will YOU do with information from this research? Hopefully you will share it with those in the nonprofit sector. I hope when we look at this data in the future we see positive trends that are consistent with the overarching values of diversity and inclusion that come from that sector. </p> <p></p> <p></p> <p></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-155528"> <img alt='' src='https://secure.gravatar.com/avatar/6fea0c4976b6a0ff2dfda99f1937465e?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/6fea0c4976b6a0ff2dfda99f1937465e?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="https://www.digitala11y.com/acccessibility-archives/" class="url" rel="ugc external nofollow">Digital A11y</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/web-accessibility-among-nonprofits/#comment-155528"> May 31, 2019</a></div> <div class="comment-content"><p>It would be good to know on which CMS platform these non-profits built their website… I see that most of the non-profits either use WordPress & Drupal, the agencies they work with lack accessibility knowledge which is the main reason for inaccessible websites. I think just doing few tweaks & creating awareness in the sector should resolve a lot of bugs.</p> </div> </li> </li> <li class="comment odd alt thread-odd thread-alt depth-1" id="comment-155734"> <img alt='' src='https://secure.gravatar.com/avatar/1d4925cfe7b4025037be5038af7d4292?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/1d4925cfe7b4025037be5038af7d4292?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="https://MRWweb.com" class="url" rel="ugc external nofollow">Mark Root-Wiley</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/web-accessibility-among-nonprofits/#comment-155734"> June 6, 2019</a></div> <div class="comment-content"><p>You write:</p> <blockquote><p>The 49 average errors per page was better in this sample of 100 nonprofits than in the WebAIM Million where there was an average of nearly 60 errors per page.</p></blockquote> <p>That is true, but the better comparison might be to the .org TLD sites in the WebAIM million sample. Those sites had an average of 47.4 errors, just about the same.</p> <p>I’d also love to know the two sites without error. I know that 0 errors does not mean the sites are perfectly accessible, but it does suggest those sites are at least doing something right.</p> </div> </li> </li> <li class="comment even thread-even depth-1" id="comment-155756"> <img alt='' src='https://secure.gravatar.com/avatar/40663df55a5d508eddb6233ccb68663f?s=70&d=mm&r=r' srcset='https://secure.gravatar.com/avatar/40663df55a5d508eddb6233ccb68663f?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://changelabsolutions.org" class="url" rel="ugc external nofollow">Leah Roderman</a></cite> <div class="commentdate"><a href="https://webaim.org/blog/web-accessibility-among-nonprofits/#comment-155756"> June 7, 2019</a></div> <div class="comment-content"><p>I work at a nonprofit that recently launched a new website (Drupal) that was developed to meet WCAG 2 AA. It was a big project and a learning curve, and we consider it ongoing work. Externally, we are very fortunate to work with web developers who prioritize accessibility and build skills and processes into their business. Internally, a big challenge now is educating our staff and getting accessibility thinking integrated more into our culture and projects. Although the website meets the standard, most of the files we make available for download do not, and that’s going to take some time.</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">May 31, 2019<br><br> <img src="/blog/authors/4.jpg" alt="" /><br>Cyndi Rowland<br><br> <a href="https://webaim.org/blog/web-accessibility-among-nonprofits/#comments"><span class="comments">3 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>