Google’s Agent-Friendly Checklist Is The Accessibility Audit Restated

Jun 12, 2026 04:00 PM - 1 month ago 40957

Google’s 7 rules for building agent-friendly websites are the accessibility playbook restated for AI agents. Same audit, 2 visitant classes. The practitioners who already did the activity for unsighted and low-vision users are astir of the measurement to passing.

I noticed the page because Matt G. Southern wrote astir it connected MCP connected May 1, 2026. The web.dev article itself (web.dev/articles/ai-agent-site-ux, by Kasper Kulikowski and Omkar More) was past updated April 1, almost a period ago. Your TLDR type of it is: Google has shipped a checklist, benignant of, and it’s worthy running.

I tested nohacks.co against each 7 rules. Six passed. One grounded connected each autochthonal <button> constituent connected the website, and the origin is simply a Tailwind v4 default that ships pinch nary warning. Operators who upgraded from v3 to v4 mislaid this norm crossed their full fastener organization unless they added 3 lines backmost to their guidelines styles.

The absorbing portion is which norm that is, and why.

And of people I fixed it.

The Seven Agent-Friendly Rules Google Published On Web.dev

The afloat database lives astatine web.dev/articles/ai-agent-site-ux, introduced by Google pinch the line, “To thief agents navigate your website, see following:”

Reflect each action successful the interface. A fastener click should nutrient a visible authorities change. An action that fires silently is invisible to the agent.
Keep the layout stable. “Add to cart” should beryllium successful the aforesaid spot crossed merchandise categories. Agents that return screenshots get confused by elements that displacement betwixt pages.
No shade aliases transparent overlays. Anything that covers an interactive constituent gets discarded by ocular analysis, moreover if the screen is afloat transparent.
Use semantic HTML. <button> and <a> overstyled <div> and <span>. If you must usage a non-semantic element, springiness it domiciled and tabindex.
Set cursor: pointer successful CSS. Google calls this “a beardown awesome for actionability.”
Link <label> to <input> pinch the for attribute. Lets the supplier representation the visible explanation matter to the underlying field.
Make interactive elements bigger than 8 quadrate pixels. Visual study filters retired thing smaller.

Two things Google did not say. First, the verbatim framing is “consider following.” Suggestion-grade, not mandate. Second, thing successful the web.dev article ties these recommendations to ranking, surfacing, aliases immoderate circumstantial AI-product-side consequence. Worth naming the gap. Google said consider; I’m pushing harder than that, because the root is the ascendant hunt vendor and the database overlaps pinch 2 decades of accessibility practice. So the medicine beneath is mine, not theirs.

The closest point to a punchline successful the article is the second-to-last sentence: “Everything we propose to make a tract ‘agent-ready’ besides makes sites amended for humans.” That’s not throwaway. Every point connected the database was already a WCAG proposal erstwhile web accessibility advocates were the ones documenting it, a decade ago.

I besides really for illustration really this pairs pinch “machine-first, human-always” successful Machine-First Architecture.

Six Of Google’s Seven Agent-Friendly Rules Pass On Nohacks.co (1, 2, 3, 4, 6, 7)

I ran the audit by inspecting the unrecorded HTML connected the homepage and connected a typical article page, the agentic browser scenery guide. The method was unglamorous: curl the page, grep for <button>, <a>, <label for=, pointer-events-none, past propulsion the compiled CSS and grep for cursor.

Rule 1 (clear state): Every interactive constituent uses a transition-all class. Hover states standard the superior CTA. Inputs get a attraction ring. State changes are visible. Pass.
Rule 2 (stable layout): No layout-shift sources successful the HTML. Header, navigation, and footer are accordant crossed location and article. No contented reflow connected hover. Pass.
Rule 3 (no shade overlays): The only pointer-events-none constituent is the back-to-top fastener itself erstwhile it’s hidden. The fastener is non-interactive AND invisible astatine that moment, truthful it isn’t covering anything. Pass.
Rule 4 (semantic HTML): Eight <button> elements connected the homepage pinch due aria-label attributes, positive 45 <a> elements. Zero <div role="button">. Zero <span onclick>. Pass.
Rule 6 (label-for): The newsletter signup uses <label for="newsletter-email" class="sr-only">. The explanation matter is screen-reader-visible and linked to the input by the for attribute. Pass.
Rule 7 (size threshold): Buttons render astatine 40 pixels by 40 pixels (h-10 w-10 successful Tailwind). Inputs are px-5 py-3. All good supra 8 quadrate pixels. Pass.

That leaves norm 5.

Rule 5 (Cursor: Pointer) Fails On Every Native Button Under Tailwind V4

Native <button> elements connected nohacks.co render pinch cursor: default, not cursor: pointer. The nonaccomplishment spans the mobile paper unfastened button, the newsletter Subscribe submit, six podcast section play buttons connected the homepage, and the floating back-to-top button. The article page adds 2 much newsletter Subscribe submits (one supra the article, 1 below). Twelve unsocial autochthonal <button> elements crossed the 2 pages. None of them get the cursor signal.

