Over 4,600 federal website accessibility lawsuits were filed in the US in 2025, and small business sites got hit just as often as big brands. If you’re running WordPress and haven’t touched accessibility, your site is probably one of them waiting to happen. This isn’t a legal scare tactic: it’s what a WordPress accessibility checklist actually needs to cover in 2026, and most sites fail on the same handful of fixable issues.
In my 10+ years building WordPress sites and running 950+ Fiverr client projects, I’ve audited a lot of “finished” websites. Almost none of them were built with accessibility in mind from day one. The good news: most violations aren’t a redesign. They’re small, specific fixes you can knock out in an afternoon.
Why This Suddenly Matters More in 2026
WordPress powers 43% of the web, and most of those sites fail basic accessibility checks. That used to be a niche concern for government and enterprise sites. It isn’t anymore. ADA Title III lawsuits keep climbing year over year, law firms actively scan small business sites for violations, and a “demand letter” before a lawsuit is now common enough that I’ve had two clients receive one in the last year alone.
The practical standard almost everyone measures against is WCAG 2.1 Level AA. That’s the bar. Not perfection, not WCAG AAA, just AA. Most small business sites have between 10 and 50 violations sitting on their homepage alone, and the majority trace back to the same root causes: missing alt text, low contrast text, and forms with no labels.
The WordPress Accessibility Checklist That Actually Matters
Skip the 200-item audit checklists. Here’s what I fix first on every site, in order of impact.
1. Alt text on every meaningful image
This is the single most common violation I find, and it’s also the easiest to fix. Every image that conveys information needs alt text describing what it shows, not “image123.jpg” or nothing at all. Purely decorative images (a background swirl, a divider graphic) should have an empty alt="" so screen readers skip past them instead of announcing useless filenames. I covered the broader image workflow, including why this matters for load speed too, in my WordPress image optimization guide.
2. Color contrast that actually passes
Light grey text on a white background looks clean in a mockup and fails WCAG almost every time. The AA standard requires a 4.5:1 contrast ratio for normal text and 3:1 for large text. Run your theme’s text and button colors through a free contrast checker before you ship. This is usually a five-minute fix in your theme’s color settings, not a redesign.
3. Full keyboard navigation
Unplug your mouse and try to use your own site. Can you reach every menu item, open the mobile nav, submit the contact form, and close a popup using only Tab and Enter? On a lot of custom-built menus and modals, the answer is no, because the interaction was built for clicks only. Add a visible “skip to content” link near the top of your header so keyboard users don’t have to tab through the entire nav on every page:
<a class="skip-link screen-reader-text" href="#main">Skip to content</a>4. Form labels, not just placeholder text
Placeholder text disappears the moment someone clicks into a field, and screen readers often skip it entirely. Every input needs a real <label> tied to it. If you’re using a modern form plugin, this is usually a checkbox in the field settings, not custom code. I ran through form plugin options that handle this well in my Contact Form 7 alternatives post.
5. A logical heading structure
One H1 per page, then H2s and H3s that nest in order. I see this broken constantly because designers pick heading tags based on font size instead of structure, skipping straight from H2 to H5 because it “looked right.” Screen reader users navigate by heading structure the way sighted users scan a page visually. If it’s broken, they can’t skim your content at all.
6. Visible focus states
A lot of themes strip the default browser focus outline for aesthetics and never replace it. That leaves keyboard users with zero visual indication of where they are on the page. If your theme removed outline: none on links and buttons, add a visible focus style back in.
7. Captions on video content
Any embedded video needs captions. YouTube’s auto-captions are a reasonable starting point, but they’re often wrong on names, product terms, or accents, so review and correct them rather than trusting them blindly.
The Overlay Plugin Trap (Don’t Fall For It)
If you’ve searched for a fast fix, you’ve seen the accessibility widget plugins: the little floating icon that promises instant WCAG compliance with one line of code. Skip them. Multiple courts have ruled that these overlays don’t protect site owners from ADA lawsuits, because they slap a JavaScript layer on top of broken markup instead of fixing the underlying code. Some plaintiffs’ firms now specifically target sites running these widgets, because the overlay itself is a signal the owner knew about accessibility and chose a shortcut over an actual fix.
Use an accessibility checker plugin to audit your site and show you exactly where the violations are, then fix those issues in your theme and content. Diagnosis tools are useful. Widgets that claim to fix everything automatically are not.
Your Legal Protection Isn’t a Plugin, It’s a Process
The best defense against an ADA complaint isn’t a perfect score on some automated scanner. It’s a documented, ongoing process: a current audit, a log of what you fixed and when, an accessibility statement published on your site, and a habit of checking new pages before they go live. That documentation is what actually matters if a demand letter shows up. I keep this same checklist on hand for every new site build, right alongside the plugins I install on every new site, because accessibility should be part of the build, not a bolt-on after launch.
Start with the seven items above. Fix what you find, write down what you fixed, and repeat the check every time you publish something new. That’s a WordPress accessibility checklist that actually holds up, not just one that looks good on paper.
Frequently Asked Questions
WordPress core and most default themes are built with reasonable accessibility support, but that’s undone fast by third-party themes, page builders, and plugins that don’t follow the same standards. The platform gives you a decent foundation. What you build on top of it determines whether the site is actually accessible.
Yes. ADA Title III has been applied to commercial websites regardless of business size, and small businesses are targeted specifically because they’re less likely to have already fixed the common issues. You don’t need to be a large company to receive a demand letter.
No. Courts have repeatedly ruled that overlay widgets don’t shield site owners from lawsuits, since they add a surface-level layer instead of fixing the actual markup. Some law firms treat the presence of an overlay as evidence the owner knew about accessibility and chose not to fix it properly.
WCAG 2.1 Level AA is the practical standard most businesses and legal frameworks reference. WCAG AAA exists but is far stricter and generally reserved for government or specialized sites. Aim for AA, and treat AAA items as a bonus where they’re easy to hit.
Every time you publish a new page or post, not just once a year. A single audit gets outdated the moment you add a new form, image, or video. Build the check into your publishing habit instead of treating it as a one-time project.
Leave a Reply