keepcalculator

06 Numbers and Powers

Accessibility Overlays: Do They Make WordPress Sites Compliant?

Card No. 06·71429 · Updated · Standard formula, shown below

Accessibility overlays do not make a WordPress site compliant with WCAG or the ADA. They can help with minor issues, but they cannot fix underlying code problems, and they often introduce new barriers for assistive technology users.

What Are Accessibility Overlays?

Accessibility overlays are third-party scripts or plugins that claim to automatically improve a website’s accessibility. They typically inject JavaScript and CSS into your WordPress site to alter how it looks or behaves. Common features include a toolbar that lets users change font size, contrast, or cursor size, and automated attempts to add ARIA labels, fix color contrast, or make images “accessible.”

Overlays are sold as a quick fix—install the plugin, paste a snippet, and your site is supposedly compliant. In reality, they are a layer on top of your existing code, not a replacement for proper development. The World Wide Web Consortium (W3C), which publishes the WCAG guidelines, has explicitly stated that overlays do not make a site compliant and can actually harm accessibility.

How Overlays Work (and What They Miss)

An overlay runs in the browser after your page loads. It scans the DOM (the page structure) and tries to patch issues. For example, it might attempt to add alt text to images that lack it, or adjust colors to meet contrast ratios. However, these automated changes are often inaccurate:

  • Alt text: An overlay cannot understand the meaning of an image. It might generate “image001.jpg” or a generic description, which is useless for screen reader users.
  • ARIA labels: Adding incorrect ARIA attributes can confuse assistive technology, making navigation worse.
  • Focus management: Overlays often break keyboard focus order, so tabbing through the page becomes unpredictable.
  • Performance: The extra JavaScript can slow down your site, which is itself an accessibility issue for users on slow connections.

Even if an overlay fixes a few visible issues, it cannot address underlying problems like improper heading structure, missing form labels, or inaccessible custom widgets. These require manual code changes.

Why Overlays Don’t Achieve Compliance

Compliance, whether with WCAG 2.1 AA or the ADA, is about meeting a set of technical standards. Overlays do not change your site’s underlying code; they only patch it in the browser. This means:

  • Source code remains broken: Screen readers and other assistive tools often read the raw HTML, not the patched version. If your HTML is invalid, the overlay can’t fix that.
  • Dynamic content: Overlays often fail on content loaded via AJAX or JavaScript, because they don’t re-scan the new content properly.
  • User control: Many overlays add a toolbar that changes the site’s appearance. While this sounds helpful, it can interfere with a user’s own browser or assistive technology settings, and it does not address the root cause.

The W3C’s “Accessibility Overlay” resource page lists multiple ways overlays can fail, including hiding content from screen readers and creating confusing focus orders. In short, an overlay is a band-aid, not a cure.

The Legal Reality

Lawsuits under the ADA have targeted companies using overlays, arguing that the overlay itself is a barrier. Courts have not universally ruled on overlays, but the trend is clear: overlays do not shield you from liability. In fact, some plaintiffs’ lawyers specifically test sites with overlays and find them non-compliant. The Department of Justice has stated that the ADA applies to websites, and while there is no official technical standard, WCAG 2.1 AA is the de facto benchmark. Overlays do not meet that benchmark.

If your site is sued, an overlay will not help your defense. You would still need to demonstrate that your site meets WCAG, and an overlay is not evidence of that.

What Actually Makes a WordPress Site Compliant?

True compliance requires a systematic approach:

  1. Audit your site: Use tools like WAVE or axe to find issues, but also test manually with a screen reader and keyboard-only navigation.
  2. Fix the code: Ensure proper HTML semantics, alt text, form labels, heading hierarchy, and color contrast. This may require editing theme files or hiring a developer.
  3. Use accessible themes and plugins: Choose themes that are built with accessibility in mind. Many popular themes are not fully accessible.
  4. Provide accessible content: Write clear link text, use descriptive headings, and add transcripts for videos.
  5. Test regularly: Accessibility is not a one-time task. As you add content or update plugins, new issues can appear.

WordPress itself has made strides, with the default themes being more accessible, but that does not guarantee your site is compliant. Each page, post, and element must be checked.

Alternatives to Overlays

Instead of an overlay, consider these options:

  • Accessibility plugins for manual fixes: Plugins like WP Accessibility (free) help you add skip links, remove title attributes, and make minor fixes, but they don’t claim to be a full solution.
  • Hire an accessibility expert: A professional can audit your site and fix issues in the code. This is the most reliable path to compliance.
  • Use an accessibility statement: Be transparent about your efforts and provide a way for users to report issues. This does not make you compliant, but it shows good faith.

Costs and Risks of Overlays

Overlays are often cheap or free, which is their appeal. But the hidden costs are significant:

  • Legal risk: If you are sued, the cost of defense far exceeds any savings.
  • Reputation: Users who encounter barriers may share their negative experience.
  • Maintenance: Overlays can break when you update WordPress, themes, or plugins, requiring constant attention.

Investing in proper accessibility from the start is more expensive, but it is a one-time cost that improves your site for everyone.

Frequently Asked Questions

Can an overlay make my site ADA compliant?

No. The ADA does not specify a technical standard, but courts and the DOJ look to WCAG. Overlays do not meet WCAG because they do not fix the underlying code.

Are there any overlays that work?

Some overlays can help with minor issues, like adding skip links or adjusting contrast, but none can make a site fully compliant. They are best used as a supplement to manual fixes, not as a replacement.

Do overlays hurt SEO?

Potentially. Overlays add heavy JavaScript, which can slow down your site and hurt your Core Web Vitals. They can also hide content from search engine crawlers if not implemented correctly.

Can I just use the WordPress accessibility plugin?

There is no single plugin that makes your site compliant. Plugins can help with specific tasks, but you still need to audit and fix your theme and content.

What is the best way to test my site for accessibility?

Use automated tools like WAVE or axe for a quick scan, but also test manually with a screen reader (like NVDA or VoiceOver) and keyboard navigation. Combine both for a thorough check.

How long does it take to make a WordPress site compliant?

It depends on the size and complexity of your site. A small site might take a few days, while a large site with many custom features could take weeks or months. It is not a quick fix.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →