Think Build Implement Repeat
Web Development

Web Accessibility Without the Panic or the Overlay

Last updated:

Two reasons to care, one of which is commercial

The first reason is that a meaningful share of your visitors have a permanent, temporary or situational impairment — including everyone using a phone in bright sunlight or one-handed on a train. Accessible design is better design for all of them.

The second is legal exposure, which varies by jurisdiction and by what your organisation does, but is trending in one direction everywhere. Neither reason requires perfection; both reward steady, unglamorous work.

The seven fixes that cover most real problems

  1. Colour contrast. Light grey on white is the single most common failure, and it is a design habit rather than a technical constraint.
  2. Keyboard navigation. Everything usable without a mouse, with a visible focus indicator. Menus and modals are the usual offenders.
  3. Form labels. Properly associated labels, not placeholder text pretending to be one.
  4. Alt text that describes the meaning, with decorative images marked as such rather than described.
  5. Heading structure that reflects the document, since screen reader users navigate by headings.
  6. Descriptive link text. “Read the pricing guide” rather than “click here”.
  7. Visible, dismissible everything — no keyboard traps in cookie banners, chat widgets or overlays.

Why overlay widgets are not the answer

The one-line script promising instant compliance is appealing and does not work. It cannot fix underlying structure, it frequently interferes with the assistive technology people already use, and it is rejected by many of the people it claims to help.

The uncomfortable detail: several high-profile accessibility complaints have been filed against sites that had an overlay installed. Buying one is not a defence and may be evidence you knew there was a problem.

Test with three cheap methods

  • Automated scanning for contrast, missing labels and structural errors. Catches perhaps a third of issues, in minutes.
  • Keyboard-only navigation. Put the mouse away and try to complete your main conversion path. Ten minutes, remarkably revealing.
  • A screen reader for fifteen minutes on your key pages. Uncomfortable at first and worth more than any report.

Build it into the process instead of the annual panic

Retrofitting accessibility is expensive; building it in is nearly free. Contrast decided at design time costs nothing. Labels written correctly the first time cost nothing. A component library that is accessible once is accessible everywhere it is used.

Add it to the definition of done for new work and let the existing site improve as it gets touched, prioritising the pages that carry traffic and conversions.

A realistic first project

For a typical business site, an audit plus the seven fixes above is generally two to four weeks of work and £4,000–£12,000. That will not make you formally compliant with every criterion, and it will remove most of the barriers real people hit.

Then keep a short accessibility statement on the site describing where you are and how to report a problem. It is honest, it is useful, and it is far better received than silence or a false claim of full compliance.

Frequently asked questions

Which standard should we aim for?

WCAG 2.2 at level AA is the working target most organisations and regulators reference. Level AAA is not expected across a whole site and is impractical for most content.

Is our site legally required to be accessible?

It depends on your jurisdiction, sector and whether you provide services to the public, and this is a question for a lawyer rather than a developer. The commercial and ethical case usually settles it before the legal question needs answering.

Will accessibility work hurt our design?

It constrains contrast and requires visible focus states, which some designers resist. In practice it tends to improve clarity. Nothing about accessible design requires ugliness.

How much does a proper audit cost?

£2,000–£6,000 for a manual audit of key templates with a prioritised remediation list. Automated-only reports are cheaper and miss most of what matters.

Keep reading

Want to know where you stand?

We will run the three cheap tests on your main conversion path and tell you what a real user would hit. No overlay will be recommended.

Book a free 30-minute call Get a project estimate WhatsApp us

Related services

What we build for problems like this one

Web DevelopmentCustom Software Development