Skip to main content
Accessibility
for teams

Where to start with accessibility as a team

article

You know your website should be accessible. But where do you start when there’s already a website, a backlog and a deadline? First find out where you stand, then stop adding new issues, then fix what’s there.

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:

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.

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.