Use the arrow keys to navigate between menu items.

The Product Owner's guide to accessibility debt: Trade-offs wrap up

1 minute read

Over the past few weeks, we've been exploring how we can measure and prioritise accessibility debt in a way that works for us.

The thing is, accessibility debt will feel overwhelming most of the time. And you'll face some choices along the way you'd rather not have to deal with. This forces you to make some trade-offs when prioritising accessibility.

In order to tackle it systematically and effectively, we talked about quite a few tactics. You can go back and read through them in case you missed any:

Throughout these emails, I've been stressing that accessibility is a shared responsibility that requires consistent effort across the entire team. You can't think of it as a one-time fix and you can't outsource that responsibility either. Not if you want to avoid blocking ongoing work all the time.

For that, you need to build accountability for accessibility debt.

Building team accountability is the last point I want to tackle, for now, on the topic of accessibility debt.

Did you enjoy this bite-sized message?

I send out short emails like this every day to help you gain a fresh perspective on accessibility and understand it without the jargon, so you can build more robust products that everyone can use, including people with disabilities.

You can unsubscribe in one click and I will never share your email address.