Skip to content
Dev Ring Technologies
Let’s talk
Back to the blog

Accessible contact forms: a practical acceptance checklist

A form can look finished while remaining difficult to use with a keyboard, showing unclear errors or claiming success too soon. This method helps site owners and developers plan acceptance checks and record observable results before release.

1. Define the journey and a test environment

Write down what people need to do: understand the request, complete the fields, correct an error and know the outcome. For a simple quotation request, question the purpose of every field and mark optional information. Information needed later should not automatically become a condition for making first contact.

Prepare a preview with an authorised test destination and fictional data. Agree how your team will simulate waiting and failure. The scenarios below are proposed acceptance checks, not a full WCAG audit or a compliance certificate. Do not send a request through a public form without the responsible person’s agreement.

2. Keep labels understandable while typing

Every control needs a name that explains its purpose. The WAI tutorial recommends associating labels with controls; for an explicit HTML label, its for attribute matches the control’s id. An example inside the field does not replace that label.

For example, use “Email address (required)” and add brief guidance if a particular format is expected. Start typing during acceptance testing: the field’s purpose and instructions should remain understandable. Ask a screen-reader user to check the announced name, required state and association between the help text and the correct field.

Reference : W3C WAI — Labeling Controls · Reference : W3C WAI — Validating Input

3. Complete the journey with a keyboard

WCAG 2.1.1 addresses keyboard operation of functionality. Criterion 2.4.7 addresses visible focus. For this journey, enter the form using Tab, go back with Shift+Tab, then reach its choices and submit button without a mouse.

Record where you lose your position, cannot reach a control or encounter an unexpected detour. Check the return from an error message too. Give the team a precise reproduction step, such as “After choosing the subject, the submit button cannot be reached by keyboard”. This is easier to investigate than a general “accessibility issue”.

Reference : WCAG 2.2 — Understanding Keyboard (2.1.1) · Reference : WCAG 2.2 — Understanding Focus Visible (2.4.7)

4. Explain errors and make correction possible

When an input error is automatically detected, WCAG 3.3.1 requires identifying the affected item and describing the error in text. A red outline alone is therefore insufficient. The WAI tutorial describes options including messages near controls and summaries of errors.

In preview, try an empty required field and then an incomplete email address. Prefer “Enter an email address in the format name@example.com” to “Invalid value”. Check that other information remains available after correction. Preserving it is a proposed acceptance condition here, not a quotation of a WCAG requirement. Browser validation does not replace server-side validation.

Reference : WCAG 2.2 — Understanding Error Identification (3.3.1) · Reference : W3C WAI — User Notifications · Reference : W3C WAI — Validating Input

5. Distinguish waiting, receipt and failure

A change of state should be understandable without watching only the button’s colour. For status messages added without a change of context or receiving focus, WCAG 4.1.3 provides for presentation by assistive technologies. Check the announcement using the tools your testers actually use.

Agree what each message means with the team. “Request recorded” requires confirmed receipt by the intended system. It does not prove that an email was delivered or a person read the message. If the network response leaves the outcome uncertain, describe that uncertainty instead of promising success or encouraging repeated submissions. These are product wording decisions to check against the actual implementation.

Reference : WCAG 2.2 — Understanding Status Messages (4.1.3)

6. Repeat on mobile and in each language

WCAG reflow criterion 1.4.10 covers, among other cases, vertically scrolling content at a width equivalent to 320 CSS pixels, with exceptions for content requiring two dimensions. Check that form labels, guidance and errors remain readable without horizontal scrolling of the page.

Repeat the same scenarios in French, English and Arabic when those versions exist. Inspect longer translations, punctuation and email-address reading within right-to-left content. Record device, browser, language and assistive technology separately: a successful mobile screenshot does not validate the entire journey.

Reference : WCAG 2.2 — Understanding Reflow (1.4.10)

7. Turn observations into a release decision

Use the checklist below in the agreed test environment. For each row, record steps, expected and observed results, and evidence without personal data. A screenshot can show a message; for keyboard operation or a spoken announcement, add the actions and what was observed or heard.

Assign each failure to someone responsible for its correction, then repeat the scenario on the corrected version. If entering information or understanding the result remains blocked, keep that issue open in the release decision. After publication, limit public checks to authorised observations and use the agreed test destination for any further submission test.

Example acceptance checklist using fictional data

Example acceptance checklist using fictional data
ScenarioResult to checkEvidence to retain
Empty required fieldThe affected field and expected correction are explainedError text and reproduction step
No-mouse journeyEvery action is available and focus is visibleKey sequence and observation
Simulated failure in previewNo success claim; information remains recoverableSimulated state and displayed wording
Success to the test destinationWording matches the outcome actually confirmedTest receipt without personal data
Arabic mobile layoutUnderstandable reading order and messages, no page overflowWidth, language and screenshot

Frequently asked questions

Is an automated tool enough?

It can flag some defects, but this checklist also includes keyboard operation, understanding messages and checks with assistive technologies. Keep these observations alongside the automated report.

Does starting require rebuilding everything?

Start with a reproducible defect and its effect on the journey. A missing label or unclear message may call for a targeted fix. Decide the scope after investigating the cause with the team.

Does this checklist certify the website?

No. It structures form acceptance testing. A conformity evaluation needs a wider scope, criteria and method; no score or business outcome is guaranteed here.

Prepare a brief your team can use

Bring the page, its languages and two or three reproducible difficulties. You can then agree the correction scope and the evidence expected at handover.

Primary sources and limits

W3C/WAI documents consulted on 30 October 2026. Understanding pages explain WCAG criteria; the scenarios, examples and acceptance decisions above are editorial recommendations.