A technical guide to making job application systems accessible covering ATS compatibility with screen readers, WCAG compliance, alternative application methods, video interview accessibility, and testing.
Making Your Application Process Accessible: ATS, Forms, and Digital Barriers
The Problem
Over 75% of job applications are now submitted through Applicant Tracking Systems (WebAIM, 2023). Yet research consistently shows that most ATS platforms have significant accessibility barriers:
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
Session timeout is at least 20 minutes, with warning and extension option
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)
Font size is at least 16px or user-adjustable
Language is clear and jargon-free
Major ATS Platforms: Accessibility Status
Platform
Accessibility
Notes
**Workday**
Improving
Published VPAT available; ongoing remediation
**SAP SuccessFactors**
Good
Committed to WCAG 2.1 AA; accessibility team
**iCIMS**
Moderate
VPAT available; some screen reader issues remain
**Greenhouse**
Good
Published accessibility statement; proactive remediation
**Lever**
Moderate
Basic WCAG compliance; improving
**Taleo (Oracle)**
Variable
Legacy system; newer versions better
**SmartRecruiters**
Good
Accessibility-focused development
Note: Accessibility status changes with each platform update. Always test with your actual configuration.
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 video interviews (HireVue, Spark Hire, etc.):
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
No AI facial analysis: AI-scored video interviews that analyse facial expressions, tone, and body language systematically disadvantage disabled candidates (particularly autistic, Deaf, and physically disabled people)
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 through Fable or AbilityNet to test the real experience
Regular audits: Test after every platform update or configuration change