Seven Accessibility Principles Every Product Designer Should Apply

Black and white photo of a young Black man wearing glasses and headphones, sitting in a wheelchair in his living room. He smiles while looking at his phone and adjusts his headphones with his other hand.

Accessible UX design means building digital products that work for people across a wide range of abilities, contexts, and circumstances, not a checkbox for a small “edge case,” but a mindset that improves usability for everyone. This article walks through seven practical principles that changed how I approach product design, from thumb-reachable layouts to error messages that actually help people move forward.

I still remember the first time I watched someone use a screen reader to navigate a product I’d designed.

What seemed straightforward on my monitor became a maze of unlabelled buttons. My carefully chosen colours? Meaningless to someone who couldn’t see them. My elegant animations? Annoying interruptions that couldn’t be skipped.

That moment changed everything. Not because I became an accessibility expert overnight, but because I realized: designing accessible products isn’t about following rules, it’s about understanding people.

Here are seven principles that transformed how I approach UX. None are particularly complicated. But together, they’ve helped me create products that work for more people, in more situations, than I thought possible.

1. Design for one-handed use (because life happens)

Here’s a truth we rarely discuss: most people don’t use their phones with two hands, perfectly centred in their vision, sitting comfortably at a desk.

They’re holding a shopping bag. Carrying a baby. Eating lunch. Standing on a crowded metro. Or they have arthritis. Or a broken arm. Or they’re just tired.

What this means in practice:

Place critical actions within thumb reach on mobile, roughly the bottom two-thirds of the screen. If someone has to stretch their thumb to the top corner to hit “Save,” you’ve made their life harder. And not just for people with motor disabilities. For everyone.

The beautiful thing? When you design for someone with limited mobility, you also design for someone holding their toddler’s hand, someone with their arm in a cast, or someone trying to buy concert tickets while running to catch a train.

Quick test: Can you complete core tasks using only your thumb? Try it right now with your product. It’s enlightening.

2. Stop designing for perfect conditions (because they don’t exist)

We design in controlled environments. Bright screens. Quiet rooms. High-speed internet. Then we’re surprised when our designs fail in real life.

I learned this watching my mum try to read 11-point grey text on white outside, in the sun, with her glasses perched on her head. That “elegant” low-contrast design? Completely illegible.

What this means in practice:

Design for chaos. For glare. For spotty wifi. For distraction.

Use high contrast, a minimum ratio of 4.5:1 for normal text, as set out in the WCAG 2.1 Level AA success criteria. Make text resizable without breaking layouts. Provide offline states. Don’t rely on colour alone — someone might be colourblind, or viewing your product in direct sunlight where everything washes out.

Test in greyscale. Step outside with your laptop. Try your product while someone talks to you. These aren’t edge cases, they’re everyday reality.

3. Write like you’re explaining to a friend (because jargon excludes people)

Ever seen “Configure authentication parameters to proceed with credential validation”? I hate it.

Clear language isn’t just for people with cognitive disabilities. It’s about respecting everyone’s time and mental energy. We’re all cognitively impaired when we’re stressed, tired, or multitasking, which is most of the time.

What this means in practice:

If you can say it in five words, don’t use seven. If you can use a common word instead of a technical term, do it.

“Enter your password” beats “Input authentication credentials.” “Try again” beats “Retry operation.” Simple, direct language works for everyone, from developers to grandmothers using your app for the first time.

And when you must use technical terms? Explain them. Right there. Not hidden behind a tooltip someone has to hunt for.

4. Make errors helpful, not punishing (because mistakes are human)

Confession: I’ve designed error messages that just said “Error occurred.” No explanation. No guidance. Just... error. I cringe thinking about it.

Errors are stressful for everyone. But especially for people with anxiety, cognitive disabilities, or those less confident with technology. A vague error message can turn a small mistake into a reason to abandon your product.

What this means in practice:

Tell people exactly what went wrong and how to fix it. Near the field with the problem, not at the top of a long form.

“Password must be at least 8 characters and include a number” is helpful. “Invalid input” is not.

“Your card was declined. Please check the card number and expiry date, or try a different payment method” is helpful. “Payment failed” is not.

And if someone makes the same mistake twice? Maybe the problem isn’t the user. Maybe your form is confusing.

5. Let people control the experience (because one size never fits all)

Auto-playing videos. Animations you can’t pause. Font sizes you can’t change. Colour schemes burned into the design.

Every time we remove control, we exclude someone. Someone with vestibular disorders who gets dizzy from animations. Someone with dyslexia who needs larger line spacing. Someone with light sensitivity who desperately needs dark mode.

