Swain-Tech Studio websites for small businesses and independent creatives

Accessibility Is Not an Add-On

Accessibility gets treated as a phase — something checked near the end, or bought as a widget. It is not a phase. Almost every failure is a decision made earlier by someone choosing a colour, writing a label, or adding a library.

The 2026 numbers make the case better than an argument would. Where decisions rely on what people say rather than what can be observed, self-reporting bias is a useful caution about self-reported information.

What the data says

WebAIM, a non-profit centre at Utah State University, runs an automated audit of the top million home pages every year. The 2026 report, from February data:

95.9% of home pages had detectable WCAG 2 A/AA failures, up from 94.8% — the first regression in six years.

56.1 errors per page on average, up 10.1% in twelve months.

Six error types account for around 96% of everything detected, and the same six have topped the list for seven consecutive years: low contrast (83.9% of pages), missing alt text (53.1%), missing form labels (51%), empty links, empty buttons, and missing document language. For an independent reference beyond this site, W3C Web Accessibility Initiative is a useful place to compare approaches.

WebAIM attributes the regression to complexity: average page elements rose 22.5% in a year to 1,437, ARIA use rose 27% with much of it implemented incorrectly, and the report points at heavier reliance on third-party frameworks and AI-assisted development.

Note the limit, which WebAIM states itself: automated testing covers only part of WCAG and cannot establish conformance. The real figure is worse than 95.9%, not better.

The uncomfortable reading

Awareness has never been higher, tooling has never been better, enforcement has never been closer — and the numbers went backwards.

The reason is in the complexity figure. Sites are being assembled from more parts, faster, with less inspection. Every framework, component library and generated block arrives with its own markup, and nobody checks whether the button it renders has a name.

Which is the argument of this page. You cannot inspect accessibility into a site at the end. It is a property of how the thing was put together.

The six failures, and what they actually are

Every one is a decision, not a technical shortfall.

Low contrast. Somebody chose grey text on white because it looked refined. On 83.9% of pages. A design decision, made in a mockup, on a good monitor, by someone with good eyesight.

Missing alt text. Somebody uploaded an image and left the field blank. Thirty seconds per image.

Missing form labels. Somebody used placeholder text instead of a label because it looked tidier. The placeholder disappears when typing begins, and it is not announced.

Empty links and buttons. An icon with no text. A "read more" arrow with nothing to read. Common in component libraries.

Missing document language. One attribute in the page's markup. Nothing to do with content at all.

None of these is exotic. All are fixable today, and all were cheaper to avoid than to retrofit.

The overlay problem

A widget promising to make a site accessible in one line of JavaScript is not the answer, and this is now a matter of record rather than opinion: in the same period covered above, the FTC collected a $1 million penalty from an accessibility-widget vendor.

The pattern is the same as security plugins. If the answer to a structural problem is another script layered on top, the structure has not changed — it has just been covered.

The legal position, briefly

Not legal advice, and it varies.

US public bodies: the DOJ's ADA Title II rule sets WCAG 2.1 AA. Compliance dates were extended by a year in April 2026 — April 26, 2027 for entities serving 50,000 or more, April 26, 2028 for smaller ones. The extension changes the deadline, not the underlying obligation.

US private businesses: the legal standard has not changed and litigation has intensified — one tracker counted 4,928 accessibility lawsuits filed in a year.

Europe: the European Accessibility Act came into effect in June 2025, with the first court decisions now landing. It applies to businesses with EU market exposure regardless of where they are based.

For a small business, the legal exposure is real but it is not the main argument, which is simpler: some of the people trying to buy from you cannot.

What I do instead

Check contrast at the design stage, not after. Two minutes, and it removes the most common failure on the web.

Every image gets alt text on the way in. A habit, not a task.

Real labels on every form field. Visible, not a placeholder.

Every link and button says what it does, including icon-only ones.

Navigate the site with a keyboard before launch. Add it to the launch checks. Tab through it. If you cannot reach something or cannot see where you are, neither can a substantial group of visitors.

Prefer fewer moving parts. The complexity finding is not a coincidence — the same restraint that keeps a site fast keeps it accessible.

Then run an automated check, knowing it catches perhaps a third of real problems.

The cost argument

Built in, accessibility costs close to nothing. It is choosing one colour over another and filling in a field you were already looking at.

Retrofitted, it costs a redesign, because contrast, structure and component choices run through everything.

That asymmetry is the whole point of this page. Not that it is a moral obligation, though it is. That it is one of the very few things in this work where doing it properly the first time is the cheap option.

The short version