Form Accessibility Errors
WCAG 1.3.1, 1.3.5, 3.3.1, 3.3.2, 4.1.2 — Form input labeling, grouping, and error handling violations.
Input with no label
This text input has no associated label element, no aria-label, and no aria-labelledby. Screen readers cannot identify the purpose of this field.
Label "for" doesn't match input "id"
The label's "for" attribute points to "email-address" but the input's id is "user-email". Clicking the label does not focus the input, and the programmatic association is broken.
Missing fieldset/legend for radio group
These radio buttons share a group question but are not wrapped in a fieldset with a legend. Screen readers cannot convey the group label.
What is your preferred contact method?
Required field with no indication
This field is required (has the "required" HTML attribute) but there is no visible or programmatic indication to the user that the field is mandatory.
Form with no error identification
When this form is submitted with empty required fields, no error messages are shown. The user receives no feedback about what went wrong or which fields need attention.
Placeholder as only label
This input uses placeholder text as its only label. The placeholder disappears when the user starts typing, and it is not reliably announced by all screen readers as a label.
Missing autocomplete on identity fields
These fields collect personal information (name, email) but lack the autocomplete attribute. Users who rely on autofill for cognitive or motor accessibility cannot benefit.