agents.hidden-interactiveControls hidden from AI agents but still usable
Why it matters
An AI agent acting in a browser for someone finds what it can use in the page's accessibility tree. Google says browser agents work partly by "interpreting the accessibility tree", and Chrome's checks for agents include "Visibility: Confirming that content is not hidden from the accessibility tree while being interactive." A link or button marked aria-hidden="true" is exactly that: a person can click it, and an agent can't see it.
The commonest case is the # link beside a heading, which an agent rarely needs: that is why this is a notice. When the hidden control is the only way to do something, the agent can't do it.
We judge only a link or control that is itself marked aria-hidden: one inside a hidden container is nearly always a closed menu that a stylesheet hides, which the HTML alone can't show. The accessibility pack has the same check for people who use screen readers; with both packs on you hear it once.
Sources: Chrome: agentic browsing scoring, Google's guide to generative AI features in Search, WCAG 2.2, 4.1.2 Name, Role, Value.
How to fix it
Hide it from everyone or from no one: tabindex="-1" beside aria-hidden on what is decoration, inert on a closed menu, and no aria-hidden at all on what people are meant to use.
<h2 id="pricing">Pricing <a href="#pricing" class="anchor" aria-hidden="true" tabindex="-1">#</a></h2>