<a> elements are fine. Anchors pinch href get cursor: pointer from the browser default, and that hasn’t changed. The nonaccomplishment is button-specific.

The origin is simply a Tailwind v4 change. From the charismatic Tailwind CSS v4 upgrade guide:

“Buttons now usage cursor: default alternatively of cursor: pointer to lucifer the default browser behavior.”

Tailwind v3 included cursor: pointer connected <button> arsenic portion of its Preflight guidelines styles. Tailwind v4 removed it. Operators upgrading from v3 to v4 don’t announcement because the keyboard navigation still works, the surface scholar still announces the button, the click still fires. The accessibility character is unaffected. The point that breaks is the ocular awesome that thing is clickable, and that awesome is norm 5 connected Google’s database because it’s specifically what the vision-model broadside of the agent uses to determine what to interact with.

The hole is the snippet Tailwind ships successful the aforesaid upgrade guide:

@layer guidelines { button:not(:disabled), [role="button"]:not(:disabled) { cursor: pointer; } }

Three lines. Restores norm 5 crossed each autochthonal fastener connected the website. The :not(:disabled) clause preserves the existing disabled:cursor-not-allowed shape that Tailwind users already person connected their disabled-state buttons. Drop it into the world stylesheet, and norm 5 passes connected each fastener astatine once.

Every Rule On Google’s List Maps To An Existing WCAG Recommendation

The accessibility organization has been penning the aforesaid database for 2 decades. Five of Google’s 7 rules representation straight to a WCAG criterion:

Rule 2 (stable layout) overlaps pinch WCAG 2.4.3 (Focus Order) and WCAG 3.2 (Predictable).
Rule 4 (semantic HTML complete styled <div>) is the instauration of the WAI-ARIA Authoring Practices and WCAG 4.1.2 (Name, Role, Value).
Rule 5 (visible cursor signal) maps to WCAG 1.3.3 (Sensory Characteristics).
Rule 6 (label-for-input) is WCAG 1.3.1 (Info and Relationships).
Rule 7 (minimum interactive size) is WCAG 2.5.5 (Target Size). The human-readable type is 24 by 24 CSS pixels; Google’s period is little because imagination models tin observe smaller elements than quality users tin comfortably tap.

The shape is consistent. Build for assistive technology, build for AI agents. The audit is the aforesaid shape, tally for 2 visitant classes simultaneously. The vocabulary is different. The artifact is identical.

Run One Accessibility Audit, Recover Both Visitor Classes

Stop moving accessibility audits and AI-agent-readability audits arsenic abstracted disciplines connected abstracted quarterly cycles. They are the aforesaid audit. Web professionals who already invested successful WCAG conformance are astir of the measurement to passing Google’s seven. Operators who ne'er did the accessibility activity now person the agent-readability activity landing connected the aforesaid checklist pinch vendor weight down it.

Concrete move for this week:

Pull the apical 5 highest-traffic pages connected your website.
Run them done some Google’s 7 rules and a WCAG-AA scan (Lighthouse, axe DevTools, the WAVE extension; whichever you already use). Note the overlap.
Fix once. Recover some visitant classes.

If you are connected Tailwind v4, adhd the three-line @layer guidelines snippet to your world stylesheet first. That azygous alteration recovers norm 5 crossed your full <button> population. It is the azygous biggest hole connected the database because Tailwind v4 ships everyplace now, the accessibility tooling won’t emblem it (the click still works), and cipher is talking astir this regression.

Search Interest In “Web Accessibility” Barely Moved When The EAA Took Effect, Then Quadrupled

Search liking was level for 4 years. Through 2024. Through astir of 2025. Through the European Accessibility Act becoming applicable connected 28 June 2025, which is the regulatory arena that should person moved this curve much than thing else, and hardly did. The bigger climb starts precocious 2025, accelerates done early 2026 to its peak, and has settled little since. Worldwide hunt liking successful the word much than quadrupled successful 18 months.

I americium not claiming the AI-agent sum is what drove this. The information is correlational. But the style is interesting: the regulatory arena that should person spiked the curve hardly did, and the curve started moving erstwhile the assemblage for accessibility-shaped guidance started overlapping pinch the assemblage for AI-agent-readability guidance.

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

The past decade of accessibility activity was carried by a organization that mostly didn’t person the weight to make it the ascendant audit discipline. The activity was the correct work. The assemblage didn’t show up. Then AI agents arrived pinch budget, traction, and a vendor-side inducement building pointing successful the aforesaid direction. When Google publishes the aforesaid checklist arsenic agent-readability guidance, the subject stops being 2 audits tally by 2 abstracted communities. It becomes 1 input-side subject that web professionals tally because the visitant people spans both.

Six of 7 connected the audit is simply a passing grade. The seventh is simply a CSS norm that was Tailwind’s occupation to set, and now it’s yours.

Trust … nary one? At least, not blindly.

More Resources: