What we observe
On every page we read we check each form field for an accessible name, from a label element, an aria-label or an equivalent, and look for required-field marks, autocomplete hints, grouping and a submit control. A missing label is one of the problems Lighthouse’s agent check fails a page on.
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 the form works once it is sent. We never send a form.
How to fix it
Give every field a visible label tied to it, or an aria-label where a visible label is impossible; 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
chk-a11y-forms
Cite as: Invara, “How AI sees your site”, method version 1, check chk-a11y-forms. https://clearsitedigital.com/how-ai-sees-sites/chk-a11y-forms