Accessibility Compliance Without a Rebuild

Somewhere in your inbox, or your lawyer's inbox, or the inbox of a business owner you know, there's a demand letter about website accessibility. These letters follow a template: your site fails to meet WCAG standards, this violates the ADA (or your country's equivalent), and you can settle now or find out what litigation costs. The letters work because they're mostly right about the first part. Many small-business websites fail WCAG in several ways, and the failures are visible to anyone running an automated scanner from their couch.

This is general information, not legal advice. Which rules apply to you depends on your country and your business, so check with a qualified advisor.

The standard panic response is to either buy an accessibility overlay widget or budget for a full rebuild. Both are usually the wrong move. Overlays don't fix the underlying problems , and a rebuild is a long and expensive answer to a problem you can meaningfully shrink in a few working days. This post is about the middle path: fixing the issues that most often draw complaints, in priority order, without touching your theme's foundations.

Understand what actually triggers complaints

Accessibility complaints don't sample randomly from the WCAG checklist. They tend to cluster around a handful of failures because those are the ones automated scanners catch and the ones that make a site genuinely unusable with a screen reader or keyboard. A commonly cited order, with no claim about exact frequency:

• Images without alt text — the single most-cited issue, because it's trivially detectable and genuinely blocks screen reader users.
• Forms without labels — a contact form where the fields are only identified by placeholder text is invisible to assistive technology.
• Insufficient color contrast — light gray text on white, white text on pale brand colors. Scanners flag this instantly.
• Missing or broken keyboard navigation — menus that only open on hover, modals that trap focus, carousels you can't skip.
• No captions on video — if video is central to your content, this one escalates quickly.
• Vague link text — a page with fourteen links that all say 'click here' or 'read more' is a mess when read as a link list.

Notice what's not on the list: perfect ARIA implementation, exotic screen reader edge cases, or pixel-level conformance debates. The risk tends to concentrate in the basics. That's good news, because the basics are fixable without a rebuild.

Run your own scan before someone else does

The plaintiffs' side of this industry uses automated tools. You should use the same ones first. Three free options cover most of what you need:

• WAVE (browser extension) — visual overlay showing errors in place on the page. Best for understanding where problems live.
• Lighthouse (built into Chrome DevTools) — gives an accessibility score per page. Useful for tracking progress over time.
• axe DevTools (browser extension) — the most thorough of the three for catching contrast and ARIA issues.

Don't scan every page. Scan the pages that matter legally and practically: your homepage, your contact page, any page with a form, your main product or services pages, and your checkout flow if you have one. A reasonable rule of thumb: if a page gets more than a few percent of your traffic or sits on the path to a transaction, it's in scope for the first pass. An old blog post about your office move is not where the risk lives.

Keep the reports. Dated scan results become part of your paper trail, which matters more than most owners realize — more on that below.

The triage order: fix in this sequence

Work through issues in order of legal visibility multiplied by fix difficulty. Here's the sequence that gets the most risk reduction per hour of work.

1. Alt text on images (half a day for most sites)

In WordPress, alt text lives in the Media Library — click an image, fill in the Alt Text field. Two rules make this fast:

• Describe what the image communicates, not what it depicts. A photo on your team page gets 'Maria Chen, head of customer support', not 'woman smiling at camera'.
• Decorative images — dividers, background textures, stock photos that add nothing — should have an empty alt attribute, which tells screen readers to skip them. In WordPress, leaving the field blank on a decorative image accomplishes this in most themes.

A plugin or a quick database query can list every image missing alt text so you can work through them systematically instead of hunting page by page.

2. Form labels (an hour or two)

Every form field needs a visible label associated with it — not just placeholder text that disappears when someone starts typing. Most modern WordPress form plugins (Gravity Forms, WPForms, Fluent Forms) output proper labels by default, but themes and page builders sometimes hide them for aesthetic reasons. If your form fields show placeholder text only, turn the labels back on. Yes, the form gets slightly taller. It also becomes usable and defensible.

3. Color contrast (half a day, mostly decisions)

WCAG AA expects a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. The WebAIM contrast checker tells you in two seconds whether your text-on-background combinations pass. The fix is usually darkening a gray or adjusting a brand color slightly — changes you make in the WordPress Customizer or your theme's settings, not in a rebuild. The most common offenders: light gray body text (#999 on white fails; #767676 barely passes), text over hero images, and white text on pastel buttons.

4. Keyboard navigation (a day, including testing)

Put your mouse aside and Tab through your site. You should be able to reach every menu item, link, and button; see where focus is at all times (a visible outline); and escape any popup with the Escape key. Common failures and fixes:

• Invisible focus indicator — some themes remove the focus outline for looks. Restore it with a few lines of CSS.
• Hover-only dropdown menus — most maintained themes have fixed this; if yours hasn't, a theme update or a small script fixes it.
• Popups that trap or lose focus — check whether your newsletter popup can be dismissed by keyboard. If not, that plugin needs replacing or reconfiguring, not your whole site.

5. Link text and headings (ongoing, start now)

Change 'read more' links to describe their destination ('Read our pricing guide'). Make sure headings nest logically — one H1 per page, H2s for sections, H3s inside them — rather than being chosen for font size. These are editorial habits more than technical fixes, so bake them into how you write from now on and clean up your top pages first.

Why overlays don't get you off the hook

Accessibility overlay widgets — the ones that add a floating icon offering font resizing and contrast toggles — market themselves as one-line compliance. The pitch is appealing and the reality isn't. Overlays sit on top of your broken markup and try to patch it in the browser; they routinely fail to fix form labels, keyboard traps, and structural issues, and many screen reader users disable them because they interfere with the assistive tech they already have configured. Sites running overlays have been named in accessibility lawsuits in significant numbers, which tells you what the plaintiffs' bar thinks of them as a defense.

If you've already bought one, it's not poison — but treat it as a supplement, never a substitute for fixing the underlying issues in the triage list above.

Documentation is half your defense

Here's the part most guides skip: your legal exposure isn't only a function of your site's current state. It's also a function of whether you can demonstrate good-faith, ongoing effort. A site that is mostly conformant with a documented remediation program is in a much better position than a slightly better one with nothing on paper. Build the paper trail:

• Dated scan reports — run your automated scans quarterly and archive the results, including the improving scores.
• A remediation log — a simple spreadsheet: issue found, date found, fix applied, date fixed. It doesn't need to be fancy; it needs to exist.
• An accessibility statement page — a public page stating your commitment, the standard you're working toward (a recognized level such as WCAG 2.2 AA is a sensible target), known limitations, and a contact method for accessibility problems. This page does double duty: it signals good faith, and it gives a frustrated user a route to email you instead of a law firm.
• A response process — decide now who answers accessibility emails and how fast. A same-week reply and a genuine fix can resolve many complaints before they escalate.

What actually requires bigger surgery

Honesty requires acknowledging the cases where triage isn't enough. If your site is built on an abandoned theme with table-based layouts, if core functionality lives inside a Flash-era widget or an inaccessible third-party booking system, or if your page builder generates markup so tangled that fixing one issue creates two — then some structural work is coming. Even then, 'rebuild' is rarely the right frame. Usually it means replacing one component: swapping the booking plugin, rebuilding the navigation menu, or moving to a maintained theme while keeping your content exactly where it is. In WordPress, content and presentation are separate layers, and that separation is your friend here. A theme change is a weekend project; it is not a rebuild.

A realistic 30-day plan

A month of part-time attention takes most small-business sites from 'obvious target' to 'documented good-faith effort with the major issues fixed'. That's not the same as perfect conformance — perfect conformance is a horizon, not a destination — but it removes you from the pool of easy cases, which is where such letters tend to concentrate.

The honest conclusion

Accessibility compliance gets sold as either a checkbox (buy the widget) or a catastrophe (rebuild everything). It's neither. It's maintenance work with a legal dimension: a triage list, a few days of fixes, and a habit of documenting what you've done. The improvements are real for actual visitors — roughly one in six people has some form of disability, and every fix on the list above also helps users on old phones, in bright sunlight, or with a broken trackpad. Do the work in the right order, write it down, and the demand letter that was heading your way finds a softer target.

Photo: Tito Zzzz on Pexels