Key takeaways
- Your CMS, theme and plugins decide much of your site’s accessibility: the HTML structure, heading levels, menus, forms and focus styles all come from them.
- WordPress is the most common platform among large sites. The 2026 WebAIM Million report detected WordPress on 252,302 of the top one million home pages, and found WCAG 2 failures on 95.9% of all home pages tested.
- WordPress core follows its own accessibility coding standards targeting WCAG Level AA, but themes, page builders and plugins can undo that work.
- Choose themes and plugins with accessibility in mind, configure your page builder carefully and train editors on alt text, headings and link text.
- Test after every theme, plugin or platform update, since one change can reintroduce barriers site-wide.
Your content management system affects accessibility in ways most website owners never consider. The theme sets the HTML structure, heading hierarchy, menu behavior and color palette. Plugins add forms, sliders, popups and galleries, each with its own markup. Editors then add content that can help or hurt. This Emulent guide covers accessibility in WordPress and other popular platforms, how to assess your setup, how to fix common problems and how the work supports SEO. It is general guidance, not legal advice.
How does WordPress handle accessibility?
WordPress core is a solid base. Its accessibility team reviews core code, the block editor supports alt text and heading levels and the theme directory has an “accessibility-ready” tag for themes that pass a defined set of checks. Problems usually come from the layers added on top.
| Area | What to know |
|---|---|
| Themes | control landmarks, heading structure, skip links, focus styles, menu behavior and default colors. A visually polished theme can still fail keyboard and contrast checks. |
| Page builders | can output extra wrapper markup, skip heading levels or use styled text instead of real headings if editors are not careful. |
| Plugins | sliders, popups, galleries, tabs, accordions and form plugins vary widely in keyboard and screen reader support. |
| Content | missing alt text, bold text used as headings, “click here” links and scanned PDFs are added one post at a time. |
At Emulent, we build WordPress sites with established themes and a page builder. That setup gives fine control over markup: set heading levels deliberately in each text and heading element, define accessible colors and focus styles in the theme options and avoid sliders or animations that cannot be paused. One setting fixed at the theme level then carries across every page.
How do other CMS platforms compare?
Every platform can produce an accessible site or an inaccessible one. The difference is how much control you have and where problems tend to appear.
- Shopify: our recommendation for ecommerce. Checkout is managed by the platform, so focus on your theme, product content, alt text and third-party apps, which are the usual source of barriers.
- Drupal: has a long record of accessibility work in core and gives developers fine control, but custom themes and modules still need testing.
- Squarespace and Wix: hosted builders with built-in alt text and heading tools. Templates and custom code blocks vary, and you have less control over underlying markup.
- Headless and custom builds: full control over the front end, which means accessibility depends entirely on the development team.
Whatever the platform, the standard is the same: WCAG 2.1 Level AA, with WCAG 2.2 as the newer target.
How do you assess and fix accessibility in your CMS?
Test the templates your CMS generates, then trace each problem back to its source: theme, builder, plugin or content.
- Scan each template type, such as home, page, post, archive, product, contact and search results, with WAVE, axe DevTools or Google Lighthouse.
- Test menus, forms, sliders, tabs and popups by keyboard and with NVDA, VoiceOver or TalkBack.
- Fix the theme first: skip link, landmarks, focus styles, color palette and menu keyboard support.
- Replace inaccessible plugins with better-built alternatives, or remove features you do not need, such as auto-rotating sliders.
- Configure editor defaults: require alt text on uploads, restrict heading choices to a logical order and offer approved color pairs.
- Train editors with a short checklist covering alt text, headings, link text, captions and PDFs.
- Retest after core, theme and plugin updates, and before launching new templates.
Avoid accessibility overlay plugins. UsableNet counted more than 1,400 lawsuits in 2025 against companies that had accessibility widgets installed. Hosting does not change accessibility directly, but a fast, well-managed host such as Kinsta, our recommended WordPress host, makes it easier to run staging sites where you can test updates before they go live.
How does CMS accessibility connect to SEO and conversions?
The same clean markup that helps screen readers helps search engines. Real headings, descriptive alt text and meaningful link text give search engines and AI answer engines stronger signals about your content, which supports your SEO. Accessible forms and menus reduce friction for every visitor on the path to a lead or sale.
The audience is large: the CDC reports more than one in four US adults has some type of disability. Building accessibility into your CMS setup means every new page starts in good shape instead of needing repairs later. Results vary by site, platform and content.
How the Emulent team can help
Emulent builds accessible WordPress sites and Shopify stores for ecommerce, and audits existing sites on any major platform. We trace each issue to its source, fix the theme and components and set up editor workflows that keep new content accessible. Our website design team can also recommend plugins and apps that will not undo the work. To check your website, contact the Emulent team.