<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>WCAG Compliance on No Semicolons</title><link>https://nosemicolons.com/tags/wcag-compliance/</link><description>Recent content in WCAG Compliance on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 09 Sep 2026 12:35:34 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/wcag-compliance/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Accessibility Audit: How I Found 23 WCAG Violations in 'Perfect' Generated Components</title><link>https://nosemicolons.com/posts/ai-code-generation-accessibility-audit-wcag-violations/</link><pubDate>Wed, 09 Sep 2026 12:35:34 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-accessibility-audit-wcag-violations/</guid><description>&lt;p>That moment when you realize your &amp;ldquo;perfect&amp;rdquo; AI-generated component just locked out millions of users? Yeah, I&amp;rsquo;ve been there. Last month, I decided to audit some components I&amp;rsquo;d generated with various AI coding assistants, expecting maybe a few minor issues. Instead, I found 23 distinct WCAG violations across just 5 components that looked flawless on the surface.&lt;/p>
&lt;p>The wake-up call hit hard: AI might be incredible at solving logic puzzles and generating syntactically perfect code, but it&amp;rsquo;s systematically failing at accessibility. Here&amp;rsquo;s what I learned and the audit framework I built to catch these issues before they hurt real users.&lt;/p></description></item></channel></rss>