What we observe
On every page we read we look for buttons and links with no accessible name, ARIA roles and attributes that are invalid or conflict, positive tabindex values, and controls nested inside other controls. These are among the problems Lighthouse’s agent check reads in the accessibility tree.
Why it is here: the evidence
Documented A platform’s own published document or code says this is read: a standard the crawlers follow, or the documentation or source code of the company that runs the system.
Source: Google Lighthouse’s agent-accessibility-tree audit, read in its source. Source grade A: read at the source: the document, the code or the study itself.
Last re-checked ; due again within 30 days.
What we cannot see
Whether a name makes sense. “Click here” is a name; whether it says where the link goes needs a person.
How to fix it
Give every button and link text or an aria-label that says what it does, and use only the ARIA roles and attributes valid for the element.
- Layer
- Transact: Can an automated visitor reach contact, booking or checkout, and use the form there?
- Level
- One of the checks of Level 2: Is what it reads about your business the same everywhere, and can it find where to act?
- Where its finding lives
- Accessibility
- How common it is
- Not published yet. We publish a share only once at least 30 sites stand behind it.
- Check id
chk-a11y-aria
Cite as: Invara, “How AI sees your site”, method version 1, check chk-a11y-aria. https://clearsitedigital.com/how-ai-sees-sites/chk-a11y-aria