I’ve spent the last several months deep in ADA and WCAG 2.1 AA remediation work for a client site, and it’s changed how I think about accessibility — not as a legal checkbox, but as a real gap between what a site looks like and who can actually use it.

Here’s the thing nobody tells medium and large business owners: “ADA compliance” sounds like a legal problem, but on WordPress it’s mostly a design and code problem, and for most established sites it’s more contained than leadership expects once you actually scope it.

Why I Bring This Up Unprompted

Demand letters and lawsuits over inaccessible websites aren’t reserved for enterprise-scale companies. Multi-location businesses, franchises, and established regional brands — sites with real traffic and a public-facing footprint — get targeted just as often, sometimes more, because they’re easier to find and represent a bigger perceived payout.

But honestly, the legal risk is the smaller reason to care. When a site works properly with a screen reader or keyboard navigation, it’s usually just a better site — cleaner structure, better contrast, forms that actually make sense. I’ve watched this play out directly on a client engagement: fixing accessibility issues kept surfacing improvements that had nothing to do with compliance and everything to do with usability, at a scale where that usability gap touches thousands of visitors a month.

The Same Issues, Over and Over

Every WordPress site I’ve worked on — including well-resourced sites with in-house marketing teams — hits some version of the same list:

• Alt text missing on images, especially ones dropped in through page builders instead of the media library
• Contrast that fails WCAG ratios even though it looks fine to a sighted eye
• Keyboard traps in menus, sliders, and popups from third-party plugins
• Form fields with no real coded label — just a placeholder that looks like one
• Skip links that are duplicated, broken, or missing
• PDFs that were never tagged, so a screen reader can’t read them at all

None of these are exotic, and none of them are unique to small operations. They’re just easy to miss unless you’re specifically looking — even on sites that have been through multiple redesigns with professional teams. The fix isn’t always where you’d guess, either: alt text lives in different places depending on whether an image came in through the media library or got hardcoded into block markup, and that inconsistency compounds on larger sites with more contributors touching content.

What “Compliant” Actually Means

WCAG 2.1 AA is the standard most legal guidance points to. Four principles: perceivable, operable, understandable, robust. In practice: alt text, contrast, keyboard access, form labels, heading structure, real link text.

It’s a range, not a switch. On a larger site with hundreds of pages and multiple content owners, I usually think of it in letter grades while I’m working through a remediation — some things (contrast, alt text, labels) get fixed fast across the board, others (a broken nav pattern used sitewide, a stack of untagged PDFs in a resource library) take longer and need to be prioritized by traffic and legal exposure.

Where I’d Start, If This Is You

1. Run an automated scan first (WAVE or axe catch the obvious stuff, and at scale they help you prioritize by page traffic)
2. Try navigating your own site with just a keyboard
3. Check contrast on your actual brand colors, not theme defaults
4. Look at alt text coverage across your media library and page builder content — especially on pages built by different contributors over time
5. If you have PDFs posted, particularly in an investor relations, HR, or resources section, test one with a screen reader

You don’t need a full rebuild for any of this, even on a large, established site. Most of the work is targeted — page by page, template by template — and it can move a site from a failing grade to a strong B+/A- without touching the design or disrupting a content team’s workflow.

If your organization is carrying accessibility risk across a large site footprint and needs a clear-eyed audit rather than a vague warning, get in touch. I’ll give you a straight read on scope, priority, and what it would actually take to fix it.