WordPress ADA & WCAG 2.2 AA

WordPress ADA compliance: four different things wrote your HTML.
None of them was you.

A WordPress page is assembled at the moment somebody loads it, out of a theme you bought, a page builder that generates its own markup, a stack of plugins that inject theirs, and whatever your editors pasted in. Every accessibility failure on your site was written by one of those four.

Compliapoint works on WordPress (including WooCommerce) and Shopify sites.

An overlay is a script that changes only what the visitor’s browser shows, after the page has loaded. We work the other way: we find which layer produced each failure and we repair it there, in your child theme, your builder output, your plugin templates and your content.

  • No overlay
  • Survives theme updates
  • U.S.-based

Your theme layer 1

Heading structure, landmarks, link and button semantics, focus states.

Your page builder layer 2

Elementor, Divi, Beaver or Gutenberg, each emitting its own wrappers and headings.

Your plugins layer 3

Forms, sliders, popups, galleries and WooCommerce, injecting markup you never wrote.

Your content layer 4

Media library alt text, pasted tables, uploaded PDFs, embedded video.

40% of all websites run on WordPress — making it the platform we remediate most. If the ADA reaches your business, it reaches your site however it was built, and your theme, plugins and uploaded content are all part of it. — W3Techs, 40.1% as of October 6, 2026

Where the problems live

The four layers, and what each one breaks

Knowing which layer produced a failure is the whole job. Fix it in the wrong place and it comes back on the next update, or it never really went away.

The theme

Your templates decide the skeleton of every page: what is a heading, what is a landmark, what a link looks like when it has keyboard focus.

  • Heading levels skipped in section titles and widgets
  • No skip link, or one that goes nowhere
  • Focus outlines removed for looks
  • Link color the only thing distinguishing a link from text

If your theme carries WordPress’s accessibility-ready tag, that is a floor rather than a finish line. The tag records that the theme met a defined set of requirements when it was reviewed. It says nothing about the three layers stacked on top of it, and nothing about whether your site meets WCAG once your builder, plugins and content are in place.

Can a plugin fix it? Not really. A plugin can bolt a skip link on, but it cannot restructure templates it did not write.

The page builder

Elementor, Divi, Beaver Builder and the block editor each generate their own markup from what you dragged onto the canvas. You chose a look; the builder chose the HTML.

  • Text styled to look like a heading but output as a paragraph
  • Accordions and tabs with no keyboard support
  • Decorative background images carrying meaning
  • Column order on mobile that no longer matches reading order
Can a plugin fix it? No. Builder output is saved in your database and rendered before any accessibility plugin runs.

The plugins

Contact forms, sliders, popups, galleries, booking widgets and WooCommerce all inject their own markup into your pages, and most were not built with assistive technology in mind.

  • Form fields with no label, or a placeholder doing the job
  • Required fields and errors never announced
  • Popups that cannot be closed by keyboard
  • Sliders that auto-advance with no pause control
Can a plugin fix it? Rarely, and never predictably. One plugin patching another is how sites break after updates.

Your content

Years of posts, pages and uploads, added by people who were never told any of this mattered. This layer is usually the largest and the cheapest to put right.

  • Media library images with no alt text, or a camera filename
  • Tables pasted from a word processor with no header row
  • Links reading "click here" or "read more" out of context
  • Uploaded PDFs that are scans of paper
Can a plugin fix it? No. This is your data. Corrections here are stored in your database, so theme and plugin updates don’t touch them.
Specialists, not a scanner

What a WordPress remediation specialist does that a scanner can’t

A scanner reads the finished page. It can report that a form field has no label; it cannot say whether that field came from your theme’s search form, a builder widget, a forms plugin or something pasted into a post. That answer decides where the fix goes and whether it lasts.

Trace

Which layer wrote it

Every finding is followed back through the four layers before anything is changed, and the report names the layer beside the WCAG criterion. That is how a fix lands in a child theme instead of in a patch the next update removes.

Test

Worked through by a person

Each template is used with a keyboard alone and with NVDA, JAWS and VoiceOver. Focus order, what gets announced, and whether alt text actually describes the picture are judgments a scanner cannot make.

Record

A record you can check

For every issue you get the finding, the layer, the fix and the date, made on a staging copy you approve before anything reaches your live site.

Questions to ask any WordPress accessibility provider

  1. Will you change my theme, builder output and content, or install something on top of them?
  2. Does each finding say which layer produced it?
  3. Do you work on a staging copy, and who approves the move to live?
  4. What happens to the fixes if I stop paying you?
  5. Will I get a dated record of what was tested and changed, and do I own it?
  6. Is your price published, and fixed in writing before work starts?

Our answers, in order: we change the source; yes; yes, and you do; nothing; yes, and yes; yes, and yes.

Your three options

What each approach actually does

On WordPress the first two are a search of the plugin directory away, which is why they get mistaken for the third. They are not variations of the same thing.

