Accessible form testing combines code inspection with real interaction. Automated checks can find some defects, but they cannot replace keyboard, zoom, error-recovery and assistive-technology review.
Check labels and instructions
Every control needs a clear purpose. Prefer a visible label whose for attribute exactly matches the input id, and explain required formats before an error occurs. Placeholder text is not a substitute for a label.
<label for="contact-email">Email address</label>
<input id="contact-email" name="email" type="email" autocomplete="email" required>Complete the form with a keyboard
Use Tab and Shift+Tab from the page header through every field and action. Focus should remain visible, follow a logical order and never become trapped. Test checkboxes, selects and the final submit action without a mouse.
Trigger and recover from errors
Submit the form empty, use an invalid email and exceed any documented limits. Messages should identify the affected field and explain how to correct it. After correction, the visitor should be able to continue without re-entering unrelated values.
Test zoom, mobile and the destination
Check at 200 percent zoom and at narrow widths without horizontal scrolling. Then exercise the real endpoint or app handoff. The status must say that an app draft opened, not that a message was sent.
- Test at a minimum on desktop and a narrow mobile viewport.
- Try the destination with popups or clipboard access blocked where relevant.
- Repeat a critical flow with a screen reader before release.
- Re-test after changing fields, styles or delivery mode.
Frequently asked questions
Is valid HTML enough for accessibility?
No. Correct markup helps, but the complete interaction, instructions, errors, focus and visual layout also need testing.
Can an automated scanner prove the form is accessible?
No. Automated checks are useful but cannot judge every label, instruction or interaction.
What should be tested after changing only the destination?
Re-test validation, status text, popup or app behavior and the final recipient because those are directly affected.
Primary sources
Turn the guide into a working form
Start from a template, change the fields and take the code with you.
Open the free builder