<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Accessibility on Corey Daley</title><link>https://coreydaley.dev/tags/accessibility/</link><description>Recent content in Accessibility on Corey Daley</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 25 Apr 2026 01:13:00 -0400</lastBuildDate><atom:link href="https://coreydaley.dev/tags/accessibility/rss.xml" rel="self" type="application/rss+xml"/><item><title>Your HTML Is Lying to AI Agents</title><link>https://coreydaley.dev/posts/2026/04/your-html-is-lying-to-ai-agents/</link><pubDate>Sat, 25 Apr 2026 01:13:00 -0400</pubDate><guid>https://coreydaley.dev/posts/2026/04/your-html-is-lying-to-ai-agents/</guid><description>&lt;p&gt;Your site has two versions. The first is the rendered page: sidebar on the left, article on the right, everything in its place. The second is what machines read — the raw HTML, in source order, before CSS gets involved. On most personal blogs, that second version leads with navigation, tag clouds, and category lists before it reaches a word of the article. That&amp;rsquo;s the version every AI agent, crawler, and screen reader encounters first.&lt;/p&gt;
&lt;p&gt;This post argues that HTML is no longer just presentation scaffolding — it&amp;rsquo;s a machine-facing interface, and most of us are still designing it as if only browsers matter. The fix is three practical changes: reordering the DOM so content leads, generating llms.txt so agents can orient to your site, and publishing plain text versions of every post so there&amp;rsquo;s nothing to strip. None require a new framework. All take an afternoon.&lt;/p&gt;
&lt;p&gt;If an agent read your site top to bottom in raw HTML, what would it think matters most?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/04/your-html-is-lying-to-ai-agents/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/04/your-html-is-lying-to-ai-agents/&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>How I Used Claude Code to Make My Blog Accessible in Minutes</title><link>https://coreydaley.dev/posts/2026/02/using-claude-code-to-improve-blog-accessibility/</link><pubDate>Wed, 18 Feb 2026 23:03:58 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/02/using-claude-code-to-improve-blog-accessibility/</guid><description>&lt;p&gt;Accessibility often gets pushed to the backlog — it feels complex, time-consuming, and hard to test without specialized knowledge. But I recently discovered just how approachable it can be with the right AI tool.&lt;/p&gt;
&lt;p&gt;I asked Claude Code to audit my Hugo blog for screen reader compatibility with a single prompt. Within seconds it had explored 13 template files, identified issues across 5 priority levels, and produced a comprehensive report. Then I asked it to fix everything — and it did, touching 13 files in one focused session.&lt;/p&gt;
&lt;p&gt;Whether you run a personal blog or a commercial platform, there is no excuse not to make your site accessible when tools like Claude Code can do the heavy lifting. What accessibility improvements have you been putting off that you could tackle today with an AI coding assistant?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/02/using-claude-code-to-improve-blog-accessibility/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/02/using-claude-code-to-improve-blog-accessibility/&lt;/a&gt;
&lt;/p&gt;</description></item></channel></rss>