Accessibility

Accessibility is not just visual

Accessibility issues often sit in structure, interaction, and behaviour. Focusing only on what appears on screen misses where many of the real barriers actually are.

Why accessible design goes far beyond contrast and typography, and why products only become truly inclusive when they work across different modes of interaction.

26 January 20246 min read

In short

Why accessible design goes far beyond contrast and typography, and why products only become truly inclusive when they work across different modes of interaction.

Why the visual layer is only part of the picture

Once the visual layer looks compliant, there's an assumption that the experience is accessible. In reality, that's only a small part of the picture. is about , not just appearance.

Some of the biggest issues I've encountered have nothing to do with how something looks. They sit in how a product behaves, how it's structured, and how it responds to different ways of interacting with it. You can have perfect contrast and still create something that is difficult to use.

A product can look accessible on screen and still break down completely once the way it is being used changes.

Why navigation changes when visual context disappears

Take as an example. On screen, a navigation might feel clear and well organised. Labels are short, the is clean, and everything looks structured. But when that same navigation is used with a screen reader, the experience changes completely. Items are read in sequence, context is reduced, and relationships between elements aren't always obvious. What made sense visually no longer holds together. If a navigation model only works visually, it's not structurally clear enough to support different modes of use.

Key takeaway

If a navigation model only works visually, it is not structurally clear enough to support different modes of use.

Why forms often fail beyond the visual layer

The same applies to forms. Visually, a form might appear simple: fields are aligned, labels are positioned neatly, the flow feels logical. But if labels aren't correctly associated, if instructions are unclear when read aloud, or if error messages aren't announced properly, the experience quickly breaks down. From a visual perspective, nothing is wrong. From a perspective, everything is harder than it should be.

What accessibility really depends on

is about how content is structured so it can be understood in different formats. About how work when someone isn't using a mouse, or can't rely on precise input. About how information is communicated when visual cues are removed, reduced, or interpreted differently. It's about how the product behaves under different conditions. And those conditions are more varied than most teams expect: users, keyboard-only users, voice control users, those with magnification tools, those dealing with temporary constraints such as injury, fatigue, or poor lighting. Accessibility spans a wide range of situations.

Why designing for multiple modes improves the whole experience

When you can't rely solely on visual cues, you're forced to make clearer. When content needs to make sense when read aloud, it becomes more structured and easier to follow. When needs to work without a mouse, unnecessary complexity is reduced. The experience becomes more resilient. And that benefits everyone, not just those with specific needs. Teams who move beyond the visual layer of start to uncover issues they wouldn't otherwise have seen. That insight is what drives better design.

Written by Andy Scott

Strategic design, UX and digital transformation thinking from real projects.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20