Option one

An accessibility plugin

Installs into WordPress and adds a toolbar, or adjusts a handful of attributes as the page renders.

What it changes
Adds its own markup on top. Your theme, builder and plugins are untouched.
Honest use
A text-resize or contrast toolbar is a genuine convenience for some visitors.
The limit
It runs last, so it cannot repair the four layers that already produced the page.
Option two

An overlay widget

A third-party script that loads on every page and attempts automated repairs in the visitor's browser.

What it changes
Nothing in your site. Remove the script and every barrier is exactly where it was.
The record
In April 2025 the FTC finalized an order requiring accessiBe to pay $1 million over claims that its widget could make any website WCAG compliant.
The limit
The FTC’s complaint alleged the widget did not make websites WCAG compliant, and the order bars accessiBe from saying it can without evidence.
Option three

Source remediation

We find which of the four layers produced each failure and correct it there, in the source.

What it changes
Your child theme, your builder output, your plugin templates and your content.
If you stop paying us
Nothing happens. The fixes are in your site and they are yours.
What a claim looks at
Your page source, plus a dated record of every change we made.

If you already run one, see how to remove it safely.

Looking for an ADA plugin?

What a WordPress accessibility plugin can and cannot do

If you searched for an ADA or WCAG plugin, this section is for you. We do not sell one, and we will not pretend the good ones are useless. There are three kinds, and they do very different jobs.

Worth having

Checkers

Scan posts and pages while your editors work and flag problems in the content layer before they are published.

An example
Equalize Digital’s Accessibility Checker, with 10,000+ active installs on WordPress.org as of October 2026.
Where it helps
Keeping layer 4 clean once the remediation is finished. We would rather you ran one than not.
The limit
It reports what it can detect; it cannot restructure your theme or builder output, or tell whether alt text is accurate.
Partial

Theme patchers

Add pieces that many themes leave out.

An example
WP Accessibility by Joe Dolson, with 60,000+ active installs: skip links, a missing language attribute, visible focus outlines, labels on the search and comment forms.
Where it helps
Quick, real improvements to common theme gaps.
The limit
Its own description says it is “not intended to make your site compatible with any accessibility guidelines.”
Not a fix

Toolbars and overlays

Add a widget that changes what a visitor sees, or rewrites the page in their browser.

Where it helps
A contrast or text-size toggle can be a convenience.
The limit
Your markup is unchanged, which is the category compared above.

A plugin runs after the page exists, so none of these can tell you which of the four layers produced a failure, or change what your builder stored in the database. That part is the remediation, and it takes a person.

The question everyone asks

Will it survive my next update?

This is the first thing WordPress owners ask, and it deserves a straight answer rather than a reassurance. It depends entirely on which layer the fix was written into.

Survives updates

Content and media

Alt text, link wording, table headers and heading levels in your posts and pages live in your database, so theme and plugin updates don’t touch them.

Stored

Page builder output

What you set inside the builder, such as heading levels, labels and alt text, is saved in the database and survives updates. The markup the builder’s own code produces can change when the builder updates, so any correction there is listed in the record to check afterwards.

Protected

Theme templates

Template fixes go into a child theme, which parent-theme updates never overwrite. If your site has no child theme, we create one as part of the work.

Documented

Plugin templates

Where a plugin supports template overrides we use them, so its updates leave our work alone. Where it does not, we tell you plainly and record it.

Running WooCommerce?

Then you have a fifth layer. E-commerce sites drew 70% of the ADA digital accessibility lawsuits UsableNet counted in 2025, and on WooCommerce the cart and checkout belong to you in a way Shopify’s do not. How much of the checkout we can change depends on which kind you run.

  • Variation selectors reachable by keyboard
  • Cart updates announced, not silent
  • Checkout errors tied to their fields
  • Product gallery focus handled properly
  • Product images given real alt text
Ours to fix

Classic checkout

If your checkout page uses the WooCommerce shortcode, its markup comes from PHP templates. We override those in your child theme’s woocommerce folder, the method WooCommerce documents, where its updates do not overwrite them.

Partly ours

Block checkout

Since WooCommerce 8.3 in November 2023, new stores on block themes get the Cart and Checkout blocks by default. That markup comes from WooCommerce’s own code, not your theme, so a template override cannot reach it. We fix what its settings and styles reach, document the rest, and tell you if moving to the classic checkout is the better answer.

The gateway’s

Card fields

Many payment gateways draw the card number and expiry fields inside a frame served from their own site. That frame is the payment provider’s code, so we test it and record it; the labels and messages around it are ours.

Once, then per image

Products and catalog

A product template is fixed once for every product built from it. Product image alt text is per image: the first 100 images are included, and volume beyond that is quoted.

The engagement

How a WordPress remediation runs

You get a written scope and a fixed price before anything starts, and your live site is never the thing being worked on.

