Accessibility as a UX practice
Design for keyboards, screen readers and real world conditions.

Zander Whitehurst
9 min read
Accessibility is often treated as a checklist at the end of a project. A quick audit, a few fixes, a box ticked. But accessibility is really a core part of user experience. It is about making sure products work for everyone, including people with disabilities, temporary injuries or difficult situations.
I will be honest: for years I thought of accessibility as someone else's job. Then I watched a screen reader user try to navigate a product I had designed. It was painful. Buttons had no names. Headings were missing. Focus jumped around randomly. That session changed how I design forever.
Accessibility helps everyone
Accessibility features help far more people than you might expect. Captions help people in noisy cafes. High contrast helps people using their phone in bright sunlight. Keyboard navigation helps power users. Clear language helps everyone.
Designing accessibly simply means designing well for a wider range of people and situations.
Start with contrast
Text needs enough contrast against its background to be readable. The WCAG guidelines recommend a contrast ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text.
Check contrast for text, icons and important UI elements like borders on inputs. Light grey text on white backgrounds is one of the most common accessibility failures.
Do not rely on colour alone
Some people cannot distinguish certain colours. If you use only colour to communicate meaning, like red for errors, those people miss the message.
Pair colour with text, icons or patterns. An error should have a clear message as well as a red border.
Design clear focus states
Keyboard users rely on focus states to know where they are on the page. Removing focus outlines because they look untidy makes products unusable for them.
Design focus states deliberately. A clear, visible outline that fits your visual style is both accessible and attractive.
Use real structure
Headings, lists, buttons and links should be real semantic elements, not just styled text. Screen readers use this structure to help people navigate.
As a designer, you can help by clearly marking heading levels, labelling interactive elements and documenting the intended reading order in your designs.
Make touch targets comfortable
Small touch targets are hard for everyone, especially people with motor impairments. Aim for at least 44 by 44 pixels for interactive elements on touch devices.
Leave enough space between targets so people do not accidentally tap the wrong thing.
Write clear content
Plain language helps people with cognitive disabilities, people reading in a second language and people who are simply busy. Use short sentences, clear headings and familiar words.
Label form fields clearly, explain errors helpfully and avoid relying on instructions like "click the green button on the right".
Respect motion preferences
Some people experience discomfort or dizziness from animation. Respect the reduced motion setting by simplifying or removing non essential animations when it is enabled.
Include disabled people in research
The best way to understand accessibility is to learn from disabled people directly. Include them in usability testing and research. Their insights often reveal issues no checklist would catch.
Make it part of your process
Build accessibility into every stage of design:
- Check contrast while choosing colours
- Annotate headings and focus order in designs
- Include accessibility criteria in design reviews
- Test with keyboard and screen readers before shipping
When accessibility is part of the process from the start, it costs far less than fixing problems later. Our UI Design Bootcamp builds these checks into every project.
Start today
Try navigating your product using only a keyboard. Then try it with a screen reader for five minutes. You will learn more in those few minutes than from any article, including this one.
Memorisely