The accessibility specialist makes sure the product other designers and engineers are building can actually be used by people who do not navigate it the way the rest of the team assumes — people who use a screen reader instead of sight, a switch device or keyboard instead of a mouse, or who cannot perceive the colour contrast a design system was built around. The primary pull is Protection: the work exists because a population that is easy to design out of a product without anyone intending it needs someone actively keeping the product safe for them to use. Where the UX Designer and Product Designer archetypes in this field are building the experience forward, the accessibility specialist is checking, continuously, whether that experience actually holds for everyone it is supposed to serve.
The daily texture is audit and remediation. Component by component, flow by flow, the specialist tests against the Web Content Accessibility Guidelines (WCAG) — can this be operated by keyboard alone, does this image have meaningful alt text, does this form error get announced to a screen reader, does this colour pairing meet contrast requirements — and writes up what fails as tickets other teams have to prioritise and fix. Automated scanning tools exist and catch a meaningful slice of the work, but they surface only a minority of real-world accessibility problems; the rest requires manually operating the product with the same assistive technology a disabled user would actually use, which is closer to user research than to conventional QA.
The Revelation and Justice gradients run underneath the Protection pull. Most accessibility failures are not deliberate; they are the accumulated effect of a design and engineering culture that defaults to sighted, mouse-using, hearing users without ever deciding to. Part of the specialist's job is making that default assumption visible to people who have never had a reason to notice it, and then making the case — sometimes against genuine indifference, sometimes against outright resistance to the cost — that the fix is worth doing. It is advocacy work as much as technical work, on behalf of a user population that is rarely represented on the team making the decisions.
Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.
Many accessibility roles are created reactively rather than proactively — after a demand letter, a lawsuit, an audit finding, or a public complaint — which means the specialist often inherits years of accumulated technical debt on day one, and the role's early credibility in the organisation is shaped by crisis response rather than by a considered case for inclusive design. That origin story is common enough across the field that it is worth expecting rather than being surprised by.
The credibility fight is a recurring feature of the job. Passing an automated accessibility scanner is not the same as a blind user being able to complete checkout, and convincing product leadership of that distinction — usually after they have already pointed to a clean scan as proof the work is done — is a constant, low-grade negotiation. The specialists who last in the role are the ones who can translate a failed screen-reader test into a business or legal risk that a non-specialist stakeholder immediately understands, not just a WCAG success-criterion number.
The regulatory floor under this work has been rising fast and shows no sign of levelling off — enforcement of the EU's European Accessibility Act began in June 2025 across all 27 member states, with penalties reaching a share of annual turnover for large companies, and the US Department of Justice's ADA Title II digital accessibility rule is phasing in for state and local government sites through 2027 and 2028. That has made headcount for the role expand quickly, but dedicated positions are still thin relative to design and research headcount at most companies, so the market for the specialist title itself is narrower than for UX design generally, even as demand for the underlying skill grows.
There is no single entry path. Some accessibility specialists move in from UX design or UX research after specialising; others come from front-end development, where fluency in semantic HTML and ARIA is a direct asset; a smaller group enters directly via the field's own certifications. The International Association of Accessibility Professionals' CPACC (Certified Professional in Accessibility Core Competencies) is the common non-technical entry credential, covering disability types, law, and organisational strategy; the WAS (Web Accessibility Specialist) credential is the deeper technical certification, generally expected to follow a few years of hands-on remediation experience. Portfolio evidence — documented audits, before/after remediation case studies, and evidence of getting a fix actually shipped rather than just flagged — carries more weight than the certifications alone. Recent salary survey data puts the role's average total compensation meaningfully above general UX design averages, with a further premium attached to the technical WAS certification specifically.
Scanners and AI code assistants compress the mechanical detection-and-patch layer, but surface only a minority of real-world accessibility problems — the manual assistive-technology testing that catches the rest, and the credibility fight of turning a failed test into a business or legal risk stakeholders act on, are not automatable. Regulatory expansion (EAA enforcement from June 2025, phasing-in ADA Title II) is growing demand for the role faster than AI is compressing its mechanical layer.
Headcount keeps expanding as regulatory enforcement widens, even as AI absorbs first-pass scanning and routine remediation suggestions. Specialists who combine AI-assisted triage with genuine assistive-technology testing and organisational advocacy are the most protected. The role stays thinner than underlying skill demand; CPACC/WAS certification plus portfolio evidence remains the credible entry path.
People drawn to Accessibility Specialistare often drawn to these — in the order they're closest. The ones marked sit in a different field entirely.