Inclusion &
Accessibility

Accessibility isn't a final check. It is how I remove unnecessary effort from an experience.

Standards and assistive technology matter. I start one step earlier: understanding the barrier, the context around it and the product decision that created it.

Start with the barrier

Who might struggle here, and why?

The answer might involve vision or motor control. It might also involve language, memory, anxiety, tiredness or a noisy environment. Good accessibility lowers the hidden cost of using a product.

Design beyond the fix

Good design is accessible design. Accessible design should still feel like good design.

When an accessibility issue exposes a barrier, I do not want the solution to stop at making a task technically possible. I look for a response that improves clarity, confidence or ease for the people directly affected, while creating a more thoughtful and delightful experience for everyone. Accessibility defines who must not be excluded; it should not put a ceiling on craft or delight.

How this shows up in my work

Accessibility becomes meaningful when it changes a decision, a component or the way a team builds.

Design beyond colour

State, progress and meaning should remain clear without depending on colour alone.

Fix the pattern

When a barrier appears in one screen, I look for the reusable pattern behind it.

Build it into the system

Tokens, component guidance and review habits help good decisions survive implementation.

Reduce cognitive load

Clear language, structure and predictable interactions matter as much as technical compliance.

Design beyond the fix

Removing the barrier is the baseline. I look for ways the solution can make the experience clearer, calmer or more enjoyable for everyone.

Questions I use

Useful constraints for the beginning of the work—not a checklist at the end.

  • Who might struggle here, and why?
  • Can this be understood without colour?
  • Can this be completed with a keyboard?
  • Does the language reduce cognitive load?
  • What happens when something goes wrong?
  • Does the solution merely remove the barrier, or improve the experience?

Principles I try to follow

  • Design for people, not personas.
  • Reduce cognitive load before adding functionality.
  • Don't rely on colour alone.
  • Make interactions predictable.
  • Build accessibility into systems, not individual screens.
  • Follow accessibility through implementation.
  • Treat access as the baseline, then design for delight.