


Accessibility has become part of most web teams’ workflows – as we realize that it’s the right way to build and that it increases the number of people who can use (or buy!) our products. There are also legal obligations, such as the European Accessibility Act, which took effect on 28 June 2025.
Luckily, your design system can help! Components don’t just improve your design and development workflows; they can actually have a massive impact on product accessibility. Let’s examine five key aspects we can test and document during development.
Note: Accessibility exists in context, so if you’re testing WCAG conformance, do it on full pages and processes.
People use all sorts of input devices to interact with your UIs, whether that’s a touch screen, a mouse, or a keyboard. To make sure your components work well with just a keyboard, as WCAG 2.1.1 requires, check that any element that a user can click on – such as links, buttons, and form controls – can also be activated using a keyboard.
If there are many controls within one component (for example, a selection widget, toolbar, or calculator), you usually don’t want them all to go into the Tab order. For complex controls, the expected behavior is that the user can tab to the control and then navigate within the control itself using arrow keys. For instance, in a calendar picker, the user would access the picker with the Tab key and then navigate between days with their arrow keys.

Some things to test for keyboard accessibility:
Design tokens are a great way to document your design decisions in one place. They are also an opportunity for accessibility. The default values for your tokens can set the right example.
The three types of tokens most important for accessibility are:
If your design system allows for documentation, *cough zeroheight cough*, take that opportunity to remind colleagues about accessible defaults while they’re in the right frame of mind.
Some things to test for design tokens:
People who use screen readers can navigate by specific types of content. They can pull up a list of all the headings, form controls, or links. These lists lack context, however, so it’s super important for the items to be self-explanatory.
Imagine a list of links that goes like this:
Without context, it would be impossible to make out where each of them goes. Users are left with no other option but to try them all. If, instead, we make sure the link text clearly conveys what it links to – for example, “About us”, “Products”, or “Contact us” – everyone saves time.
A similar principle applies when using controls, like buttons and form fields, on a website: You’ll want them all to have a name that clearly describes what will happen.
Some things to test for control names:
Lots of users zoom in when they use your application. For UI design, that means your available space will vary. Especially when zoomed in, less space means you’ll need to get creative.

People may also be using platform-specific preferences: from color preferences (like dark mode on macOS/iOS and forced colors on Windows) to reduced motion.
Some things to test for zoom and user preferences:
To get your components to work well with screen readers, they need to expose the so-called “accessibility meta information” for each element they contain. Broadly, it comes down to information about:
aria-multiline).
We only need to add and check for these, if they are elements that are identified in ARIA.
Note that some elements already include implicit metadata. For instance, a button element has a button role built in, so it’s not necessary to add one.
It’s also perfectly fine for elements to not have any roles, states, or properties. If it’s just text, for example, it’s just text.
This is what to test for screenreader compatibility (use the browser’s accessibility tree):
In addition to these checks in the browser, also test in real screen readers, such as VoiceOver on the Mac and NVDA or JAWS on Windows. Or, even better, test with users who rely on them, so that you can get the most realistic feedback on whether your UI works well.
In this post, we’ve looked at five things you can test against all of your design system components. They give you a fast, practical way to catch accessibility issues at the component level.
Conducting these tests doesn’t replace a full WCAG evaluation. They need the context of whole websites and apps. However, these tests give you a head start: Mistakes are a lot cheaper to fix in a component than after an application goes live.
