Skip to content
wcagc
Create account
←Back to blog
ADATitle IhiringWCAG

ADA compliance for job application and hiring portals

What the ADA asks of a careers site: Title I and the application process, third-party applicant tracking systems, and the WCAG checks for apply flows.

P

Pavel Charkasau

ADA compliance for a job application portal comes from a different part of the law than the rest of your website. Hiring falls under Title I, the employment title, which applies to private employers with 15 or more employees and to state and local government employers (EEOC; 42 U.S.C. § 12111(5)(A)). Title I bans disability discrimination "in regard to job application procedures" (42 U.S.C. § 12112(a)). The EEOC's regulation lists "modifications or adjustments to a job application process" as a form of reasonable accommodation (29 CFR § 1630.2(o)).

What Title I does not contain is a technical web standard. Nothing in the statute or the EEOC regulation names WCAG. So the practical answer has two halves. First, a candidate who can't use your online application must have a working way to ask for an alternative, and someone has to answer. Second, the apply flow itself should meet WCAG 2.2 Level AA, so that fewer candidates need that alternative in the first place.

Does the ADA apply to online job applications?

Yes, through Title I, if you are a covered employer. The statute defines "covered entity" as an employer, employment agency, labor organization, or joint labor-management committee (§ 12111(2)). An employer is a business with 15 or more employees for each working day in 20 or more calendar weeks of the current or preceding year. The definition also includes "any agent of such person."

The application process is named explicitly. Section 12112(a) covers "job application procedures" in the same breath as hiring, advancement and discharge. And the duty to provide reasonable accommodation in § 12112(b)(5)(A) applies to an "applicant or employee" alike. A candidate does not have to be on payroll to be owed an accommodation.

State and local governments carry a second obligation on top. Their careers pages are web content under the Justice Department's Title II rule, which requires WCAG 2.1 Level AA. The compliance dates are now April 26, 2027 for governments serving 50,000 people or more and April 26, 2028 for smaller ones (ADA.gov; Federal Register, 91 FR 20902). A city's job board is in scope the same way its permit forms are. Our Title II guide covers that rule in full.

What counts as a reasonable accommodation in the application process?

Anything that lets a qualified candidate be considered for the job, short of undue hardship. The EEOC's question-and-answer guide for applicants gives offline examples: readers or sign language interpreters, modified equipment, moving an interview to an accessible first-floor office (EEOC, Job Applicants and the ADA). That guide dates from 2003 and does not mention websites at all. The principle carries over without much stretching. For an online application, accommodations look like:

  • accepting a résumé by email when the upload widget doesn't work with a screen reader
  • a phone number or email address that a person actually monitors, published on the careers page and in the posting
  • extra time, or an untimed version, of an online assessment
  • completing the application with a recruiter over the phone

The guide also covers what you may ask. An employer can describe the hiring process to every applicant and "ask whether they will need a reasonable accommodation for this process." It generally cannot ask every applicant whether they will need an accommodation to do the job itself, because the answer could reveal a disability. So "Need help applying? Email accessibility@yourcompany.com" is fine on every posting. A screening question asking "Do you require accommodations to perform this role?" is the kind of question the guide warns against.

My view, after looking at a lot of careers sites: the accommodation contact is the most important line on the page and the one most often missing. When the ATS breaks for a screen reader user, that email address is the only route to the job. If it's absent, or it points at a no-reply inbox, the candidate never gets considered, and that is exactly the outcome Title I is about.

Are pre-employment tests and assessments covered?

Yes, and the rule here is more specific than the general accommodation duty. Under § 12112(b)(7), and the matching EEOC rule at 29 CFR § 1630.11, an employer must administer tests so that the results for a candidate with an impaired sensory, manual or speaking skill reflect "the skills, aptitude, or whatever other factor" the test measures, not the impairment. The exception is a test of that skill itself.

Take a timed cognitive test built from drag-and-drop puzzles. For a keyboard user it measures whether they can operate a drag interaction without a mouse, not reasoning. A separate provision, § 12112(b)(6), covers selection criteria that "screen out or tend to screen out" people with disabilities. Those criteria have to be job-related and consistent with business necessity.

The same logic reaches automated screening tools: video interviews scored on eye contact or speech patterns, games with tight time limits, chatbots that time out. I'm not going to tell you how a given tool will fare in front of a court, and I'm not a lawyer. What I can say is that the statutory test above is the question to put to the vendor before you buy: what does this measure, and what happens when a candidate can't use it the standard way?

Is the employer responsible if the ATS vendor's form is inaccessible?

In practice, yes. The EEOC's rule at 29 CFR § 1630.6 makes it unlawful for a covered entity to participate in "a contractual or other arrangement or relationship" that has the effect of subjecting its own applicants to discrimination. The listed examples (employment and referral agencies, unions, benefit and training providers) don't name software vendors, but the list is expressly "not limited to" them. And the statute's employer definition includes the employer's agents.

