DamienKomala.
All articles
UI/UX3 min read

Designing for All Users

Designing for All Users

Accessibility isn't a checklist. It's a mindset, a commitment to making digital experiences usable by everyone, whatever their abilities. Yet it still gets treated as an afterthought. My view is simple.

Accessible design is good design. Inaccessible design is broken design.

Here's why it matters, what it involves, and how to build it into a UI/UX process from day one.

1. Why accessibility matters (beyond compliance)

According to the CDC, 1 in 4 adults in the U.S. has a disability. That covers visual, auditory, cognitive, motor, and neurological conditions. Accessibility also helps people with temporary impairments, like a broken arm, and situational ones, like trying to read a phone in bright sunlight.

So designing for accessibility doesn't leave anyone out. It makes the experience better for everyone.

2. Accessibility is UX

It isn't a separate discipline sitting off to the side. It's part of good UX. If people can't read, hear, understand, or interact with your interface, the product has failed them.

It means clear language, layout, and interaction, predictable structure and navigation, and empathy for different needs and abilities. I think of it as designing with users of all kinds, not just for them.

3. Core accessibility principles in UI/UX

Perceivable. Use enough color contrast to meet the WCAG guidelines, give images alt text, and support screen readers with semantic HTML and ARIA labels.

Operable. Make every function reachable from the keyboard. Avoid flashing content or animation that can trigger seizures. Give interactive elements a visible focus indicator.

Understandable. Write in plain language, keep navigation consistent, and give clear feedback and error messages.

Robust. Stay compatible with assistive technologies, follow web standards, and test across browsers and devices.

4. Common UX mistakes that hurt accessibility

  • Using color alone to carry meaning, such as red error text with no icon or label.
  • Low-contrast text, or form fields labeled only by their placeholder.
  • Overcomplicated animation, or content that's hidden away.
  • Modal windows that trap keyboard focus.

These don't just hurt users with disabilities. They frustrate everybody.

5. How to build accessibility into your design process

  1. Start early. Don't wait for QA. Design with accessibility in mind from wireframes to prototypes.
  2. Use accessible components. Lean on frameworks or design systems that already support ARIA, labels, and keyboard navigation.
  3. Test with real users, especially people who use assistive tech like screen readers.
  4. Automate the checks. Run tools like Axe, Lighthouse, or Wave during development.

It's a process, not a checkbox. You don't need to be perfect. You need to be committed.

6. The ethical (and business) case for accessibility

Inclusive design reaches a wider audience. Accessible sites tend to do better in search. And empathetic UX earns loyal users. Beyond the metrics, it's just the right thing to do.

Final thoughts

Accessibility is about human-centered design, not compliance. Every decision you make, from color to copy to keyboard flow, either opens a door for someone or puts up a barrier.

Next time you're designing a screen, ask yourself: Can everyone use this? Can everyone understand it? Can everyone finish the task?

If the answer to any of them is no, go back and make it better. Accessibility isn't optional.