Skip to main content
Accessibility
for teams

Accessibility for product managers

full guide

Each person on your team has their own responsibility to deliver accessible websites. As a product manager, you keep the overview of what needs to be done. This guide is a starting point.

New to accessibility? Where to start as a team

What to do as a product manager

chapter 1

Getting started

Must know: Why accessibility is important

Accessibility helps disabled people use your products and services.

Unfortunately, many websites are not designed and built properly, which makes them difficult or impossible for some people to use.

Web accessibility opens up your products and services to many more individuals, which in turn is good for business. International web standards define what you need to do for accessibility.

  • Accessibility improves user experience for disabled people, older people, and people who use older devices.
  • At some point in their life, everyone will experience a (temporary) disability.
  • Accessibility is a legal requirement in many countries.
  • At least 15% of the world’s population has a recognized disability. Accessibility opens up your services to this market.

Must know: Make accessibility a priority for the team

Learn what your team needs to do to make your services accessible.

The guides for each role and the checklist show what each person on your team needs to do.

It can help to assign a dedicated accessibility champion on the team who makes sure everything is designed and built with accessibility in mind. A champion keeps an eye on it, but accessibility stays everyone’s job.

Learn what accessibility is

Familiarise yourself with the guidelines and best practices.

Make sure you know what accessibility is and where to find the guidelines.

Most of accessibility is covered by the international Web Content Accessibility Guidelines (WCAG) standard. The current version is WCAG 2.2. Get familiar with the guidelines and what it means to make your products “accessible”.

Read the guidelines and one of the many articles and books that cover accessibility, or follow an online course.

Planning and process

Must know: Don’t make accessibility an afterthought

Accessibility should be part of your Definition of Done.

If you want to do accessibility right, you need to bake it into your process. Not as a backlog item or a fix afterwards, but in the Definition of Done.

Make sure to put tests in place throughout the project, just as you would for performance testing or browser compatibility.

Automated tests are a good start, but they find only part of the issues. And you need to check the results for false positives and false negatives. You’ll also need to do manual testing and involve disabled people in your design process.

Where accessibility lives in your process.

Don’t

“Backlog item: fix accessibility issues after launch.”

Do

“Definition of Done: automated accessibility tests pass, and the feature is tested with the keyboard and a screen reader.”

Accessibility takes time

The earlier you start, the less it costs.

Accessibility that is part of a feature from the start costs little extra time. Fixing it after launch means designing, building and testing that feature again. So make sure your team has enough time to design and build new features correctly the first time.

Make sure to reserve time in each sprint to test new features and to improve their accessibility. This includes sprint planning, where you want to take possible accessibility requirements into account.

Where accessibility goes in your planning.

Don’t

“Sprint 12: the accessibility sprint.”

Do

“Every sprint: time to test new features and fix what we find.”

Write accessibility into your user stories

Acceptance criteria make accessibility part of every feature, and testable.

Requirements that only live in a separate document get forgotten. Put them in the user stories and their acceptance criteria, where the team looks when they build and test a feature.

You don’t need separate “accessibility stories” for most features. Add the criteria to the story itself. For a sign-up form, for example:

  • Every field has a visible label.
  • Error messages say what went wrong and how to fix it.
  • You can complete the form with only a keyboard.
  • The focus is always visible.

The Definition of Done covers what applies to every feature. Acceptance criteria cover what is specific to this one. Write them together with your designers and developers: the guides for each role and the checklist give them a starting point.

Budget for audits and research

Plan money for an expert audit and for research with disabled people.

An accessibility audit by an expert tells you what doesn’t meet the guidelines. Plan one before launch and after big changes.

Research with disabled people tells you what it is like to actually use your product. Both find issues that automated tests miss.

Measure your progress

Know where you stand, and whether it gets better.

Start with a baseline: an expert audit of your most important pages and user journeys. It tells you how many issues there are and how serious they are.

Then track a few things over time, for example:

  • the number of open accessibility issues, by severity;
  • whether new features meet your Definition of Done;
  • how many issues users report, and how quickly you fix them;
  • the results of automated tests in your build pipeline.

Automated scores are easy to track, but they show only part of the picture. A score of 100 doesn’t mean your product is accessible. Repeat the audit regularly, for example once a year and after big changes.

To see how well accessibility is part of the way your organisation works, not just your product, use the W3C Accessibility Maturity Model.

Buying and publishing

Must know: Adding a widget doesn’t make your website accessible

Full compliance cannot be achieved with an overlay.

Overlay products cannot help you become fully compliant with accessibility standards, and they cannot eliminate legal risk.

What does help: make accessibility part of your Definition of Done and budget for an expert audit.

Watch out

Be wary of any product that promises compliance with one line of code.

Check what you buy

Products from suppliers are part of your website too.

Many accessibility issues come from things you buy or embed: a cookie banner, a chat tool, a video player, a payment page. Your users don’t know the difference.

Ask suppliers how accessible their product is, and ask for an Accessibility Conformance Report (ACR), often based on the VPAT template. Test the product yourself before you sign, and put accessibility requirements in the contract.

Publish an accessibility statement

Tell users how accessible your website is.

An accessibility statement tells users how accessible your website is, what doesn’t work yet, and how they can contact you when they get stuck. For public sector websites in the European Union, it’s a legal requirement.

Keep it honest and up to date. A statement that lists known issues builds more trust than one that claims everything is perfect.

Legislation and guidelines

chapter 2

Different countries have different laws around accessibility. W3C’s Web Accessibility Initiative has an extensive list of laws and policies around the world.

In the European Union, the European Accessibility Act (EAA) applies since 28 June 2025. It covers many products and services for consumers, such as online shops, banking, e-books and passenger transport. Public sector websites and apps already had to be accessible under the Web Accessibility Directive.

Most laws refer to the Web Content Accessibility Guidelines (WCAG), often through the European standard EN 301 549. Check which version of WCAG your law refers to: EN 301 549 version 3.2.1, for example, refers to WCAG 2.1. Aim for WCAG 2.2 level AA: it includes everything in WCAG 2.1 and adds a few criteria.

Books about accessibility for product managers

reading list