<?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: Chris Clow</title>
    <description>The latest articles on DEV Community by Chris Clow (@chris_clow_04d2c038f345cc).</description>
    <link>https://dev.to/chris_clow_04d2c038f345cc</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%2F4240184%2Fbd270925-8356-46ae-9192-072ab0ab76db.jpg</url>
      <title>DEV Community: Chris Clow</title>
      <link>https://dev.to/chris_clow_04d2c038f345cc</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chris_clow_04d2c038f345cc"/>
    <language>en</language>
    <item>
      <title>I built a free WCAG 2.2 AA scanner that writes a report a client can read</title>
      <dc:creator>Chris Clow</dc:creator>
      <pubDate>Thu, 12 Nov 2026 04:04:49 +0000</pubDate>
      <link>https://dev.to/chris_clow_04d2c038f345cc/i-built-a-free-wcag-22-aa-scanner-that-writes-a-report-a-client-can-read-3968</link>
      <guid>https://dev.to/chris_clow_04d2c038f345cc/i-built-a-free-wcag-22-aa-scanner-that-writes-a-report-a-client-can-read-3968</guid>
      <description>&lt;p&gt;I run AccessLens. It's a scanner you paste one URL into: it loads that page in a real headless Chromium browser, runs axe-core's WCAG 2.2 A and AA rules, and writes a report — issues grouped by severity, the success criterion each one breaks, a plain-English explanation, the markup fix, and the offending elements.&lt;/p&gt;

&lt;p&gt;The gap I wanted to fill: an automated check usually gives you either a raw rule dump or an enterprise platform behind a sales call. Neither helps much when a freelancer has to tell a client what is broken and what fixing it takes.&lt;/p&gt;

&lt;p&gt;Some real numbers, so you can calibrate. The W3C's deliberately-bad demo page comes back in about 2 seconds with 6 problem groups covering 46 elements, worst severity "critical". Our own pages come back with zero automated failures — one item on the front page is flagged for a human rather than passed — and that self-check is published on our accessibility statement.&lt;/p&gt;

&lt;p&gt;What it can't do, worth knowing before you try it: automated testing catches roughly a third of real accessibility problems. There is no screen-reader pass, no keyboard walkthrough and no conformance claim — a clean report is not a certificate. Pages behind a login, or that block automated browsers, can't be scanned at all.&lt;/p&gt;

&lt;p&gt;The scan and the summary report are free: severities, criteria, the fixes, and three sample elements per issue, with no account and no email wall. A one-time $19 buys the complete element-by-element work list for one page, plus a report link that doesn't expire — there's a real example report you can read before paying at &lt;a href="https://a7ba2c9f8e51600b668cfcbbb6ecb648.ctonew.app/offer" rel="noopener noreferrer"&gt;https://a7ba2c9f8e51600b668cfcbbb6ecb648.ctonew.app/offer&lt;/a&gt;, and there is no subscription.&lt;/p&gt;

&lt;p&gt;I'd especially like to hear from people who deliver client sites: does that report read like something you could hand to a client, and if not, what's missing? And from anyone who has shipped axe-core before: what are we getting wrong?&lt;/p&gt;

&lt;p&gt;Link: &lt;a href="https://a7ba2c9f8e51600b668cfcbbb6ecb648.ctonew.app" rel="noopener noreferrer"&gt;https://a7ba2c9f8e51600b668cfcbbb6ecb648.ctonew.app&lt;/a&gt; — free, no sign-up.&lt;/p&gt;

&lt;p&gt;Disclosure: that link is ours — I run AccessLens, so this is self-promotion in the open. This draft was written with AI assistance, and I reviewed and edited it before publishing.&lt;/p&gt;

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