How to make a job application form easier to access

An application form should let people understand the questions, provide information, correct mistakes, and know whether their application was received. Accessibility needs to cover that whole journey.

Use a recognized accessibility standard and qualified testing where appropriate. A short checklist helps find problems, but it does not establish full conformance or legal compliance by itself.

Give controls clear labels

Each field needs an understandable label associated with the control. A placeholder that disappears when someone types is a poor substitute for a persistent label.

Explain expected formats and required information before the candidate makes an error. For an upload, state accepted file types and the size limit near the control. Do not communicate "required" or "invalid" through color alone.

Group related questions logically so someone can understand the form without relying on the visual layout.

Walk through with a keyboard

Check whether a person can reach every field, open menus, upload a file, and submit without a mouse. The current focus should be visible and move in a sensible order.

Look for dialogs that trap focus incorrectly or close without returning it to a useful location. Test the sign-in or account-creation steps too if the application requires them.

Make errors specific and recoverable

An error should identify the field and explain what needs correcting. "Something went wrong" does not help someone fix an invalid date or an oversized file.

Keep entered information where possible and connect field-level errors with their controls. If there are several errors, a summary can help people navigate to them.

Use appropriate announcements for changes that a screen reader might otherwise miss, such as an upload failure or successful submission. Test the actual behavior rather than assuming an accessibility attribute guarantees it.

Provide a contact route that works

Explain how to request help or an adjustment to the application process. The contact should be monitored and the team should know how to handle the request without turning it into an assessment of suitability.

Include candidates with different access needs in usability research where feasible, with appropriate consent and support. Automated checks can identify some technical issues but cannot establish whether the instructions and recovery steps make sense.

Keep a record of findings and recheck after form changes. A new upload widget or sign-in step can break a previously usable application journey even if the rest of the career site looks unchanged.

Further reading

• Labeling Controls | Web Accessibility Initiative (WAI) | W3C
• Understanding Success Criterion 3.3.1: Error Identification | WAI | W3C

Related guides

• Test mobile applications
• Make submission confirmation clear
• How to build a career page that helps candidates decide to apply