Is My WordPress Site ADA Compliant?

The Americans with Disabilities Act (ADA) was passed in 1990, before the web existed. Courts have ruled — and the Department of Justice has confirmed — that the ADA applies to “places of public accommodation,” including their websites.

The legal standard for compliance is WCAG 2.1 Level AA — a technical specification covering how websites should work for users with disabilities. WCAG covers four areas:

• Perceivable — content can be seen and heard (alt text, captions, color contrast)
• Operable — interface works with keyboard, screen readers, voice control
• Understandable — clear labels, error messages, predictable navigation
• Robust — works with assistive technologies (screen readers, refreshable braille displays)

The common issues we find on Tampa WordPress sites:

1. Insufficient color contrast

Light gray text on a white background. Light buttons on a light background. Brand colors that look stylish but fail WCAG AA’s 4.5:1 contrast ratio for normal text and 3:1 for large text.

Test it: use webaim.org/resources/contrastchecker. Plug in your text color and background. If it fails AA, you have a violation.

2. Missing alt text on images

Every meaningful image needs descriptive alt text for screen reader users. Decorative images need empty alt (alt="") so screen readers skip them. Most WordPress sites have a mix of:

• Images with no alt at all (violation)
• Images with auto-generated alt like “image-001.jpg” (effectively no alt, violation)
• Images with descriptive alt (correct)

3. Form fields without labels

A form input that says “Name” inside the box (placeholder text) instead of having a proper element. Screen readers can’t reliably read placeholder-only fields.

4. Missing form error messages

When a form fails validation, errors need to be programmatically associated with the field and announced to screen readers. Most default WordPress forms don’t do this without extra work.

5. Keyboard navigation broken

If you can’t tab through your site and reach every interactive element, you have a violation. Common breaks:

• Custom dropdown menus that don’t expand on keyboard focus
• Modal popups that trap focus or can’t be closed via keyboard
• Mobile menus that aren’t keyboard accessible
• Sliders and carousels with no keyboard controls

6. Heading hierarchy broken

Skipping from H1 to H4, having multiple H1s on a page, or using headings for styling rather than structure. Screen reader users navigate by headings — broken hierarchy makes pages unusable.

7. PDF documents

Most PDFs hosted on WordPress sites are not accessible. Scanned-image PDFs without OCR are entirely unreadable to screen readers. Even text PDFs often lack proper structure.

8. Videos without captions

YouTube auto-captions are not WCAG-compliant — they’re not accurate enough. Real captions (manually reviewed) or transcripts are required.

Total perfect WCAG 2.1 AA compliance is genuinely hard and expensive. A “perfect” audit and fix for a 50-page WordPress site can run $5,000 to $20,000, plus ongoing maintenance.

The realistic bar for most Tampa small businesses:

1. Catch the obvious issues — color contrast, alt text, form labels, basic keyboard nav
2. Fix everything an automated scanner catches — covers about 30% of WCAG criteria
3. Manual review of key user flows — homepage, contact, key service pages
4. Document your accessibility efforts — a published accessibility statement helps in litigation
5. Plan ongoing review — re-audit every 6 to 12 months as content changes

This level of compliance significantly reduces lawsuit risk without requiring a $20K audit. It’s also genuinely better for users.

WordPress has gotten better at accessibility over the years. The core is reasonably accessible. The issues come from:

Themes

Most themes have accessibility issues. Look for themes explicitly tagged as “accessibility-ready” in the WordPress.org theme directory. Custom themes (the ones we build) should be designed with accessibility from the start.

Page builders

Page builders vary widely. Elementor has improved but historically had issues with focus management and ARIA. Bricks is reasonably accessible if used carefully. Native blocks are improving. See best WordPress page builder.

Plugins

Every plugin that adds front-end content (sliders, forms, popups, navigation menus) can introduce accessibility issues. Test after adding any plugin that touches the front-end.

WooCommerce

The default WooCommerce templates have known accessibility issues. Custom WooCommerce builds need explicit accessibility work. See WooCommerce development in Tampa.

Our standard accessibility approach when building a Tampa WordPress site:

1. Pick or build an accessibility-aware theme
2. Color palette tested for WCAG AA contrast during the design phase
3. All images get descriptive alt text during content entry
4. Form fields properly labeled and keyboard accessible
5. Heading hierarchy validated
6. Keyboard navigation tested through key user flows
7. Automated scan with axe DevTools before launch
8. Published accessibility statement at /accessibility/
9. Optional: paid accessibility audit ($500) for higher-risk industries

For clients in healthcare, education, legal, or other high-lawsuit-risk industries, we strongly recommend the paid audit.

Even if your site isn’t fully compliant yet, publishing an accessibility statement at /accessibility/ helps. The statement should include:

• Your commitment to accessibility
• Your target compliance level (WCAG 2.1 AA)
• Known limitations (if any)
• How users can report issues or request accommodation
• Contact info for accessibility concerns

A statement won’t save you from a lawsuit alone, but it demonstrates good faith effort, which courts and plaintiff firms consider.

If you receive an ADA web lawsuit threat:

1. Don’t ignore it. Most plaintiff law firms file if you don’t respond.
2. Don’t panic-pay. Initial demand letters often request $10,000 to $25,000 for what’s actually a $2,000 to $5,000 fix.
3. Hire a lawyer who handles ADA web cases. Florida has several.
4. Get an accessibility audit immediately. Documenting your fix-in-progress is part of negotiation.
5. Fix the actual issues. Settlement usually requires both money and a remediation plan.