Test keyboard access and error recovery in a contact form.

Instruction: Provide concrete manual and automated checks, expected outcomes, and the limits of the resulting accessibility claim.

Context:

A fictional contact form has required Full name, Email, and Message fields and a Send button. Invalid submission must identify each invalid field in text, explain known corrections, preserve valid input, and allow correction without a mouse. A malformed email such as qa-example must not submit. The team targets WCAG 2.2 Level AA and has a documented supported browser/screen-reader pairing available. You may use synthetic text only. Evaluate this form; a whole-site conformance audit is outside this exercise.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would test a complete keyboard-only path: reach and identify each field, enter values, move forward and backward through the form, submit, correct errors, and submit successfully. Focus should remain visible, and a focused control must not be entirely hidden by sticky headers or other author-created overlays. The sequence should be understandable, and every required action must work without a mouse or precisely timed keystrokes...

Upgrade to view official answer

Related Questions