WordPress Accessibility: How to Make Your Site WCAG 2.2 Compliant

Picture of Ivan Predojev
Ivan Predojev

Writer

Table of Contents

Most WordPress sites are not built to shut anyone out, yet many do it every day. A menu that only opens on mouse hover, a contact form with no labels, pale grey text on a white background, a video with no captions. Each of these small choices can stop a blind visitor, a keyboard user or someone with low vision from reading your content, booking a call or buying a product. WordPress accessibility is the work of finding and removing those barriers so every visitor can use the site, whatever device or assistive technology they rely on.

It matters for legal reasons too. US businesses receive ADA demand letters over inaccessible websites, public bodies now have a federal web rule with fixed deadlines, and the European Accessibility Act has applied to many online services since June 28, 2025. This guide explains what WCAG 2.2 AA asks for, what the legal picture looks like, why an overlay script will not solve the problem, and how to audit and fix a WordPress site step by step. It is written for small business owners and agencies, and it is general information, not legal advice.

What Accessibility Means for a WordPress Site

When people talk about web accessibility, they almost always mean the Web Content Accessibility Guidelines from the W3C. The current version is WCAG 2.2, first published as a W3C Recommendation on 5 October 2023 and updated in December 2024. WCAG is not a WordPress feature or plugin setting. It is a set of testable rules that apply to any web page, whether it was built with Gutenberg, Elementor, Divi or custom code.

The guidelines are grouped under four principles, often shortened to POUR. Every success criterion sits under one of them, and they are a useful lens for looking at your own site before you open any testing tool.

PrincipleWhat It MeansWordPress Example
PerceivablePeople can see, hear or otherwise take in the contentAlt text, captions, enough color contrast
OperableEvery control works, including with a keyboardMenus, sliders and popups that work without a mouse
UnderstandableContent and controls behave clearly and predictablyForm labels, clear errors, consistent navigation
RobustContent works with browsers and assistive technologyClean HTML, correct ARIA, buttons that are real buttons

WCAG has three levels: A, AA and AAA. Level A covers the most basic barriers, AA adds the requirements most laws and policies point to, and AAA is a stricter level few sites aim for across the board. When a client, lawyer or regulator talks about an accessible website, they almost always mean Level AA.

WordPress core takes accessibility seriously, with a dedicated accessibility team and an “Accessibility Ready” tag in the theme directory. The weak points are usually the layers on top: the theme, the page builder, sliders, form plugins and the content editors add every week. That is why a site can launch in good shape and drift out of it within months, and why accessibility belongs in the same routine as updates, backups and security checks.

What WCAG 2.2 AA Actually Requires

WCAG 2.2 AA contains dozens of success criteria, and the full standard is long. In practice, a small group of criteria explains most of the problems found on real WordPress sites, so understanding them covers the bulk of what an audit will flag.

According to the W3C’s summary of what is new in WCAG 2.2, version 2.2 adds nine success criteria to WCAG 2.1 and removes one, 4.1.1 Parsing, which is now obsolete. Six of the new criteria are at Level A or AA. They focus on keyboard focus, touch targets, dragging, help and login flows, which are exactly the areas where modern themes tend to struggle.

CriterionLevelWhat It Asks ForCommon WordPress Problem
1.1.1 Non-text ContentAText alternatives for images and iconsEmpty alt text, icon buttons with no label
1.3.1 Info and RelationshipsAVisual structure also exists in the codeFake headings made with bold text
1.4.3 Contrast (Minimum)AA4.5:1 for normal text, 3:1 for large textLight grey text, text on busy hero images
2.1.1 KeyboardAEverything works with a keyboardHover-only menus, sliders and popups
2.4.7 Focus VisibleAAYou can see where keyboard focus isThemes that remove the focus outline
2.4.11 Focus Not Obscured (Minimum)AA (new)Focused items are not fully hiddenSticky headers and cookie bars covering links
2.5.8 Target Size (Minimum)AA (new)Targets at least 24 by 24 CSS pixels, or enough spacingTiny social icons and close buttons
3.3.8 Accessible Authentication (Minimum)AA (new)Logins without memory or puzzle testsLogin forms that block password managers
4.1.2 Name, Role, ValueAControls expose their name and stateCustom toggles built from plain divs

One helpful detail: the W3C states that content which conforms to WCAG 2.2 also conforms to WCAG 2.0 and 2.1. So aiming for WCAG 2.2 WordPress conformance covers the older versions many laws and contracts still name. Keep in mind that conformance applies to full pages and complete processes, such as an entire checkout. A homepage that passes while the contact form fails does not make the site conformant, which is why the audit below looks at journeys, not just pages.

The Legal Picture in the US and Europe

The legal side is where most of the worry comes from, and also most of the confusion. This section summarizes what official sources say. It is not legal advice, and anyone who has received a complaint or demand letter should speak to a qualified lawyer.

In the US, the ADA applies to state and local governments under Title II and to businesses open to the public under Title III. The Department of Justice’s guidance on web accessibility and the ADA says the Department has consistently taken the position that ADA requirements apply to services offered on the web. It also notes there is no regulation setting detailed web standards for businesses, so they have flexibility in how they comply, but they must still comply. That is why lawsuits and demand letters against businesses usually measure a site against WCAG anyway.

For public bodies, the rules are more specific. The DOJ’s April 2024 Title II rule sets WCAG 2.1 Level AA as the standard for state and local government web content and mobile apps. According to the DOJ’s fact sheet on the web rule, an Interim Final Rule published on April 20, 2026 extended the deadlines to April 26, 2027 for entities with a population of 50,000 or more, and April 26, 2028 for smaller entities and special district governments. Agencies building sites for cities, school districts or utilities should put those dates in their project plans.

In Europe, the European Accessibility Act sets common rules for products and services such as e-commerce, banking, e-books and passenger transport. The EU’s Your Europe guidance for businesses explains that the requirements apply to products and services placed on the market after June 28, 2025. Service businesses with fewer than 10 employees and under €2 million in turnover are exempt, and each EU country has its own national law, so details vary.

FrameworkWho It CoversTechnical BenchmarkKey Dates
ADA Title II web ruleUS state and local governmentsWCAG 2.1 AAApril 26, 2027 or 2028, by population
ADA Title IIIUS businesses open to the publicNo detailed federal web standard; WCAG commonly usedIn force now
European Accessibility ActCovered EU products and services, such as e-commerceEU accessibility requirementsSince June 28, 2025

The practical takeaway is simple. If your site sells, books or informs the public, an inaccessible site carries legal risk as well as lost customers, and WCAG 2.2 AA is the clearest benchmark to work toward.

Why an Accessibility Overlay Won’t Make Your Site Compliant

An accessibility overlay is a script, often added with one line of code or a plugin, that places a widget on your site and promises to fix problems automatically. It is tempting because it is cheap and fast. But most real barriers live in the structure of the page: missing labels, broken heading order, keyboard traps in a menu, images whose meaning only a human can describe. A script running on top cannot reliably repair all of that.

Regulators have noticed. In January 2025 the Federal Trade Commission announced an order requiring accessiBe to pay $1 million over claims that its AI widget could make any website WCAG-compliant. The FTC alleged the tool did not make all user websites compliant, and the order, finalized in April 2025, bars such claims without evidence. The DOJ guidance makes a similar point, warning that a clean automated report does not necessarily mean everything is accessible. A text-size toggle can be a nice extra, but the real fix is changing the theme, templates, forms and content.

How to Audit Your WordPress Site

A good audit combines automated tools with manual testing. Scanners are fast and catch many code issues, but they cannot judge whether alt text makes sense or whether a keyboard user can finish your checkout. Start with your most important journeys: the homepage, a main service or product page, the contact or booking form, and the checkout.

