Careers page and job application accessibility: job listings, application forms, resume uploads and applicant portals

Staffing agencies run their whole business through job listings and application forms, and every small business that hires has at least a careers page or a "Join our team" form. Applicants who use a screen reader, magnifier, keyboard or voice control often get stuck on the same things: job filters that only work with a mouse, placeholder-only fields, resume uploads with no feedback, sessions that time out halfway through, and no way to ask for help. An applicant who can't apply simply doesn't, and you never see them. Much of this runs on an applicant tracking system (ATS), so part of the job is knowing what to ask your vendor for. Here's what to check.

1. Job listings and filters

Each job title should be a real link whose text is the title, not "Apply" or "Learn more" repeated down the page. Location, pay and schedule belong in text, not only in icons. Filters (location, shift, job type) need labels, must work with the keyboard, and the updated count should be announced. (WCAG 2.4.4, WCAG 2.1.1, WCAG 4.1.3)

<label for="loc">Location</label>
<select id="loc" name="location"><option>All locations</option><option>Tulsa</option></select>
<p role="status">Showing 12 jobs in Tulsa</p>
<ul>
  <li><a href="/jobs/warehouse-associate">Warehouse associate</a> Tulsa, day shift, $18 to $20 an hour</li>
</ul>
<!-- example values -->

2. Job descriptions as real text

A job description posted only as a flyer image or a scanned PDF can't be read by a screen reader, can't be resized and isn't found by search engines. Use headings ("What you'll do", "Requirements", "Pay and benefits") and lists. Put physical requirements in plain words so people can judge for themselves. (WCAG 1.4.5, WCAG 1.3.1)

See accessible PDFs and heading structure.

3. Application forms

Every field needs a visible label (not placeholder text), contact fields need autocomplete, required fields are marked in text, and errors say in words what to fix. Group yes/no questions in a fieldset with a legend. Don't make people type their whole work history again after they've uploaded a resume, or offer to fill it from the resume and let them check it. (WCAG 3.3.2, WCAG 1.3.5, WCAG 3.3.1, WCAG 3.3.7)

<label for="email">Email (required)</label>
<input id="email" name="email" type="email" autocomplete="email" required aria-describedby="email-err">
<p id="email-err">Enter an email address like [email protected]</p>
<fieldset>
  <legend>Are you available for weekend shifts?</legend>
  <label><input type="radio" name="weekends" value="yes"> Yes</label>
  <label><input type="radio" name="weekends" value="no"> No</label>
</fieldset>
<!-- example values -->

See form error messages and accessible contact forms.

4. Resume and document uploads

Use a real file input with a label that says which file types and sizes you accept. After upload, announce the file name or the error in text ("resume.pdf uploaded" or "That file is over 5 MB. Choose a smaller file"). Drag-and-drop zones need a "Choose file" button too, and offer another way to apply, such as email, for people who can't upload. (WCAG 3.3.2, WCAG 2.5.7, WCAG 4.1.3)

<label for="cv">Resume (PDF or Word, up to 5 MB)</label>
<input id="cv" name="resume" type="file" accept=".pdf,.doc,.docx">
<p role="status" id="cv-status"></p>
<!-- fill cv-status with "resume.pdf uploaded" or a plain-words error -->

5. Timeouts and long applications

Multi-page applications that time out lose people who type slowly or use assistive technology. Warn before a timeout and let people extend it, save progress between steps, and show which step they're on in text ("Step 2 of 4: Work history"). (WCAG 2.2.1, WCAG 2.4.8)

6. Applicant portals, logins and CAPTCHAs

Let password managers fill logins, don't block paste, allow one-time codes to autofill, and avoid puzzle CAPTCHAs. Most applicant portals belong to an ATS vendor, so ask them for their accessibility conformance report (VPAT) and test the apply flow yourself. See accessible logins and CAPTCHA and what a VPAT is. (WCAG 3.3.8)

7. Assessments and interview scheduling

Timed skills tests and personality quizzes need a way to ask for more time or another format. Interview schedulers need full-time slot buttons that work with the keyboard and an announced confirmation, with a phone or email option next to them. Video interview tools need captions. (WCAG 2.2.1, WCAG 4.1.2, WCAG 1.2.2)

See our 10-minute scheduler test.

8. Say how to ask for an accommodation

Put a short, findable line on the careers page and in the application telling people how to get help applying, with a real email and phone number, and make sure someone answers. Keep it factual and don't claim the process is "fully accessible". (WCAG 3.2.6)

<p>Need help applying, or an accommodation during hiring? Email [email protected] or call 555-0100 and we'll work with you.</p>
<!-- example wording, use your real contact details -->

See the accessibility statement template.

Common mistakes

• "Apply" links with no job title, repeated down the page.
• Job descriptions posted only as images or scanned PDFs.
• Placeholder-only fields and red-border-only errors.
• Drag-only resume uploads with no feedback.
• Applications that time out with no warning and lose everything.
• No way to ask for help applying.
• An overlay widget instead of real fixes. It won't fix an ATS form, and the FTC fined one overlay vendor $1 million in 2025 over compliance claims; see overlays vs real fixes.

A 15-minute check you can do today

1. Using only Tab, Shift+Tab, Enter and Space, find a job and start applying. Can you always see where you are?
2. Submit the first step empty. Do the errors say what to fix, in words?
3. Upload a resume with the keyboard. Is the result shown in text?
4. Zoom to 200% on a phone-width window. Can you still finish the first step?
5. Find how to ask for help applying in under a minute.
6. Run the free homepage scan for code-level problems.

What a scan can and can't check here

Our scan is automated, so it finds only part of the barriers on the public pages it visits: missing alt text, unlabelled fields and buttons, low contrast, missing page language and similar code problems. It doesn't submit applications, upload files, sign in to an applicant portal or take assessments, which is why the 15-minute check matters. Our Fix-Pack scans up to 10 public pages and gives copy-paste fixes for your platform. Employment law has its own rules on accommodations in hiring, so check those with your attorney. Platform steps: WordPress, Squarespace, Wix, Webflow. Related: form error messages, accessible contact forms, contractor and home-service websites.

This is general technical guidance, not legal advice, and it doesn't certify compliance with the ADA or any law, or protect against claims.

Want the fixes written for you?

Start with a free homepage snapshot. The $149 Fix-Pack scans up to 10 pages and gives copy-paste fixes for your platform within 48 hours, with a 14-day refund promise. See a sample report first.

This is general technical guidance, not legal advice, and it does not certify compliance with the ADA or any law.

Related guides

• Online course and coaching website accessibility: sales pages, video lessons, quizzes and workbooks
• WCAG 2.2 explained for small-business websites
• Squarespace accessibility fixes: alt text, contrast, forms and more
• Wix accessibility fixes: a practical checklist

All guides

This guide is general technical information, not legal advice. Following it does not certify ADA or any legal compliance. Automated checks find only part of accessibility barriers.