Accessibility is Innovation

Designing for screen readers, keyboard navigation and cognitive load forces decisions that a purely visual process lets you avoid. You have to know what each element is, not just what it looks like. You have to define an order for things. You have to name your controls.

Those are not accessibility tasks. They are design tasks that accessibility makes non-optional. The interfaces that come out the other side tend to be simpler, more predictable and easier to maintain, because ambiguity that would have survived a visual review does not survive a keyboard test.

This is the same reason curb cuts, captions and voice control all ended up used overwhelmingly by people they were not designed for. Removing a barrier for someone at the edge usually removes friction for everyone in the middle.

The single highest-leverage accessibility decision is using the right element. A button element is focusable, keyboard-operable and announced as a button with no extra work. A div styled to look like a button is none of those things until you reimplement all of them, usually incompletely.

Landmarks matter for the same reason. Header, nav, main, footer and properly nested headings give screen-reader users a way to skip straight to what they came for, in the same way a sighted user scans a page. A document built entirely from divs offers no such shortcut.

ARIA is a supplement, not a substitute. The first rule of ARIA is not to use it if a native element will do — an incorrect ARIA role actively misleads assistive technology in a way that no markup at all would not.

Insufficient colour contrast is the most common, and the easiest to fix. Light grey placeholder text, low-contrast disabled states and pale text over photographs account for a large share of real-world failures.

Missing or useless alternative text is second. An image that conveys information needs alt text describing that information; an image that is purely decorative needs an empty alt attribute so screen readers skip it. A filename is never an acceptable answer.

Keyboard traps and invisible focus states are third, and the most damaging. If a user can tab into a modal and not out of it, or cannot see which element is focused, the interface is unusable without a mouse. Removing focus outlines for aesthetic reasons — without replacing them with something visible — is still distressingly common.

Forms round it out: inputs without associated labels, error messages conveyed only by turning a border red, and required fields marked only with a colour.

Around one in five people has a disability of some kind. Excluding them is both a moral problem and a straightforwardly commercial one, and in Australia the Disability Discrimination Act applies to web services — WCAG 2.1 Level AA is the standard normally referenced.

The SEO overlap is real but frequently overstated, so it is worth being precise about it. Alt text, a sane heading outline, descriptive link text and semantic landmarks genuinely help crawlers understand a page, because search engines parse structure much the way assistive technology does. Accessibility is not a ranking factor in itself — but the practices largely coincide.

The cheapest time to do any of this is during design. Retrofitting accessibility into a finished build is the expensive path, and it is the one most projects take.