Entry aid Checker
Check forms for accessible names, button captions, and autocomplete personal data notices. Especially useful for leads, checkout, login and contact forms.
Test a form field from name to correction
Example: the e-mail address in the contact form
A visible placeholder such as “email” can disappear when typing. Use a permanently recognizable label and connect it to the input field. For the user's own e-mail address, a suitable autocomplete value supports the input; the field type and an input indication must still match the expected input.
Check four conditions
Test the empty form, an incorrect address, the correction and the successful submission. Are already entered values retained? Does the error message specifically describe which field needs to be changed? Is it technically assigned to the field and perceived when using assistive technology? The automatic finding can mark missing names or attributes. Whether the entire error correction works understandably, check on the open form. Especially with multi-step forms, a backward step should not cause unexpected data losses.
Additional documentation: W3C: Form labels
Forms and input purposes
Focused view for WCAG 1.3.1, 1.3.5, 3.3.2 and 4.1.2.
Analyze accessibility and other test areas together: up to 20 URLs for free. Full website audit for one-off 99 € net or SEO Suite from 19 € net monthly.
Forms are conversion infrastructure
If a field is not clearly named or input aids are missing, a small accessibility problem quickly becomes a cause for abandonment. This is especially true on mobile devices.
Typical improvements
- Visible labels with a for/id relationship.
- Clear button names instead of pure icons.
- Autocomplete values such as email, tel, name or postal code.
- Error messages associated with fields.
Sort form aids by effect
Input aids are particularly important when users need to transmit data without errors and quickly. Good labels, autocomplete values and understandable error messages help screen readers, mobile browsers and all users who fill in forms repeatedly.
Prioritisation in practice
- Check contact, request, login and checkout forms first
- Connect mandatory fields and error messages to the fields
- Make sense of autocomplete for name, e-mail, telephone, address and payment data
Next meaningful check
If many form variants exist, you should also run the form label checker to bundle template errors.
When input aids are particularly important
Input aids directly affect conversion and error rate. Critical are forms that collect personal data, contact requests, bookings, billing data or payment information. Labels, autocompletes and error messages should fit together there.
Even short forms deserve attention: A search field, newsletter field or login can become unnecessarily difficult for users with a keyboard, screen reader or mobile helper if the technical name is missing.
For teams, it is helpful to record a small test case per form: empty mandatory field, incorrect format, successful input and correction. After a template update, you can quickly check whether input aids have remained stable.