Design system team weeknotes: Issue 5

Show and tell

We’ve not done an external show and tell yet, but we do record the ‘no prep’ show and tells. We felt this show and tell was such a good update (and felt prepped) that we should start inviting external people. In the meantime you can watch the web team show and tell here — same content as the weeknotes, but including Coherence and Efficiency. The Design system update is first lasting about 14 minutes.

We’re almost ready to test our user journey (level 2) accessibility testing framework

We’ve previously written about the levelled approach to accessibility testing we’re developing so far we’ve developed 2 levels, these are:

  • level 2 — the user journey level testing we’re developing now

What we’ve done

This week we began to further filter the areas we need to test. The problem we were solving here was trying to get the issues that must be tested (and fixed if issues are uncovered) down to a manageable amount for teams.

  1. Major issues — things that will make it very difficult for somebody to use our products and services.
  2. Minor issues — things that will make it frustrating for somebody to use our products or services.
Minor and Critical accessibility issues on an online whiteboard
  • allowing people to resize the content
  • making sure videos can be understood with no sound
  • checking that all the parts of each form have text labels
  • not using hovers to reveal extra information
  • if something changes on a page, it must be described to screen reader users
  • the use of semantics, ARIA landmarks and roles
The testing framework level 2 spreadsheet

Making component development easier and better documented

Alongside all of the accessibility work running in the design system team, we’ve also got a functional spike of Storybook up and running — massive thanks to Jiebin Su for all the work he’d done in his own time on starting this up — this allows us to provide an a single repository where anyone can see components and interact with them, change properties etc. and see how they react.

What’s next

We need to finish off our framework spreadsheet and research some of the critical issues further. We’ll then test this framework with the Food digital team in the near future.

Our roadmap and walls

We’ve revamped our web team walls so you can easily see our strategy, goals and roadmaps for the web platform teams in once place.



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


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