Jira Accessibility Compliance
- Client
- Atlassian Jira · via EPAM
- Role
- Accessibility SME / Lead Engineer
- Timeline
- EPAM · remediation program
Objective
Drive WCAG 2.1 AA remediation across a massive React surface area used by millions of daily users — and leave behind governance so regressions die in CI, not production.
Decision log
Choices under review — why they stuck, and what they cost.
Prioritize high-traffic violation classes over one-off polish
With 2,000+ components in play, triage had to follow user impact and repeatable fix patterns.
Some edge components waited — core journeys and reusable primitives moved first.
LLM-assisted ARIA drafts with human review
Repetitive remediation burned senior hours; Copilot-assisted drafts with SME review compressed cycle time without abandoning judgment.
Required clear review rituals so speed never outran correctness.
Axe gates in CI as non-negotiable
Manual audits alone cannot hold the bar on a living product.
Pipeline noise early on — tuned rules until signal beat friction.
What we built
- Remediation program across 2,000+ React components
- LLM-assisted ARIA fix playbooks with human review
- Axe-integrated CI quality gates
Panel observations · people
Codified remediation patterns other engineers could execute without waiting on a single SME
Paired with teams to teach semantics and keyboard models, not just ticket dumps
Turned accessibility from a late audit into a shared quality gate