Free check

Can you fix website accessibility without a redesign?

Usually, yes. Most accessibility barriers come from a small number of templates, components and style rules that repeat across a site. Fix those once and every page that uses them improves. A full redesign is the exception, not the starting point.

Published by Web Accessibility Fix

Why fixes travel further than you’d expect

A typical small-business site might have dozens or hundreds of pages but only a handful of building blocks: a header and menu, a footer, a few page templates, a contact or booking form, product or service cards. When an audit finds a problem, the first question is which building block it comes from. A missing label on the newsletter field in the footer is one fix, even if it shows up on every page.

One template fix reaches every pageA single footer template, marked as fixed, connects to six pages that all use it. Fixing the template once fixes the problem on all six pages.Footer templatelabel added onceHomeServicesAboutContactBook a visitEvery other page
Most barriers come from shared building blocks. One fix in a shared template reaches every page that uses it.

What usually gets fixed in place

  • Form labels and error messages. Adding real labels, connecting error text to its field, and making sure errors are announced.
  • Buttons and menus. Turning clickable <div>s into real buttons, so they work with a keyboard and announce whether a menu is open.
  • Keyboard focus. Removing CSS that hides the focus outline and adding a clear, on-brand focus style.
  • Color contrast. Nudging a few theme colors, usually without changing the look people recognize.
  • Images and icons. Writing useful alt text, and naming icon-only links and buttons.
  • Structure. Fixing heading order, adding landmarks and a skip link so assistive technology can find its way around.

Here is what one of those changes looks like in code. The menu looks the same before and after; only how it behaves for keyboard and screen-reader users changes.

Before

<div class="menu-toggle" onclick="openMenu()">☰</div>

After

<button class="menu-toggle" aria-expanded="false"
        aria-controls="site-menu">Menu</button>

When a rebuild is worth considering

Sometimes fixing in place costs more than it saves. That tends to happen when:

  • the platform doesn’t let anyone change the parts that cause the barriers, such as some hosted site builders’ core templates;
  • an essential feature depends on a third-party widget that can’t be made accessible and has no accessible alternative;
  • the site was hand-built page by page, so there are no shared templates to fix once;
  • a redesign is already planned, in which case it’s cheaper to build accessibility into the new site from the start.

Even then, the most damaging barriers can often be fixed on the current site so customers aren’t blocked while the new one is built.

How to find out which situation you’re in

  1. Run the free check on your homepage and your most important form. It shows the most common patterns quickly.
  2. Get an audit that maps each confirmed issue to the template or component it comes from. That map is what tells you how much work the fix is.
  3. Fix the shared building blocks first, then the one-off content.
  4. Re-test, and keep a dated record of what was tested and changed.

That’s how we work: remediation in your existing site wherever possible, and a straight answer when something can’t be fixed in place.