Google’s Agent Checklist Reframes the Accessibility Audit

Google has quietly published a set of seven rules for building websites that AI agents can navigate effectively. But here’s the twist: this new agent-friendly checklist is essentially a rephrased version of the accessibility audit that web professionals have been running for years. The same work, two different visitor classes. And the teams who already prioritized accessibility for blind and low-vision users are most of the way to passing.

The page caught my attention after Matt G. Southern covered it on Search Engine Journal on May 1, 2026. The original web.dev article (by Kasper Kulikowski and Omkar More) was last updated April 1. The short version: Google published a checklist, and it’s worth auditing your site against it.

I ran nohacks.co against all seven rules. Six passed. One failed on every native `` element across the site. The culprit? A Tailwind v4 default that ships without warning. Anyone who upgraded from v3 to v4 lost this rule across their entire button population unless they added three lines back to their base styles.

The interesting part is which rule failed and why.

I fixed it, of course.

The Seven Agent-Friendly Rules Google Published

The full list lives at web.dev/articles/ai-agent-site-ux, introduced with the line: “To help agents navigate your website, consider following:”

1. Reflect every action in the interface. A button click should produce a visible state change. Silent actions are invisible to the agent.Two important gaps: Google frames this as “consider following” , suggestion-grade, not mandate. And nothing in the article ties these recommendations to ranking or any specific AI product consequence. But I’m pushing harder than Google did, because the source is the dominant search vendor and the list overlaps with two decades of accessibility practice. The prescription below is mine.The article’s closest punchline is the second-to-last sentence: “Everything we suggest to make a site ‘agent-ready’ also makes sites better for humans.” That’s not throwaway. Every item was already a WCAG recommendation when web accessibility advocates were documenting it a decade ago.

Six of Seven Rules Pass on Nohacks.co

I audited the live HTML on the homepage and a representative article page. The method was simple: curl the page, grep for `

`, ``, `

• Rule 1 (clear state): Every interactive element uses a `transition-all` class. Hover states scale the primary CTA. Inputs get a focus ring. State changes are visible. Pass.That leaves Rule 5.

Rule 5 Fails on Every Native Button Under Tailwind v4

Native `

` elements on nohacks.co render with `cursor: default`, not `cursor: pointer`. The failure spans the mobile menu open button, the newsletter Subscribe submit, six podcast episode play buttons, and the floating back-to-top button. The article page adds two more newsletter Subscribe submits. Twelve unique native `` elements across two pages. None get the cursor signal.

`` elements are fine. Anchors with `href` get `cursor: pointer` from the browser default. The failure is button-specific.

The cause is a Tailwind v4 change. From the official upgrade guide: “Buttons now use `cursor: default` instead of `cursor: pointer` to match the default browser behavior.”

Tailwind v3 included `cursor: pointer` on `

` as part of its Preflight base styles. Tailwind v4 removed it. Upgrading operators don’t notice because keyboard navigation still works, screen readers still announce the button, clicks still fire. The accessibility tree is unaffected. What breaks is the visual signal that something is clickable , and that signal is exactly what the vision-model side of the agent uses to decide what to interact with.

The fix is the snippet Tailwind ships in the same upgrade guide:

“`css @layer base { button:not(:disabled), [role=”button”]:not(:disabled) { cursor: pointer; } } “`

Three lines. Restores Rule 5 across every native button. The `:not(:disabled)` clause preserves the existing disabled-state pattern. Drop it into the global stylesheet, and Rule 5 passes on every button at once.

Every Rule Maps to an Existing WCAG Recommendation

The accessibility community has been writing this same list for two decades. Five of Google’s seven rules map directly to a WCAG criterion:

• Rule 2 (stable layout) overlaps with WCAG 2.4.3 (Focus Order) and WCAG 3.2 (Predictable).The pattern is consistent. Build for assistive technology, build for AI agents. The audit is the same shape, run for two visitor classes simultaneously. The vocabulary is different. The artifact is identical.

Run One Accessibility Audit, Recover Both Visitor Classes

Stop running accessibility audits and AI-agent-readability audits as separate disciplines on separate quarterly cycles. They are the same audit. Web professionals who already invested in WCAG conformance are most of the way to passing Google’s seven rules. Operators who never did the accessibility work now have the agent-readability work landing on the same checklist with vendor weight behind it.

Concrete move for this week:

Pull the top five highest-traffic pages on your website. Run them through both Google’s seven rules and a WCAG-AA scan (Lighthouse, axe DevTools, or the WAVE extension). Note the overlap. Fix once. Recover both visitor classes.

If you are on Tailwind v4, add the three-line `@layer base` snippet to your global stylesheet first. That single change recovers Rule 5 across your entire `

` population. It is the single biggest fix on the list because Tailwind v4 ships everywhere now, the accessibility tooling won’t flag it (the click still works), and nobody is talking about this regression.

Search Interest in “Web Accessibility” Barely Moved When the EAA Took Effect, Then Quadrupled

Search interest was flat for four years. Through 2024. Through most of 2025. Through the European Accessibility Act becoming applicable on June 28, 2025 , the regulatory event that should have moved the curve more than anything else , and barely did. The bigger climb starts late 2025, accelerates through early 2026 to its peak, and has settled lower since. Worldwide search interest in the term more than quadrupled in 18 months.

I’m not claiming the AI-agent coverage drove this. The data is correlational. But the shape is telling: the regulatory event that should have spiked the curve barely did, and the curve started moving when the audience for accessibility-shaped guidance started overlapping with the audience for AI-agent-readability guidance.

The Convergence Is a Decade Old; Google’s Vendor Weight Is What’s New

The last decade of accessibility work was carried by a community that mostly didn’t have the weight to make it the dominant audit discipline. The work was the right work. The audience didn’t show up. Then AI agents arrived with budget, traction, and a vendor-side incentive structure pointing in the same direction. When Google publishes the same checklist as agent-readability guidance, the discipline stops being two audits run by two separate communities. It becomes one input-side discipline that web professionals run because the visitor class spans both.

Six of seven on the audit is a passing grade. The seventh is a CSS rule that was Tailwind’s job to set, and now it’s yours.

Trust … no one? At least, not blindly.

(Source: Search Engine Journal)

Topics

agent-friendly websites 95% web accessibility 93% wcag standards 88% tailwind css v4 85% cursor pointer rule 82% semantic html 80% ai agents 78% accessibility audits 76% european accessibility act 72% search interest trends 70%

Tags

ai agent checklist semantic html tailwind css v4 wcag compliance web accessibility audit

Copy URL URL Copied