Submit the form with the screen out of view

Prepare a realistic incomplete request

Use a synthetic support request with a valid description, one invalid contact field and a missing required choice. Keep the description long enough that losing it would matter to the person completing the task.

Navigate using only the keyboard. Confirm that every interactive element is reachable in a sensible order and that focus remains visible. Note any custom control whose keys behave differently from the expected pattern.

Run the same journey with the supported screen-reader and browser combination. Record what is announced when entering the form and each grouped question.

Fail submission and follow the recovery

Activate Submit from the bottom of the page. The error summary should become discoverable, identify the problems and lead to the relevant controls. Each field message should explain a correction rather than merely say Invalid.

Correct one field and submit again. Confirm that the resolved error disappears, the remaining error is still clear and all unaffected answers survive.

Watch for duplicate announcements caused by focus movement combined with several assertive live regions. More speech is not necessarily better feedback, especially when it interrupts the control the user is trying to correct.

Add the mobile constraints

Repeat on a narrow viewport with the on-screen keyboard open. Reach the final fields and action without a sticky footer covering them. Zoom and enlarge text to expose clipped labels, fixed-height messages and horizontal page overflow.

Test a long error message and a translated-length label even if the current site uses only English. The goal is to reveal brittle sizing, not to claim full language support.

Check touch operation around adjacent choices. A compact layout should not make a checkbox or destructive action difficult to select accurately.

Interrupt the final request

Delay the response, activate the action again and simulate a lost connection. The form should explain its state and avoid silently creating duplicate business requests.

Confirm success with a discoverable reference or next step when the backend has accepted the work. If the feature only saves a local draft, the message must say that. Finish the test by reopening the resulting record or draft through the intended user path.