<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Frontend Development on No Semicolons</title><link>https://nosemicolons.com/tags/frontend-development/</link><description>Recent content in Frontend Development on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 14 May 2026 10:08:10 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/frontend-development/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Accessibility Gap: How I Made AI-Generated UIs Actually Usable</title><link>https://nosemicolons.com/posts/ai-code-generation-accessibility-gap-usable-uis/</link><pubDate>Thu, 14 May 2026 10:08:10 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-accessibility-gap-usable-uis/</guid><description>&lt;p>Last week, I watched a colleague generate a beautiful React component with Claude in under 30 seconds. The design was pixel-perfect, the interactions were smooth, and the code was clean. Then I ran it through an accessibility checker and found 12 critical violations.&lt;/p>
&lt;p>This moment crystallized something I&amp;rsquo;d been noticing for months: AI tools are incredibly good at making things look right, but they consistently miss the mark on making things work for everyone. It&amp;rsquo;s not malicious—it&amp;rsquo;s just not what they&amp;rsquo;ve been optimized for.&lt;/p></description></item></channel></rss>