WordPress · Themes · Plugins
WordPress Accessibility Checker
Audit WordPress sites for accessibility gaps across themes, plugins, and content templates. Check WCAG compliance, focus order, and screen reader support.
Theme Audit
Ensure theme templates provide semantic headings, proper landmarks, and accessible navigation components.
Plugin Review
Audit forms, sliders, and popups added by plugins for keyboard support and clear labels.
Content Hygiene
Review content blocks for alt text, heading order, and contrast compliance.
How to audit a WordPress site for accessibility
Find theme, plugin, and content accessibility issues on a live WordPress site.
Audit the homepage and a representative post
These cover the theme shell and the content blocks you use most often. Submit both URLs to VertaaUX.
Audit a page where plugins inject content
Pick a page with a popup, slider, or form. Plugin-driven UI is where most accessibility regressions hide.
Fix in the customizer, theme files, or block editor
Apply each prioritized fix where the offending element lives. For plugin issues, check the plugin's settings — many have accessibility-related options (close button labels, ARIA attributes).
Re-audit
Re-run the audit on the same URLs to confirm the fix and check for new regressions introduced by the change.
Frequently asked questions
- Do WordPress themes pass accessibility audits out of the box?
- The Twenty-twenty-* default themes are accessibility-ready, but most premium and custom themes are not. Plugins compound the problem by injecting forms and popups with their own accessibility quality bar.
- What is accessibility-ready in WordPress?
- It is a tag the WordPress.org theme review team applies to themes that meet a defined accessibility checklist (skip links, keyboard support, no all-caps menus, focus indicators, and semantic markup). It is a useful starting point but does not guarantee site-wide accessibility once you add content and plugins.
- Which WordPress plugins most often break accessibility?
- Slider/carousel plugins, popup builders, and form builders are the most frequent offenders. They often render their own keyboard handlers, hide focus, or lack labels. Audit any page where they appear, not the dashboard preview.
- How do I check Gutenberg blocks for accessibility?
- Audit a representative post that uses the blocks you rely on. Verify heading hierarchy across blocks, alt text on Image blocks, contrast on Cover blocks with overlays, and that interactive blocks (buttons, navigation) are reachable by keyboard.
Related Topics
WCAG Compliance Failures
Accessibility violations that prevent users with disabilities from accessing your website, resulting in legal risk and lost revenue.
ARIA Label
An HTML attribute that provides accessible names for interactive elements like icons and buttons without visible text, essential for screen readers.
Focus Visible Indicator
A visual indicator showing which interactive element currently has keyboard focus, required for WCAG 2.4.7 compliance and keyboard navigation.
Other Accessibility Checkers
Get a full accessibility audit
Run a VertaaUX audit for deeper accessibility and UX coverage beyond the quick check.
Start Audit