WordPress Accessibility: What Your Business Site Needs

WordPress accessibility means people using a keyboard, a screen reader, zoom or high contrast can read your pages, use your menus and send your forms. WordPress itself gives you a solid starting point, but the theme, plugins and content you add on top decide whether a real visitor can actually book, buy or get in touch.

This guide is for owners and marketing managers of business sites on WordPress. By the end you will know which rules apply to you, where WordPress sites usually fail, how to check yours in an afternoon, and whether to fix your current site or replace the theme.

What WordPress accessibility covers in practice

Accessibility is measured against the Web Content Accessibility Guidelines (WCAG), published by the W3C. The current version is WCAG 2.2, and level AA is the level that laws and contracts usually point to. In plain terms, AA asks that text has enough contrast, images have text alternatives, every control works with a keyboard, focus is visible, forms have labels and errors are explained, and nothing flashes or moves without a way to stop it.

The WordPress project holds itself to that standard. Its accessibility coding standards say new and updated code in WordPress core must conform to WCAG 2.2 at level AA. That covers the admin screens and the block editor’s own output. It does not cover the theme you bought, the slider plugin, the cookie banner or the 300 images in your media library.

So the useful question is not whether WordPress is accessible. It is whether your WordPress site is. That is also how we approach it on our WordPress development projects: the platform is rarely the problem, the build on top of it usually is.

Which accessibility rules apply to your business website

The answer depends on who you are and where your customers are. This table covers the rules our clients ask about most, checked on November 8, 2026.

Your situation	Rule	What it asks of a website	Key dates
US business open to the public (shops, clinics, law firms, contractors, online stores)	ADA Title III	No detailed web regulation, but the Department of Justice says websites must be accessible; courts and settlements usually measure against WCAG AA	Applies now; enforced mainly through private lawsuits and demand letters
US state or local government body	ADA Title II web rule	WCAG 2.1 level AA	April 26, 2027 for entities serving 50,000 people or more; April 26, 2028 for smaller ones
Selling covered services, including e-commerce, to consumers in the EU	European Accessibility Act	Accessible websites and online shops, assessed in practice against the EN 301 549 standard, which builds on WCAG	Applies since June 28, 2025; service microenterprises are exempt
Serving customers in the UK	Equality Act 2010	A duty to make reasonable adjustments so disabled people are not put at a disadvantage	Applies now; public sector bodies have separate, stricter regulations

For a US private business, the practical risk is litigation rather than a government audit. Seyfarth Shaw’s annual count found 3,117 federal website accessibility lawsuits in 2025, with New York and Florida courts handling most of them. That figure leaves out state court cases and the demand letters that settle before anyone files.

The Title II deadlines were pushed back by one year in April 2026 through an interim final rule. If you run a site for a city, county, school district or public college, the standard did not change, only the date.

This is practical guidance, not legal advice. If you have received a demand letter, speak to a lawyer before you change anything on the site, and keep a record of what you fix and when.

Six problems found on most websites, and where they come from in WordPress

The same handful of errors turn up year after year. The WebAIM Million 2026 report, which scans the home pages of the top one million websites, found detectable WCAG failures on 95.9% of them, with an average of 56.1 errors per page. Six error types accounted for most of it. Here is how each one usually gets into a WordPress site.

Error (share of home pages, WebAIM 2026)	Usual WordPress cause	Typical fix
Low-contrast text (83.9%)	Theme or page-builder colors: pale gray body text, white text on photos, light buttons	Adjust the global color palette once, then check every template
Missing image alt text (53.1%)	Images uploaded without alt text, or logos and icons added as background images with no label	Add alt text in the media library and blocks; mark purely decorative images as decorative
Form inputs without labels (51%)	Form plugins set to show placeholders instead of labels, newsletter and search boxes	Turn on visible labels in the form plugin; label search and signup fields
Empty links (46.3%)	Social icons, logo links and card images with no text inside the link	Add accessible names to icon links in the theme or builder settings
Empty buttons (30.6%)	Menu toggles, slider arrows and close buttons built as icons only	Give each button a text label that screen readers announce
Missing page language (13.5%)	A theme that drops the language attribute from the page code	A small theme fix; WordPress sets it correctly when the theme lets it

Two things on top of that list cause most of the failures automated tools miss: keyboard traps (pop-ups, mega menus and sliders you cannot leave with the Tab key) and focus outlines that a theme has hidden for the sake of looks. Both need a person to test them.

Page builders deserve a mention. Elementor, Divi and similar tools can produce accessible pages, but they make it easy to stack headings out of order, use icons as buttons and add animations everywhere. If your site was built that way and is getting hard to maintain, our guide to moving from Elementor to the block editor covers when a switch is worth it.

An accessibility plugin alone will not make your site compliant

Accessibility plugins fall into two groups, and only one of them helps.

• Checkers and small fixers. Plugins that scan your pages and posts and list problems inside the editor, or fix specific issues such as adding skip links or removing title attributes. They are useful because they show your editors what to fix while they write.
• Overlays. A toolbar or widget that sits on top of the page and promises to make the whole site compliant with one line of code. These change how the page looks for some visitors, but they do not repair the underlying code, labels or structure that screen readers rely on.

The overlay promise has been tested by a regulator. In January 2025 the Federal Trade Commission alleged that accessiBe misrepresented its accessWidget tool as able to make any website WCAG compliant, and in April 2025 it approved a final order requiring accessiBe to pay $1 million and barring such claims without evidence. UsableNet’s 2025 year-end lawsuit report also recorded a growing number of suits against companies that were already using an accessibility widget.

Our view: use a checker to keep new content clean, and spend the overlay budget on fixing the theme and forms instead.

How to check your WordPress site in an afternoon

