Form fields
WCAG 4.1.2 Name, Role, Value · AAUTOMATICDECISION QUEUE
What the rule requires
Every form field needs a name and role assistive technology can announce. An unlabeled field is a guessing game — “edit text, blank” tells the user nothing about what to type.
How Proof clears it
Fields registered automatically: widgets are tagged into Form structure with tooltips written.
Meaningful labels are human-authored per field — “Applicant’s date of birth”, not “Text1”.
Ghost widgets cleared: vestigial exporter-artifact widgets are removed — but only when provably junk.
What to expect
Label wording is a human decision by design: Proof registers and structures every field automatically, but what a field should be called is content, not plumbing.
Related rules
Run the full profile on one of yours.