Work through these checks on each page:

  • Keyboard test: put the mouse aside and press Tab through the page. Every link, button and field should be reachable in a logical order, with no traps.
  • Visible focus: watch for a clear outline on the focused item, and check that sticky headers and cookie banners do not cover it.
  • Contrast: check text, buttons and text over images against 4.5:1, or 3:1 for large text.
  • Alt text: meaningful images need a short description; decorative ones need empty alt text.
  • Headings: one H1 and a logical H2/H3 order, not bold paragraphs posing as headings.
  • Forms: visible labels tied to each field, required fields marked in text, errors explained in words.
  • Captions: prerecorded videos with speech need captions, and autoplaying media must be easy to pause.

Three free tools cover most of the automated side, and each catches slightly different issues.

ToolWhat It Does WellWatch Out For
WAVE by WebAIMVisual map of errors, contrast and structureAlerts need human judgment
axe DevTools extensionDeveloper-friendly issue list with code locationsFree version covers automated checks only
Lighthouse in ChromeQuick score next to performance dataA high score is not conformance

You can run WAVE by pasting a URL or using its extension. Google’s documentation on how the Lighthouse accessibility score works explains it is a weighted average of pass or fail audits, so a 100 only means the automated checks passed. If you already use Lighthouse for speed, our guide to LCP, CLS and INP covers that side of the report. Log each finding with the page, WCAG criterion and severity, and that list becomes your fix plan.

Fixing Common WordPress Accessibility Issues

Most fixes fall into four areas: the theme, the page builder, plugins and forms. Working in that order makes sense, because one theme fix improves every page at once, while content fixes happen page by page.

Themes set the foundation. Common problems are CSS that removes focus outlines, low-contrast palettes, hover-only dropdowns and missing “skip to content” links. An accessible WordPress theme with the Accessibility Ready tag is a sensible starting point for a new build, though your own colors and content can still add barriers. On an existing theme, a child theme can restore focus styles, make menus open on keyboard focus, adjust colors and add landmarks such as header, nav, main and footer.

Page builders are where many sites pick up their worst issues. Elementor, Divi and similar tools make it easy to style a paragraph like a heading, stack icon boxes with no labels, or use tabs and sliders that ignore the keyboard. The fix is mostly discipline: real heading widgets in order, labels on icon-only buttons, no autoplaying carousels, and a Tab-key test on every interactive widget before it goes live.

Plugins add their own markup. Cookie banners, popups, chat widgets and booking calendars often trap focus or cover the focused element, which is now a direct WCAG 2.2 issue. Check each front-end plugin, and replace the ones that cannot be fixed. A shorter plugin list also helps security and speed, as our WordPress security checklist explains.

Forms are where leads and sales happen, so they deserve extra care. Use visible labels instead of placeholder text alone, show errors next to the field in text, and avoid visual puzzles that lock users out. Login forms should allow password managers and pasting. Finally, train editors to write useful alt text, use heading blocks in order and write descriptive link text. If a change breaks a layout, our guide to common WordPress errors can help you recover.

A Real-World Scenario: An Agency Client Gets a Demand Letter

Picture a small agency that manages 30 WordPress sites. One Monday, a client who runs a regional furniture store forwards a letter from a law firm. It claims the store’s site is not accessible to blind users, lists unlabeled product images and a checkout that cannot be finished by keyboard, and asks for a response by a deadline.

The agency tells the client to take the letter itself to a lawyer, since that is a legal matter. In parallel, it audits the key journeys: homepage, category and product pages, cart and checkout. WAVE and axe flag missing alt text, low-contrast sale badges and unlabeled filter checkboxes. The manual keyboard test finds the real blocker: the mini-cart opens on hover only, and the payment step traps focus.

The agency builds a prioritized plan. Week one fixes cart and checkout, because they stop people from buying. Week two covers product images, filters and theme contrast. Week three cleans up older content and adds an accessibility statement with a way to report problems. Every fix is logged with the date, page and WCAG criterion.

