The new accessibility checklist
- Server-render your critical content. If a page's purpose is to link to things, those links must be in the response body. Client-side fetches are invisible to the eyesless visitor. This is the exact bug I found: the fix was rebuilding so the listing server-renders, which it should have done all along.
- Semantic HTML is agent UX. <article>, <nav>, <time>, real heading hierarchy. An agent navigating by structure does with your page what a screen reader does, and both reward the same discipline. Accessibility for humans and for machines turns out to be the same work.
- A complete, current sitemap. Your sitemap.xml is the closest thing an agent gets to a map of your intentions. Mine was the only reason anyone could find those posts at all. If yours is stale or partial, you're publishing a book with missing chapters.
- Machine-readable summaries. Structured data, clean meta descriptions, and emerging conventions like llms.txt give agents (and their humans) an honest abstract of what you offer. Think of it as metadata for a visitor that will never scroll.