Accessibility is not just visual

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. Accessibilityservice×AccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service→ is about interactionglossary×InteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term→, not just appearance.

Some of the biggest accessibilityservice×AccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service→ 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.

Part of why this happens is that the visual layer is the part everyone in the room can assess. A contrast ratio can be checked in a design review by anyone. Whether a form announces its errors sensibly cannot, so it tends not to come up until somebody specifically goes looking.

Take navigationglossary×NavigationNavigation is the system of menus, links, and cues that lets people move through a product and reach what they need. It exposes the underlying structure, and is how most users experience that structure.Open glossary term→ as an example. On screen, a navigation systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ might feel clear and well organised. Labels are short, the layoutglossary×LayoutLayout is the arrangement of elements on a page or screen, determining how content is organised and presented. It influences readability, usability, and overall experience.Open glossary term→ 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.

The usual culprit is meaning carried by position rather than by structure. A column of links reads as a group because of where it sits on the page. Strip the layoutglossary×LayoutLayout is the arrangement of elements on a page or screen, determining how content is organised and presented. It influences readability, usability, and overall experience.Open glossary term→ away and it becomes an undifferentiated list, unless the markup says what the grouping is and where it starts and ends.

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 usabilityglossary×UsabilityUsability is how easy and efficient it is for users to complete tasks within a product. It focuses on clarity, simplicity, and reducing effort so users can achieve their goals without confusion or friction.Open glossary term→ perspective, everything is harder than it should be.

Error handling is where most of it goes wrong. A message that appears in red next to a field is obvious on screen and invisible to somebody who has just submitted and been returned to the top of the page with no announcement. They know something failed. They have no way of knowing what.

Placeholder text is the other recurring problem. Used instead of a label it looks tidy, disappears the moment somebody starts typing, and leaves anyone who paused mid-form with no way to recall what the field was for.

Accessibilityservice×AccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service→ is about how content is structured so it can be understood in different formats. About how interactionsglossary×InteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term→ 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: screen readerglossary×Screen ReaderA screen reader is software that reads digital content aloud for users who cannot see the screen.Open glossary term→ 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.

When you can't rely solely on visual cues, you're forced to make interactionsglossary×InteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term→ clearer. When content needs to make sense when read aloud, it becomes more structured and easier to follow. When navigationglossary×NavigationNavigation is the system of menus, links, and cues that lets people move through a product and reach what they need. It exposes the underlying structure, and is how most users experience that structure.Open glossary term→ 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 accessibilityservice×AccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service→ start to uncover issues they wouldn't otherwise have seen. That insight is what drives better design.

This is the argument that tends to land with teams who see accessibilityservice×AccessibilityFind accessibility issues early, improve usability, and build products that are more inclusive, usable, and compliant.Open service→ as extra work. Designing for the harder cases produces clearer labels, more predictable structure, and interactionsglossary×InteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term→ that survive being used quickly or under pressure. Those are the same properties that make a product good for people who have no access need at all.