Google’s Agent-Friendly Checklist is the Reworded Accessibility Audit

) forms the basis of WAI-ARIA creation practices and WCAG 4.1.2 (Name, Role, Value).

Rule 5 (cursor signal visible) corresponds to WCAG 1.3.3 (Sensory Characteristics).

Rule 6 (etiquette for seizure) is WCAG 1.3.1 (Information and Relationships).

Rule 7 (minimum interactive size) is WCAG 2.5.5 (target size). The human-readable version is 24 x 24 CSS pixels; Google’s threshold is lower because vision models can detect smaller elements than human users can comfortably operate.

The model is consistent. Built for assistive technologies, built for AI agents. The audit is of the same form, executed simultaneously for two classes of visitors. The vocabulary is different. The artifact is identical.

Run an accessibility audit and retrieve both visitor classes

Stop running accessibility audits and AI agent readability audits as separate disciplines on separate quarterly cycles. This is the same audit. Web professionals who have already invested in WCAG compliance are poised to pass Google’s seven. Operators who have never done accessibility work now see agent readability work landing on the same checklist, with the weight of the vendor behind it.

Concrete movement for this week:

1. Extract the five most visited pages from your website.
2. Run them through both Google’s Seven Rules and a WCAG-AA analysis (LighthouseDevTools axis, the WAVE extension; the one you already use). Note the overlap.
3. Correct once. Collect both classes of visitors.

If you are on Tailwind v4, add the three lines @layer base first extracted from your global stylesheet. This single change recovers rule 5 on your entire population. This is the most important fix on the list because Tailwind v4 is now available everywhere, accessibility tools won’t report it (the click still works), and no one is talking about this regression.

Search interest in “web accessibility” barely changed when the EAA took effect, then quadrupled

Search interest remained stable for four years. Until 2024. For most of 2025. Until The European Accessibility Act will become applicable on June 28, 2025which is the regulatory event that should have moved this curve more than anything else, and barely did. The biggest climb begins in late 2025, accelerates through early 2026 to its peak, and has stabilized lower since. Global search interest in the term has more than quadrupled in 18 months.

I’m not claiming that AI agent coverage is the cause of this situation. The data is correlational. But the shape is interesting: the regulatory event that should have raised the curve barely raised the curve, and the curve began to move when the audience for accessibility advice began to overlap with the audience for AI agent readability advice.

The convergence dates back a decade; The weight of Google suppliers is new

Over the past decade, work on accessibility has been led by a community that largely lacked the clout to make it the dominant auditing discipline. The work was the good work. The public did not show up. Then the AI ​​agents arrived with budget, traction and incentive structure on the supplier side moving in the same direction. When Google publishes the same checklist as the Agent Readability Tips, the discipline ceases to be two audits conducted by two separate communities. This becomes an entry discipline handled by web professionals because the visitor class covers both.

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

Trust… anyone? At least, not blindly.

More resources:

---

This article was originally published on No hacks.

---

Featured image: Beast01/Shutterstock