Product owners

Let's set realistic goals, prioritize work and write accessibility acceptance criteria

Why this matters

There are a lot of ways to explain the benefits of accessibility, especially if product managers are hesitant to adopt it or view it as a cumbersome requirement.

Team alignment

Can explain why accessibility is a requirement

Team members possess varying levels of understanding.

The minimum level garners compliance. But when the reasons are taken to heart, your team’s performance can dramatically improve.

Accessibility isn’t just the right thing to do, it’s the smartest thing to do.

Living your organization’s values

Every organization has a set of values, often including core ethical tenets like treating people with respect and doing the right thing.

How does accessibility fit those values? How does ignoring accessibility breach them?

A tool for innovation

Accessible design and development builds better products for everyone. When teams put accessibility at the beginning of their processes, they create more valuable products for your enterprise.

Competitive advantage

26% of the US population has a disability that requires accommodation, making people with disabilities the largest minority in the United States. This adds up to billions of dollars in combined purchasing power.

Accessibility is the law. Designing and building accessibility into products also helps the enterprise avoid legal risk and liability due to a customer complaint.

Adds feature specific accessibility acceptance criteria

Developers will need specific testable criteria to hold them accountable.

Product owners can use MagentaA11y.com to generate acceptance criteria and simplify the process of accessibility testing.

It’s an intuitive way for product teams to define “done” in a way that ensures accessible experiences work for everyone.

Attends design systems reviews

Product owners and managers must attend design reviews with the design systems team. While the design system team exists to support the success of products, it also enables designers to make the best choices for the customer.

What happens when product owners don’t participate

Feedback given from the design systems reviews to the designer becomes a game of telephone. The product owner’s absence also creates opportunity to allow an inaccessible product to be launched, since not every designer is comfortable standing up to their management team.

Accepts guidance from design systems reviews

Product owners and managers must be willing to attend and accept guidance from design systems reviews. The design system team will be advocating for the best customer experience and taking accessibility into account.

Facilitates use of design annotation for developers

Communication needs to be more than designers throwing design over the wall to developers. Designers can leave notes or even use a specific annotation kit to describe the experience for people using assistive technology.

Expects product demos with assistive technology

Create the expectation for teams to demo features with assistive technology. This reinforces the importance of accessibility to the organization and doesn’t allow teams to hide from requirements.

Your checklist

Download checklist
Team alignment
Download checklist