Making Your Application Process Accessible: ATS, Forms, and Digital Barriers
The Problem
Most employers now route applications through an Applicant Tracking System (ATS) and online forms. When those systems are not built and configured accessibly, they create barriers such as:
- Screen reader incompatibility: Unlabelled form fields, inaccessible CAPTCHA, poor keyboard navigation
- Timeout issues: Forms that expire before candidates with dexterity or cognitive impairments can complete them
- Inaccessible document uploads: Requirements for specific file formats that assistive technology cannot produce
- Video screening tools: Pre-recorded video interviews that exclude Deaf candidates and those with speech differences
The result: qualified disabled candidates are screened out before a human being ever sees their application.
ATS Accessibility Audit Checklist
Keyboard Navigation
Every field, button, and link is reachable using Tab key alone
Focus indicator is visible (not hidden by CSS)
Dropdown menus and date pickers work without a mouse
"Submit" button is keyboard accessible
Screen Reader Compatibility
All form fields have associated labels (not just placeholder text)
Error messages are announced by screen readers
Progress indicators are accessible (not visual-only)
Upload buttons are properly labelled
CAPTCHA has an accessible alternative (audio or bypass option)
Timing and Sessions
Time limits can be turned off, adjusted or extended — WCAG 2.1 (2.2.1 Timing Adjustable) requires, for example, a warning before time expires and at least 20 seconds to extend with a simple action
Progress is saved automatically or can be saved manually
Application can be completed across multiple sessions
Content
Job descriptions are in HTML (not PDF-only or image-only)
Text meets WCAG 2.1 AA contrast requirements (4.5:1 for body text)
Text can be resized without loss of content or function
Language is clear and jargon-free
Choosing and Configuring Your ATS
Accessibility differs between platforms, versions and your own configuration, so do not rely on a vendor's reputation:
- Ask every vendor for its current accessibility conformance report (VPAT/ACR) and accessibility statement
- Check which WCAG version and level the vendor claims, and which known issues it lists
- Write accessibility requirements into procurement and renewal contracts
- Test your own configured application flow — custom questions, assessments and integrations can introduce new barriers
Alternative Application Methods
Every employer should offer at least one alternative to the online ATS application:
- Email application: Accept CV and cover letter by email
- Phone application: Allow candidates to apply verbally
- Paper application: For candidates without digital access
- In-person: Accept walk-in applications
- Third-party support: Allow employment support workers to submit on behalf of a candidate
State this clearly on your careers page: "If you experience difficulty with our online application system, please contact [email/phone] and we will arrange an alternative."
Video Interview Accessibility
If you use one-way or recorded video interview tools:
- Provide captions: Auto-captions at minimum; professional captions for Deaf candidates
- Allow text-based alternatives: Written responses instead of video for candidates who cannot use video
- Avoid AI scoring of expressions and voice: Automated scoring of facial expressions, tone or body language risks penalising candidates whose communication differs because of a disability (for example autistic, Deaf, or physically disabled people); offer a human-reviewed alternative
- Flexible timing: Allow candidates to re-record or have extended time
- Test with assistive technology: Ensure the platform works with screen readers and voice control
Testing Your Process
- Automated testing: Run axe, WAVE, or Lighthouse on your careers page and application forms
- Manual testing: Navigate your entire application process using only a keyboard
- Screen reader testing: Complete an application using NVDA (free) or VoiceOver
- User testing: Engage disabled users — for example through AbilityNet's user testing service — to test the real experience
- Regular audits: Test after every platform update or configuration change
Resources
- W3C WCAG 2.1: w3.org/TR/WCAG21
- WebAIM: webaim.org
- AbilityNet: abilitynet.org.uk
- Deque axe Tool: deque.com
- NVDA screen reader: nvaccess.org