An effective accessibility specialist job description defines the role’s scope, lists specific technical qualifications, and reflects how the position fits within the organization. A vague posting attracts the wrong candidates. A precise one filters for the people who can actually do the work.
The difference between a strong hire and a long search often comes down to what the job description communicates before a single resume arrives.
| Component | What to Include |
|---|---|
| Role Summary | One to two sentences defining the position’s purpose and reporting structure |
| Core Responsibilities | Specific tasks: conducting audits, reviewing code, creating remediation guidance, writing documentation |
| Required Qualifications | WCAG proficiency, assistive technology experience, accessibility certification preferred |
| Technical Skills | Screen reader proficiency, HTML/CSS/ARIA knowledge, familiarity with accessibility evaluation tools |
| Soft Skills | Clear written communication, ability to translate technical issues for non-technical teams |
What Does an Accessibility Specialist Do?
An accessibility specialist evaluates digital products against WCAG conformance standards and identifies issues that prevent people with disabilities from using websites, web apps, mobile apps, and documents. The role spans evaluation, documentation, remediation guidance, and ongoing monitoring.
Some specialists focus on auditing. Others work embedded within development teams, reviewing code during the build process. Many do both. The job description should clarify which model the role follows.
Specialistsmay also produce documentation such as accessibility reports.
Start with a Clear Role Summary
The first section of the job description should state what the role is, who it reports to, and why the position exists. Two to three sentences are enough.
Avoid generic language like “passionate about inclusion.” Candidates reading the posting want to know the scope: Is this a solo practitioner role? Part of a larger team? Consulting-facing or internal? These details determine who applies.
A good role summary example: “The Accessibility Specialist evaluates web and mobile products for WCAG 2.1 AA conformance, produces audit reports and remediation documentation, and advises development teams on accessible implementation. This role reports to the Director of Product and works across all product lines.”
How to List Core Responsibilities
Responsibilities should be specific and action-oriented. Every line item should describe something the person will actually do on a regular basis.
Strong responsibility statements for an accessibility specialist job description include:
- Evaluate websites and web applications against WCAG 2.1 AA or 2.2 AA conformance standards
- Identify accessibility issues using assistive technologies including screen readers, keyboard navigation, and magnification tools
- Write detailed audit reports with documented issues, WCAG criterion references, and remediation guidance
- Review design mockups and development code for accessibility conformance before release
- Produce and maintain ACRs using the VPAT template
- Deliver accessibility training to design and development teams
- Track remediation progress and validate that identified issues are resolved
Each item should map to a real deliverable. If a responsibility does not produce a tangible output, it probably belongs in a different section or should be cut.
Required Qualifications vs. Preferred Qualifications
Separate hard requirements from preferences. Mixing the two discourages qualified candidates who check most boxes but not all.
Required qualifications typically include:
- Working knowledge of WCAG 2.1 AA (or 2.2 AA)
- Experience evaluating websites and applications for accessibility
- Proficiency with at least one screen reader (NVDA, JAWS, or VoiceOver)
- Understanding of HTML, CSS, and ARIA attributes
- Strong written communication skills for producing audit reports and documentation
Preferred qualifications might include:
- IAAP certification (CPACC, WAS, or CPWA)Familiarity with automated scan tools like AXE, WAVE, or Accessibility Insights
- Background in front-end development or UX design
- Experience with different types of screen readers
Technical Skills to Specify
Accessibility work is technical. The job description should reflect that without overloading the listing with every possible tool or technology.
Focus on categories of technical skill rather than exhaustive tool lists:
| Skill Category | Examples |
|---|---|
| Assistive Technology | NVDA, JAWS, VoiceOver, TalkBack, keyboard-only navigation, magnification software |
| Web Standards | WCAG 2.1 AA / 2.2 AA, ARIA Authoring Practices, HTML semantics |
| Evaluation Tools | axe DevTools, WAVE, Accessibility Insights, Colour Contrast Analyser |
| Code Review | HTML, CSS, JavaScript as it relates to accessible component patterns |
| Documentation | Audit reports, ACRs (VPAT template), accessibility statements, remediation tickets |
Screen reader proficiency deserves special emphasis. The ability to evaluate a product using a screen reader separates candidates who understand accessibility theory from those who can identify real-world issues that affect users.
Communication Skills Matter More Than Most Postings Suggest
An accessibility specialist who identifies every issue but cannot explain them clearly creates bottlenecks instead of progress. Written communication is a core function of the role.
Audit reports, remediation guidance, training materials, and ACRs all require the ability to translate technical WCAG criteria into language that developers, designers, and leadership can act on. The job description should explicitly call this out as a requirement, not bury it in a generic “good communication skills” line.
What to Avoid in the Job Description
Several patterns make accessibility job descriptions less effective:
- Listing automated scanning tools as the primary evaluation method. Scans only flag approximately 25% of accessibility issues. A specialist role centered on scan output signals that the organization does not understand the work.
- Requiring five or more years of experience for a mid-level role. Digital accessibility is a relatively young field. Certification, demonstrable skill, and portfolio work are stronger indicators than years alone.
- Using vague titles like “Accessibility Advocate.” Clear titles attract candidates who are searching for the actual role.
- Omitting the WCAG version and conformance level the role targets. Specifying WCAG 2.1 AA or 2.2 AA signals that the organization understands the standards.
Setting Expectations Around Tools and Platforms
If the organization uses a specific accessibility tracking platform or project management workflow, the job description should mention it. Accessibility Tracker Platform and similar tools increasingly define how specialists organize, prioritize, and report on their work. Familiarity with these systems can be a meaningful advantage.
However, tool-specific experience should land in the preferred qualifications section. The core skill is accessibility evaluation and documentation. The tools are learnable.
Sample Accessibility Specialist Job Description Structure
A complete posting follows this structure:
- Role summary (2-3 sentences defining scope, reporting line, and purpose)
- Core responsibilities (6-10 specific, action-oriented items)
- Required qualifications (5-7 non-negotiable skills and experience)
- Preferred qualifications (3-5 items that strengthen a candidacy)
- Compensation range and benefits
- Equal opportunity statement
Organizations that include compensation ranges in accessibility postings tend to attract stronger candidate pools. The field is competitive, and experienced specialists compare opportunities quickly.
Does the Role Need a Certification Requirement?
IAAP certifications (CPACC, WAS, CPWA) validate knowledge, but they do not replace practical experience. A candidate with a WAS certification and a portfolio of audit work is a stronger match than one with certification alone.
Listing certification as preferred rather than required keeps the candidate pool open to highly skilled practitioners who may not have pursued formal credentials. Accessible.org and other organizations in the accessibility space evaluate candidates based on demonstrated ability alongside credentials.
What WCAG version should the job description reference?
WCAG 2.1 AA is the current standard referenced by most regulations, including ADA Title II and the EAA. WCAG 2.2 AA is the latest published version. Specifying “WCAG 2.1 AA or 2.2 AA” in the job description covers both and signals the organization is current on standards.
Should the job description mention legal requirements like the ADA or EAA?
Yes, if the role involves compliance documentation or the organization operates in regulated sectors. Mentioning ADA compliance requirements or EAA obligations helps candidates understand the legal context they will work within.
How does an accessibility specialist role differ from an accessibility engineer?
An accessibility specialist typically focuses on evaluation, documentation, and guidance. An accessibility engineer writes and implements accessible code directly. Some roles blend both functions. The job description should clarify which side of the work the position emphasizes.
Can a single accessibility specialist cover an entire organization?
It depends on the organization’s size and the number of digital products. A single specialist can be effective for small to mid-size organizations with a few products. Larger organizations with multiple web properties, apps, and document libraries typically need a team.
A well-written accessibility specialist job description does more than fill a position. It communicates the organization’s understanding of accessibility work and attracts candidates who can deliver real results.