Design system team weeknotes: Issue 4

Accessibility in our user journeys

With Dave Cunningham’s help we’ve been looking at how we scale accessibility testing into product teams.

What we did

We began by collating everything we would test in a user journey within a spreadsheet. This gave us a sense of the scale of the challenge and quickly realised it would need breaking down.

Automated testing running on coop.co.uk
On the left: Terminal output of the automated tests. On the right the guided manual tests (question and answer at the bottom).
Minor to critical accessibility issues on an online whiteboard

What’s next

We need to flesh out these severity levels further and decide how we group and test them with a product team to see how it works in practice.

Our roadmap

We’ve also done some work fleshing out our roadmap. At a high level this now looks like:

  1. A first pass accessibility framework being used by a product team.
  2. New accessibility documentation in the design system.
  1. Making development of new components easier.
  1. Understand the tech approach for the future
  2. Understand adoption of the current design system with 3rd parties/agencies to identify potential pain points we can fix in future versions
  3. Understand the contribution model of the design system and how we can simplify it in the future, whilst still upholding our high standards
  1. Maintain community input and create backlog of future work.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Matt Tyas

Matt Tyas

168 Followers

Service and interaction design. Product, team management and front-end engineering. matt.tyas.fyi