You do not need to be technical to find the biggest problems. Pick your five most important pages, usually the home page, a service or product page, the contact page, a blog post and the checkout or booking page, then work through these steps.

1. Run a free automated scan with a browser extension such as WebAIM’s WAVE or the Lighthouse accessibility check in Chrome. Note contrast, alt text, label and empty-link errors. Expect the scan to find only part of the problem.
2. Put the mouse away. Press Tab from the top of each page. You should see where you are at every step, reach every menu item and button, open and close the mobile menu, and submit the form without touching the mouse.
3. Zoom to 200%. Text should reflow without overlapping or forcing you to scroll sideways.
4. Listen to one page. Turn on VoiceOver on a Mac or iPhone, or the free NVDA screen reader on Windows, and move through the headings. Do they make sense out of context? Are the images described?
5. Submit a form with a mistake in it. The error should say what is wrong and where, in text, not only as a red border.
6. Check what you link to. PDF menus, price lists and brochures count too. If they are scanned images, they are unreadable for screen reader users.
7. Write down every problem with the page address, so a developer can price the work instead of guessing.

If that list comes back short, your editors can probably handle most of it. If the menu cannot be reached by keyboard or the forms fail, the fixes are in the theme or plugins and need a developer.

Fix your current theme, replace it, or rebuild

Most business sites do not need a new website to become accessible. The decision comes down to where the problems sit.

What your check found	Best route	Why
Mostly content issues: alt text, link wording, heading order, PDFs	Fix it yourself, with a checker plugin and a short guide for editors	The code is fine; the people adding content need a routine
Contrast, labels, icon buttons and focus outlines across the site	Targeted developer fixes to the theme, builder settings and form plugin	A handful of template changes repairs every page at once
Menus, pop-ups or sliders that trap the keyboard; a theme with no recent updates	Replace the theme, keep the content and URLs	Patching an abandoned theme costs more over time than switching
The site also looks dated, loads slowly and is hard to edit	Redesign or rebuild with accessibility checked before launch	You fix several problems with one budget instead of paying twice

If you are leaning towards the last row, our breakdown of a website refresh versus a full redesign helps you decide how far to go.

What WordPress accessibility work costs with us

We do not sell a separate accessibility certificate. Accessibility work is quoted the same way as other WordPress work, from our published prices on the pricing page.

Route	Our price	Terms that change the price
Fixes on your current site	$35 an hour	Booked in blocks of 5 hours; every change tested on a staging copy first; time report with every block
New custom block theme from your design	From $1,990	Includes speed and accessibility checks and 30 days of free support; final price depends on your design
New WordPress website	From $890 (up to 6 main pages)	Accessibility, speed, mobile, SEO and every form tested before launch; extra main pages are $90 each
Keeping it accessible after launch	$49 or $99 a month	Per website, cancel with 30 days’ notice; the $99 Business plan includes up to 1 hour of edits a month

A worked example. Say your afternoon check on a 20-page service site finds low-contrast buttons, a mobile menu you cannot open with a keyboard, a contact form with placeholder-only fields and a dozen icon links with no names. Those are theme and plugin fixes. If the developer’s fix list comes to around 10 hours, that is two five-hour blocks at $35 an hour, about $350, with every change tested on a staging copy first. Compare that with replacing the theme from $1,990 only if the menu or layout code turns out to be beyond repair.

Hosting, premium plugin licences and any third-party audit you choose are paid by you directly. For the full picture of what a WordPress site costs to build and run, see our WordPress website cost breakdown.

From our projects: Accessibility is one of the checks in the testing step of every WordPress build we deliver, alongside speed, mobile layouts, SEO and forms. On the family dental practice website we redesigned in WordPress for a practice in Virginia, the brief was a calm site that makes booking easy, with an appointment request on every page, and we tested every layout on desktop, tablet and phone before launch. Booking forms are where accessibility and revenue meet: a patient who cannot complete the form simply calls someone else.

Keeping a WordPress site accessible after launch

A site that passes on launch day can fail three months later. New blog posts go up without alt text, someone pastes a heading in bold instead of using a heading block, a plugin update changes the form markup. Accessibility needs a routine, not a one-off project.

• Give editors a one-page checklist: alt text on every meaningful image, one H1, headings in order, link text that says where it goes, no text inside images.
• Keep a checker plugin running so problems show up in the editor before a post is published.
• Test updates before they go live. Theme and plugin updates can change menus and forms; a staging copy catches that.
• Re-run the afternoon check every quarter, and after any redesign or new plugin.
• Publish an accessibility statement that says what you have done, what you know is still imperfect and how visitors can report a barrier. Ours is at attors.com/accessibility, and it is deliberately honest that it is not a certification.

The update routine is the same work a care plan covers. Our WordPress care plans test core, theme and plugin updates before release, and our website maintenance checklist shows what a good plan should include.

Sources checked on November 8, 2026: WordPress accessibility coding standards (WCAG 2.2 level AA for core); W3C WCAG 2.2; ADA.gov guidance on web accessibility (Department of Justice, March 2022); Federal Register, Title II compliance date extension (April 20, 2026); Seyfarth Shaw ADA Title III blog (March 2026, 2025 lawsuit counts); WebAIM Million 2026; FTC final order, accessiBe (April 2025); Ireland’s CCPC guidelines for microenterprises under the European Accessibility Act.

Get your WordPress accessibility fixes priced

Attors Technologies is a web development agency that builds and maintains WordPress websites for businesses in the US, UK and Europe. Send us your site address and, if you have it, the list from your afternoon check. We will review the theme, forms and key pages, then reply with a fixed written quote for the fixes, or tell you plainly if a new theme would cost you less over time.

Request a fixed quote for WordPress accessibility fixes