Accessibility Is Engineering, Not Compliance

Accessibility usually enters a project late, as a remediation exercise driven by legal exposure. An audit produces a list of violations, a developer works through it, and the site technically conforms. It also frequently remains unusable for the people the work was supposed to serve.

The framing is the problem. Accessibility is not a category of defect to be cleared — it is a property of well-built interfaces, and it is far cheaper when it is designed in.

Automated Tools Find a Minority of Issues

Automated scanners reliably catch contrast failures, missing alt attributes and absent form labels. They cannot evaluate whether alt text is meaningful, whether focus order matches visual order, whether a custom component behaves correctly with a screen reader, or whether an error message actually explains how to fix the problem.

A clean automated report is a floor, not a result. It is worth being explicit about that internally, because a green dashboard creates false confidence.

Semantic HTML Does Most of the Work

The majority of accessibility issues stem from rebuilding native elements out of generic containers. A real button is focusable, keyboard-operable, announced correctly and styleable. A div with a click handler is none of those things until a developer reimplements each behaviour, usually incompletely.

Use the native element. Reach for ARIA only when there is genuinely no HTML equivalent — incorrect ARIA is worse than none, because it actively misleads assistive technology.

Keyboard Navigation Is the Fastest Check

Put the mouse aside and complete a core task using only the keyboard. Focus indicators must be visible at every step, order must follow the visual layout, modals must trap focus and return it on close, and nothing may become unreachable.

This takes minutes and surfaces more real problems than most formal audits.

Motion, Contrast and Reading Comfort

Respect the reduced-motion preference — parallax and large transitions cause genuine physical discomfort for some users. Verify contrast against the actual backgrounds used, including text over images. Let text reflow when zoomed to two hundred percent rather than clipping it.

Build It Into the Definition of Done

Remediation projects are expensive because they mean revisiting finished work. Accessibility criteria in the component definition of done, linting in the pipeline, and keyboard checks in code review cost a fraction of the same work done afterwards.

The Commercial Case Is Real

A substantial share of the population has a disability affecting web use, and the same properties that help them — clear structure, keyboard operability, sufficient contrast, meaningful markup — improve usability for everyone and are read directly by search crawlers.

Building it in is simply better engineering. The compliance benefit is a side effect.