<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: ME</title>
    <description>The latest articles on DEV Community by ME (@webmotcheck).</description>
    <link>https://dev.to/webmotcheck</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4128439%2F8fb2e5df-f46c-46bc-92c6-be182b1f6ce3.png</url>
      <title>DEV Community: ME</title>
      <link>https://dev.to/webmotcheck</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/webmotcheck"/>
    <language>en</language>
    <item>
      <title>I Tested 140 UK Charity Homepages for Accessibility — 138 Had Detectable WCAG Failures #accessibility #webdev #a11y #frontend</title>
      <dc:creator>ME</dc:creator>
      <pubDate>Wed, 16 Sep 2026 16:56:46 +0000</pubDate>
      <link>https://dev.to/webmotcheck/i-tested-140-uk-charity-homepages-for-accessibility-138-had-detectable-wcag-failures-2iob</link>
      <guid>https://dev.to/webmotcheck/i-tested-140-uk-charity-homepages-for-accessibility-138-had-detectable-wcag-failures-2iob</guid>
      <description>&lt;p&gt;I recently built an accessibility checker called WebMotCheck: &lt;a href="https://webmotcheck.com" rel="noopener noreferrer"&gt;https://webmotcheck.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I wanted to test it on real websites rather than controlled demo pages, so I randomly sampled 140 UK charities from the Charity Commission register, limited to incorporated charities with annual income between £250k and £5M.&lt;/p&gt;

&lt;p&gt;Each homepage was rendered in Chromium at desktop width and at 320px, then checked against WCAG 2.2 AA criteria that can reasonably be tested automatically.&lt;/p&gt;

&lt;p&gt;The result&lt;/p&gt;

&lt;p&gt;138 of 140 homepages had at least one automatically detectable WCAG failure.&lt;/p&gt;

&lt;p&gt;The median homepage had 5 distinct issues.&lt;/p&gt;

&lt;p&gt;78 sites had 5 or more&lt;br&gt;
20 sites had 10 or more&lt;br&gt;
Most common failures&lt;br&gt;
Issue   Sites affected&lt;br&gt;
Insufficient text contrast  79%&lt;br&gt;
Links with no accessible name   69%&lt;br&gt;
Duplicate IDs   64%&lt;br&gt;
Invisible keyboard focus    39%&lt;br&gt;
Form fields without labels  26%&lt;br&gt;
Images missing alt attributes   25%&lt;br&gt;
Reflow / horizontal scrolling at 320px  24%&lt;br&gt;
Buttons without accessible names    11%&lt;br&gt;
Browser zoom disabled   11%&lt;/p&gt;

&lt;p&gt;A few numbers stood out.&lt;/p&gt;

&lt;p&gt;There were 418 contrast failures, with a median failing contrast ratio of 2.85:1.&lt;/p&gt;

&lt;p&gt;I also found 1,025 links with no accessible name, often social icons or search icons implemented as SVGs inside links without a label.&lt;/p&gt;

&lt;p&gt;On the 55 sites with keyboard-focus problems, 414 of 1,696 focusable elements showed no visible focus state.&lt;/p&gt;

&lt;p&gt;And 34 sites required horizontal scrolling at 320px, usually because of fixed-width elements.&lt;/p&gt;

&lt;p&gt;Important limitation&lt;/p&gt;

&lt;p&gt;Automated accessibility testing only catches part of the problem.&lt;/p&gt;

&lt;p&gt;It cannot reliably decide whether:&lt;/p&gt;

&lt;p&gt;alt text is actually useful&lt;br&gt;
reading order makes sense&lt;br&gt;
a custom widget works properly with a screen reader&lt;br&gt;
text over a photograph has sufficient contrast in every part of the image&lt;/p&gt;

&lt;p&gt;So these results do not mean 138 sites are completely inaccessible.&lt;/p&gt;

&lt;p&gt;They mean 138 had at least one problem that could be detected automatically.&lt;/p&gt;

&lt;p&gt;Interestingly, the two pages with no detected failures were not especially sophisticated. They were simply relatively simple sites with dark text, light backgrounds, straightforward layouts, and fewer icon-only controls.&lt;/p&gt;

&lt;p&gt;I’d be interested to hear from people working in accessibility or frontend development:&lt;/p&gt;

&lt;p&gt;Do these numbers surprise you? And what would you change or add to the testing methodology?&lt;/p&gt;

</description>
      <category>a11y</category>
      <category>testing</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
