You don’t have to fix everything at once, and you don’t have to be an expert to begin. What matters is the order. If you start by fixing old issues, the team adds new ones every sprint, and you never catch up.
This is a suggested order, not a schedule. Some steps take a day, others take months. Each step links to the guide that explains it.
Step 1: Find out where you stand
Who: the whole team, led by the product manager.
- Choose the tasks that matter most. Think of logging in, searching, ordering or getting in touch. An issue there stops people from doing what they came for. An issue on a page nobody visits can wait.
- Do a quick check yourself. Try those tasks with only a keyboard, at 400% zoom and with an automated tool. The checklist helps you get started.
- Get a baseline. For the complete picture, have an accessibility specialist audit those tasks against WCAG 2.2. Read more in Budget for audits and research.
- Learn the basics together. Everyone reads What is accessibility? and the guide for their own role.
Step 2: Stop adding new issues
Who: the product manager, designers, developers and testers.
Fixing old issues makes little sense while every new feature adds more. So start with the way you work:
- Add accessibility to your Definition of Done, so every feature is checked. Read more in How to include accessibility in the Definition of Done.
- Write it into your user stories. Acceptance criteria make it testable. Read more in Write accessibility into your user stories.
- Reserve time in every sprint, instead of planning one accessibility sprint. Read more in Accessibility takes time.
- Annotate your designs, so developers don’t have to guess. Read more in Annotate your designs.
- Run automated checks in your pipeline, so nobody has to remember. Read more in Run automated checks in your pipeline.
- Add a few questions to code review. Read more in Include accessibility in code review.
Step 3: Fix what’s there
Who: the product manager sets the priorities, designers and developers fix.
- Start with what blocks people in your most important tasks. An issue that stops someone from finishing a task comes before one that only slows them down.
- Fix it in the component, not on the page. If your buttons, forms and dialogs come from a design system or a component library, one fix helps every page that uses them. Read more in Check a component library before you trust it.
- Check what you buy. A cookie banner, a chat tool or a payment page from a supplier is part of your website too. Read more in Check what you buy.
- Publish an honest accessibility statement. Say what doesn’t work yet, and when you plan to fix it. Read more in Publish an accessibility statement.
Step 4: Keep it up
Who: everyone, with an accessibility champion who keeps an eye on it.
- Test every release by hand, with a keyboard, at 400% zoom and with a screen reader for the main tasks. Read more in Do a short manual test every release.
- Measure your progress. Track the open issues by severity, and repeat the audit regularly, for example once a year and after big changes. Read more in Measure your progress.
- Do research with disabled people. They find problems that no checklist does. Read more in User research and usability testing.
- Choose an accessibility champion. A champion keeps an eye on it, but accessibility stays everyone’s job. Read more in Make accessibility a priority for the team.
What not to start with
- An overlay or accessibility widget. Adding a widget doesn’t make your website accessible. Read more in the guide for product managers.
- A perfect automated score. Tools find only part of the issues. A score of 100 doesn’t mean your website is accessible.
- One big accessibility project. A project ends; accessibility doesn’t. It works best as part of the way you already work.