What this means in practice:

Respect system settings. If someone has chosen dark mode, honour it. If they’ve set text to large, don’t override it. If they’ve disabled animations, don’t force fancy transitions.

Provide pause buttons on anything that moves. Let people stop videos, carousels, notifications. What’s ambient background to you might be a migraine trigger to someone else.

And when people customize something — their dashboard, their notifications, their accessibility settings — remember those choices. Don’t make them reconfigure everything every login.

6. Design for interruption (because focus is a luxury)

I used to design flows assuming people would complete them in one sitting, with full attention. Then I became a parent.

Now I understand what it’s like to have your attention constantly fractured. To start something and forget what you were doing. To lose your place because your toddler decided to draw on the wall.

What this means in practice:

Save progress automatically. Don’t make people start over if they leave. Show them where they are in multi-step processes. Make it obvious how to pick up where they left off.

This isn’t just for parents or people with ADHD. It’s for anyone who lives in the real world, where phone calls happen and deliveries arrive.

Don’t punish people for having lives outside your product.

7. Test with humans, not just tools (because empathy requires connection)

Automated accessibility scanners are brilliant. I use them. But research from Deque Systems suggests they catch only around 20–30% of WCAG failures, they’re good at flagging things like missing alt text, but they can’t tell you if that alt text is actually useful.

The turning point for me was watching someone who’s blind navigate a prototype. She patiently explained why “image” as alt text told her nothing. Why identical “click here” links left her guessing. Why our “intuitive” visual groupings meant nothing because screen readers read everything in order.

What this means in practice:

Test with real people who use assistive technologies. Not once, at the end. Throughout the process. And don’t just test for compliance, test for experience.

Better yet, hire people with disabilities on your team. Because they bring perspectives you’re missing. Because they’ll catch issues before they become problems. Because accessibility shouldn’t be retrofitted, it should be built in from the start.

And when someone tells you something is hard to use? Believe them. Listen, learn, make it better.

The truth about accessible design

Accessible design is harder. It takes more thought, more testing, more humility. You can’t just design for yourself and people like you.

But accessible design is also better design. More usable. More resilient. More human.

Every time I’ve made something more accessible, I’ve made it better for everyone. The ramp for wheelchair users? Also helps people with pushchairs. The captions for deaf users? Also help people in noisy environments. The clear language? Helps literally everyone.

That’s the secret: accessibility isn’t separate. It’s just good UX.

These seven principles won’t make you an accessibility expert. But they will make you a more thoughtful designer. Someone who considers more perspectives. Someone who builds products that work for more people, in more situations.

Start small. Pick one principle. Apply it to your next project.

You might be surprised how much better your work becomes when you design for the messiness and diversity of real human life.

FAQ

What does “accessible UX design” actually mean?

‍It means designing digital products so people with a wide range of abilities, devices, and situational contexts, not only people with permanent disabilities, can use them effectively.

Is accessible design only relevant for people with disabilities?

‍No. Situational and temporary limitations (a broken arm, bright sunlight, a distracted parent, a slow connection) affect everyone at some point, and accessible design improves the experience for all of them.

Can automated tools fully test for accessibility?

‍No. Automated scanners like axe or WAVE typically catch around 20–30% of WCAG failures. Manual testing with real assistive-technology users is needed to catch the rest, especially issues around meaning, context, and usability.

What’s the minimum colour contrast ratio for accessible text?

‍WCAG 2.1 Level AA requires a contrast ratio of at least 4.5:1 for normal text (3:1 for large text).

Where should I start if I can only apply one principle right now?

‍Pick whichever feels most relevant to your current project. Thumb-reachable actions and clear error messages tend to be the quickest wins with the biggest impact.

Other insights

Inside Hyphen: Exploring UX Trends and Perspectives with Our Deep Insights Series

Inside Hyphen: Exploring UX Trends and Perspectives with Our Deep Insights Series

The Deep Insights Series is Hyphen's programme of sessions with external guests on how AI is reshaping UX design, product strategy, and design work. Six editions in, it's covered everything from AI workflows to building agents and sustaining design systems. Each session starts from a real theme, shaped with the speaker so people leave with something usable. This looks behind the scenes at how it's built and what we've learned.
The myth of human error

The myth of human error

Accidents blamed on "human error" are often design failures — at Three Mile Island, a misleading indicator light stopped operators from closing a valve and nearly caused a nuclear disaster. The same pattern plays out in today's poorly designed digital systems, with costs ranging from frustration to real danger. The fix: involve human-centred designers from the start and never launch without usability testing.