What we observe
On the contact, booking and checkout pages we read, we count the form fields with no accessible name: the same count the accessibility check reads, kept to the pages where people act.
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
A booking tool that runs inside a frame from another company; its fields are not counted here.
How to fix it
Give every field on these pages a label tied to it; a placeholder alone does not count.
- Layer
- Transact: Can an automated visitor reach contact, booking or checkout, and use the form there?
- Level
- One of the checks of Level 3: Can it get all the way to the submit button?
- 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
fact:path-form-names
Cite as: Invara, “How AI sees your site”, method version 1, check fact:path-form-names. https://clearsitedigital.com/how-ai-sees-sites/fact-path-form-names