Within a month, the store has a documented audit, a record of fixes and a site that customers using screen readers and keyboards can actually shop on. Nobody can predict how a legal dispute will end, but the client is in a far stronger position than one who installed an overlay and hoped. The agency also adds an accessibility check to its launch process and monthly maintenance for all 30 sites.

Your WordPress Accessibility Checklist

Use this list as a starting point for a new build or an older site. It is not a full WCAG audit, but it covers the issues that appear most often.

  • Run WAVE, axe and Lighthouse on key pages, forms and checkout.
  • Tab through every key page and confirm focus is always visible and never covered.
  • Fix text and button contrast to at least 4.5:1, or 3:1 for large text.
  • Add meaningful alt text to informative images and empty alt text to decorative ones.
  • Use one H1 per page and a logical heading order.
  • Give every form field a visible label and text-based error messages.
  • Make touch targets at least 24 by 24 CSS pixels or space them out.
  • Caption videos and avoid autoplaying motion or audio.
  • Remove themes and plugins that block keyboard or screen-reader users.
  • Publish an accessibility statement with a way to report problems.
  • Re-test after every major update, redesign or new plugin.

The last item matters most. Accessibility slips quietly, so a short recurring check beats a big audit every few years. Fold it into your WordPress maintenance routine so it happens without anyone having to remember.

How Webueno Handles Accessibility Fixes

Webueno is a managed WordPress support company, and accessibility work fits into how we already help site owners and agencies. You open a ticket, list the pages or issues to check, and our team works through them with automated scans and manual keyboard checks. Fixes cover theme CSS and templates, menus and widgets, page builder layouts, plugin replacements, forms and content cleanup.

Work is billed with support credits at $42 per hour, with bundles up to 21% off, so you pay only for the time a fix takes. For new builds, our Design team creates mobile-first layouts in Figma and our Website Development team builds them in WordPress, which is the cheapest moment to get contrast, focus and structure right. Our maintenance plans run Daily ($60), Weekly ($20) or Monthly ($10) per site, keeping updates under control. Through the white-label agency program, agencies can offer audits and fixes under their own brand and set their own margin. We do not give legal advice or legal certification, but we can give you a documented audit and practical fixes.

Frequently Asked Questions

These are the questions we hear most often from business owners and agencies starting on accessibility.

QuestionAnswer
Is WordPress accessible by default?Core puts real effort into accessibility, but your theme, page builder, plugins and content decide whether the finished site is accessible.
Do I need WCAG 2.1 or WCAG 2.2?The DOJ Title II rule names WCAG 2.1 AA, while 2.2 is the current W3C version. Content that conforms to 2.2 also conforms to 2.1, so 2.2 AA covers both.
Does ADA compliance for WordPress apply to small businesses?Title III covers businesses open to the public, and the DOJ says it applies to services offered online. Ask a lawyer about your specific case.
Will an accessibility overlay protect me from lawsuits?No tool can promise that. The FTC’s 2025 accessiBe order shows regulators take automatic compliance claims seriously.
Does the European Accessibility Act apply to my website?It applies to covered services, such as e-commerce and banking, placed on the EU market after June 28, 2025. Service microenterprises are exempt.
How long does fixing a site take?It depends on the theme, templates and content. An audit of key pages shows whether you need a few hours of fixes or a theme rebuild.

Make Accessibility Part of How Your Site Is Run

Accessibility is not a badge you earn once. It is a quality you build into the theme, forms and content, then protect every time something changes. Done well, it opens your business to more customers, lowers legal risk and often improves usability at the same time.

If you want a clear picture of where your WordPress site stands and a practical plan to fix it, Webueno can help with audits, fixes and ongoing checks for one site or a whole agency portfolio. Create your free Webueno account and open your first accessibility ticket today.

You may also like

Illustration of a first byte of data traveling from a server to a browser with a stopwatch measuring the delay, representing Time to First Byte (TTFB) server response time in WordPress.
How to Reduce Server Response Time (TTFB) in WordPress

Ready to Move Your Website and Business Forward?

No contracts. No unnecessary complexity. Just reliable execution and real results.