Accessibility Engineer, Design Systems

remoteo; Barcelona; Híbrido; EUR 70.000 - 90.000; Jornada completa

Descripción de la vacante

remoteo is seeking a senior Accessibility Engineer to join a design systems team on a contract basis. The role focuses on making accessibility default as part of a web component library used across a large global organisation.

You will remediate findings, test components to WCAG and EN 301 549, document guidance, and help shape AI-driven workflows for accessible output. Barcelona preferred; London also considered, with overlap with US colleagues.

Formación

• Experience delivering accessible design systems.
• Strong knowledge of WCAG and EN 301 549.
• Hands-on testing with screen readers and keyboard navigation.

Responsabilidades

• Remediate: fix findings as a developer through to release.
• Assess: test components with automated/manual testing against WCAG/ EN 301 549 and raise tickets.
• Document: write guidance for docs and AI usage.
• Shape the future: integrate accessibility into AI workflows for accessible outputs.

Conocimientos

TypeScript

Web Components

Shadow DOM accessibility

Node & build pipelines

WCAG EN 301 549

Herramientas

Deque axe DevTools

NVDA

JAWS

VoiceOver

Descripción del empleo

Make accessibility the default for an enterprise design system

We are looking for a senior Accessibility Engineer to join a design systems team on a contract basis. The team owns a web component library used by product teams across a large global organisation to build accessibly by default. An ongoing accessibility sweep has produced a sizeable backlog, and you will bridge engineering, testing and design systems to clear it and raise the bar for everything that follows.

This is a European role (Barcelona preferred, London also considered), with EN 301 549 central to the work. The contract starts as soon as possible and runs to 30 June 2027. You will need to overlap with US colleagues until around 2pm ET (8pm CET) on Tuesdays to Thursdays; Mondays and Fridays are flexible.

What you will do

• Remediate: pick up existing sweep findings, understand them in a design system context and fix them as a developer through to release.
• Assess: test components not yet swept using the team's established framework, combining automated, semi-automated, manual and usability testing against WCAG and EN 301 549, and raise clear tickets.
• Document: write guidance that works both for people who read documentation and for people building with AI.
• Shape the future: bring accessibility expertise into the team's agentic AI workflow so new output starts accessible, and help create skills for teams composing with the components.

What you will bring

• Strong TypeScript and Web Components experience, including what Shadow DOM means for accessibility, plus Node and standard build and deploy pipelines.
• In-depth knowledge of WCAG and EN 301 549, grounded in fundamentals that let you spot and call out AI errors.
• Hands-on testing with Deque axe DevTools, NVDA, JAWS and VoiceOver, keyboard-only testing, screen magnification and contrast tooling.
• A real understanding of how disabled people use assistive technology, with a usability-first approach rather than box-ticking compliance.
• Clear written communication: what the issue is, why it matters and its impact on the user, plus accurate ticket scoping and estimation.
• A self-sufficient, proactive mindset that drives work forward once you are up to speed.

Nice to have

• Switch access testing experience
• Mobile accessibility testing
• IAAP WAS certification
• Experience with Copilot, Claude Code or other agentic workflows
• Some React exposure

How you will work

You will join a Scrum team with daily contact, a product owner and sprint planning, working closely with an accessibility developer and tester. There is a weekly sweep triad and a weekly remediation session with the accessibility team, within a wider group of around 30 people across the US.

The interview process has two stages: a live walkthrough of how you would test and approach an unseen component, then a short exercise reviewing AI-generated component output, presenting your findings, user impact and fix sizing.