Assessment

Five minutes of questions: your theme, your builder, your plugin list, roughly how many pages, and whether you run WooCommerce or host PDFs. A written scope and price comes back, typically within 24 hours.

Audit on a staging copy

We clone the site and test every template against WCAG 2.2 AA. Each finding names the page, the element, the criterion it breaks, and which of the four layers produced it.

Repairs at source

Child theme for template fixes, builder output for layout, template overrides for plugins, and your media library and content for the rest. Standard turnaround is 7–10 business days, rush 1–3.

Review and documentation

You approve the staging site before anything goes live. You keep an audit report, a dated record of every change, and an accessibility statement for the site.

Straight answers

What WordPress owners ask first

Will a theme update wipe out the fixes?

No, because of where each fix is written. Content and media library corrections live in your database and survive everything. Template fixes go into a child theme, which parent updates never overwrite. Builder settings are stored in the database, not in theme files; the markup a builder generates from them can shift when the builder itself updates, and the record shows what to check.

If your site has no child theme, creating one is part of the work rather than an extra.

Can an accessibility plugin do this instead?

No. A plugin runs after your theme, your builder and your other plugins have already produced the page. It can add a toolbar or adjust a few attributes, but it cannot rewrite the templates that created the problem.

Some of what is marketed as an accessibility plugin is an overlay, the kind of product the FTC’s 2025 order against accessiBe concerned. What each kind of plugin can do is set out above.

Do you work on my live site?

No. Everything happens on a staging copy, you review it, and it deploys when you approve. If you have no staging environment we set one up. Your live site does not change until you say so.

My site was built by an agency. Do you need them involved?

Usually not. We need administrator access, and access to staging if one exists. Every change is documented so your agency or developer can see exactly what was altered and why, which also means they can maintain it afterwards.

What about the PDFs in my media library?

Our audit covers the documents you post as well as your pages, and on WordPress they are a common finding, especially for schools, clinics and government bodies. The assessment counts what you actually have and prices remediation separately, rather than folding a guess into the total.

What does it cost?

It depends on how many screens your site has, which on WordPress means its distinct templates and layouts rather than its URLs, how many builders and plugins are in play, and whether WooCommerce and PDFs are in scope. That is what the assessment establishes, and you get a fixed written price before any work begins. A Complete Package, covering the audit, the remediation and the records, is $4,750, $9,995 or $19,995 by screen count. Current pricing is published here. A theme is counted once however many pages use it; see how that plays out against a vendor that quotes every engagement.

Some eligible small businesses may qualify for the federal Disabled Access Credit for qualifying accessibility expenditures. Ask your tax professional whether your project qualifies. Estimate yours.

Does this cover WooCommerce?

Yes. Product pages, variation selectors, cart and checkout are all audited. A classic checkout is fixed in your child theme; the newer block checkout is WooCommerce’s own code, so we fix what its settings and styles reach and document the rest.

Should I switch to an accessibility-ready theme?

Only if you are redesigning anyway. The accessibility-ready tag means a theme met a defined set of requirements when it was reviewed, which makes it a sound starting point, but switching replaces layer 1 alone: your builder, plugins and content come with you. On an existing site it is usually less work to fix the theme you have, in a child theme.

Can you guarantee I will not be sued?

No, and nobody honest will. The FTC’s 2025 order against accessiBe shows what happens to claims about overlays that outrun the evidence. What we can do is repair the barriers in your source and hand you a dated record of what was wrong, what changed and when, which is the thing that actually helps when a claim arrives.

Not ready for the assessment?

The five-minute assessment is the fastest way to a written price. If you would rather ask something first, use the form and a person answers, typically within 24 hours.

  • Start the assessment instead Five minutes, no sales call, written scope and price. Begin the assessment.
  • Answering a demand letter Time-sensitive work is prioritized and handled separately. Emergency guidance.
  • Not sure WordPress is the issue Compare how the same failures show up on Shopify.

Ask us about your site

Tell us what you need and we will reply, typically within 24 hours. Nothing here is a commitment and you will not be added to a sales sequence.

For example yoursite.com

This opens your email app with the message ready to send, so nothing is stored on this page. You can also write to us directly at info@compliapoint.com.

Find out which layer is failing you

Five minutes of questions about your theme, your builder and your plugins. We come back with a written scope and a fixed price. No call, no obligation, no automatic charge.

Some eligible small businesses may qualify for the federal Disabled Access Credit for qualifying accessibility expenditures. Ask your tax professional whether your project qualifies.

Compare Compliapoint

Compliapoint vs accessiBe · Compliapoint vs AudioEye · Compliapoint vs UserWay · Compliapoint vs EqualWeb · Compliapoint vs Deque · Compliapoint vs EcomBack · Compliapoint vs Accessible.org · Compliapoint vs Accessibility.Works · All 10 providers compared