How Atlassian is improving accessibility for public sector teams preparing for ADA Title II
If you work at a state or local government agency, public school, or public university, you may be reviewing the accessibility of the tools your team uses ahead of the ADA Title II web and mobile rule deadlines. For teams serving the public, accessibility affects whether people can get information, request services, and do their work using tools such as screen readers, voice input, or a keyboard.
I want to share where Atlassian’s accessibility work stands, what we’re doing next, and where you can check our progress for yourself.
Here’s a practical look at our progress, and how to get help.
How we’re improving our products
Inside Atlassian, we are very busy working on existing barriers while building accessibility checks into design, development, and testing. Our goal is WCAG 2.2 Level AA alignment across our products, and while that work is still ongoing, we are working with customers to ensure we prioritize those experiences that are most critical to users. Here’s a snapshot of the progress and processes we’ve shared:
- Fixing existing barriers: Our teams are addressing accessibility barriers across our cloud products, prioritizing issues in key user journeys across our product suite, and continuing to work on more complex challenges such as content reflow.
- Building accessible design foundations: Our Design System components target WCAG 2.2 Level AA. Designers and engineers also have accessibility annotations and guidance to use when building product experiences.
- Checking designs early: Accessibility checks in our design tools review prototypes for issues such as focus order, labels, and keyboard access. In validation testing, these checks reduced potential design-origin defects by nearly 80% before development began.
- Checking code before release: Automated linting and continuous integration checks help teams find issues earlier. More than 30% of detected defects are now caught at the pull request stage.
- Helping teams fix issues faster: Our AI-assisted pipelines inspect eligible backlog issues, propose fixes for specific WCAG criteria, and open pull requests for review by engineers.
- Improving contrast at the system level: After reviewing hundreds of contrast patterns, our teams built contrast formulas into color tokens to help prevent recurring issues across product interfaces.
- Tracking remediation timelines: Our service level objectives require committed timelines for accessibility bugs, based on the impact the users.
- Testing with people who use assistive technology: We work with independent accessibility specialists and people who use screen readers and alternative inputs to test real workflows, alongside automated checks.
- Sharing progress publicly:
- Recognizing the team’s work: Atlassian received a Tech for Good Merit Award at the 2026 TechDiversity Awards for its accessibility program.
Questions or accessibility barriers? Get in touch
If you’re evaluating Atlassian products for Title II or have found an accessibility barrier, we’d like to hear from you. Here are two ways to reach us:
- Report a barrier or ask a question: Use the Accessibility Support Portal or contact us at a11y@atlassian.com.
- Plan a product evaluation: Talk with your Atlassian account team about technical briefings, product roadmaps, or procurement requirements.