Either way, the candidate sees your logo at the top of the page, and the accommodation duty sits with you. Some practical steps:

  1. Ask the ATS vendor for a current accessibility conformance report. Read our guide on what a VPAT is before you read theirs, because the "Supports" column is self-reported.
  2. Test the vendor's apply flow yourself, on your configuration. Custom screening questions and file-upload settings change what the candidate actually gets.
  3. Put the accommodation contact outside the ATS too (on the job posting and the careers landing page), so a candidate stuck inside the vendor's form can still reach a human.

Which parts of an application flow usually fail WCAG?

The same few, on nearly every applicant tracking system I've looked at. WCAG 2.2 Level AA is the reasonable target: the Justice Department's web guidance points to WCAG, and content that conforms to 2.2 also conforms to 2.1 and 2.0 (W3C). The common failures:

  • File upload. A styled <div> replaces <input type="file">, is not reachable by Tab, and has no accessible name. That fails 2.1.1 Keyboard and 4.1.2 Name, Role, Value, and it blocks the one step every application needs.
  • "Apply with LinkedIn" and résumé parsing. The parser fills fields, then asks the candidate to type the same work history again on the next screen. WCAG 2.2's 3.3.7 Redundant Entry (Level A) fails when previously entered information must be re-entered and isn't auto-populated or selectable.
  • Account creation. A CAPTCHA with no alternative, or a password field that blocks paste, runs into 3.3.8 Accessible Authentication (Minimum), Level AA.
  • Session timeouts. Long applications that expire after 20 minutes with no warning fail 2.2.1 Timing Adjustable, which requires a way to turn off, adjust or extend most time limits.
  • Error messages. "Please fix the errors above" in red text, with no indication of which field is wrong, fails 3.3.1 Error Identification.
  • Self-identification forms. The voluntary disability and veteran-status questions are often custom radio groups with no <fieldset> and <legend>, so a screen reader announces "Yes, radio button" with no question attached. That fails 1.3.1 Info and Relationships.

Our WCAG checklist lists these criteria with the checks for each. For the field-by-field patterns, see our accessible forms guide.

How do you test a careers site for accessibility?

Apply for one of your own jobs, twice. Once with only the keyboard, and once with a screen reader (VoiceOver on a Mac, NVDA on Windows). Upload a résumé, answer the screening questions, trigger an error on purpose, and let the session sit idle for a while. Write down where you got stuck. That list is your first round of tickets, and on most careers sites it is short and specific.

Then run an automated scan across the postings and the apply pages for coverage. Be clear-eyed about what that finds. Deque's analysis of more than 2,000 audits put automated detection at about 57% of issues by volume (Deque); counted by success criteria, the share is nearer 30%. Our scanner will flag the unlabeled upload button and the missing <legend>. It won't tell you that your assessment's time limit screens people out, or that nobody reads the accommodation inbox. Full conformance needs human review, and on a hiring flow part of that review is a recruiter checking that the accommodation route works end to end.

Last, write it down. An accessibility statement on the careers site that names the accommodation contact and the known gaps in the vendor form is honest and useful to candidates. Our statement generator gives you a starting draft. More on the US legal background is in our ADA overview.

FAQ

Does the ADA apply to online job applications?

Yes, for covered employers. Title I prohibits disability discrimination in "job application procedures" (42 U.S.C. § 12112(a)) and applies to private employers with 15 or more employees and to state and local governments (EEOC).

Does Title I require a careers site to meet WCAG?

No regulation under Title I names WCAG. The duty is to provide reasonable accommodation in the application process (29 CFR § 1630.2(o)); WCAG 2.2 Level AA is the practical standard for making the online process usable. State and local government careers pages also fall under the Title II web rule, which requires WCAG 2.1 Level AA (ADA.gov).

Can an employer ask applicants if they need an accommodation?

Yes, for the hiring process itself. The EEOC says an employer may tell all applicants what the process involves and "ask whether they will need a reasonable accommodation for this process" (EEOC). Asking every applicant whether they need accommodation to do the job is generally not allowed.

Who is responsible if the applicant tracking system is inaccessible?

The employer still owes the accommodation. The EEOC rule at 29 CFR § 1630.6 covers contractual arrangements that have the effect of discriminating against the employer's own applicants, so test the vendor's flow and publish a contact that works outside it.

Are online pre-employment tests covered by the ADA?

Yes. Tests must be given so that the results reflect the skill being measured rather than a candidate's sensory, manual or speaking impairment, unless that skill is what the test measures (42 U.S.C. § 12112(b)(7); 29 CFR § 1630.11).

See which of your job postings and apply pages fail WCAG checks, with the exact selectors, before you talk to your ATS vendor: run a free scan.

Written by Pavel Charkasau, founder of wcagc.com. I read Title I and the EEOC's regulations for this post, and I'm an engineer, not a lawyer, so treat it as a technical guide rather than legal advice.

Last updated: October 15, 2026

Sources