WordPress
WCAG 2.2 Checklist for WordPress Sites (Elementor, Divi and Gutenberg)
Key takeaways
- WCAG 2.2 AA includes all of WCAG 2.1 AA plus six new A and AA criteria.
- Sticky headers and cookie banners often hide the focused element, failing Focus Not Obscured.
- Interactive targets need to be at least 24 by 24 CSS pixels or have enough spacing.
- Forms shouldn't ask for the same information twice, and logins shouldn't rely on memory puzzles.
- Automated tools catch only part of the issues; test with a keyboard and a screen reader too.
What's new in WCAG 2.2?
WCAG 2.2 became a W3C Recommendation in October 2023. It keeps everything in WCAG 2.1 (except the obsolete 4.1.1 Parsing) and adds nine success criteria. These are the six at levels A and AA, which most laws and contracts point to:
| Criterion | Level | What it means on a WordPress site |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | Sticky headers, chat bubbles and cookie bars mustn't fully hide the focused element |
| 2.5.7 Dragging Movements | AA | Sliders, carousels and sortable lists need a click or tap alternative |
| 2.5.8 Target Size (Minimum) | AA | Buttons, icons and links at least 24×24 CSS pixels, or spaced apart |
| 3.2.6 Consistent Help | A | Contact, chat or help links in the same place on every page |
| 3.3.7 Redundant Entry | A | Multi-step forms don't ask for the same details twice |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logins allow password managers and paste, with no puzzle-only CAPTCHA |
Which WCAG 2.1 basics still fail most often?
- Contrast: at least 4.5:1 for body text and 3:1 for large text and interface elements.
- Alt text: set in the Media Library or per image; empty alt for decorative images.
- Keyboard access: mega menus, accordions, tabs, popups and off-canvas menus all usable with Tab, Enter, Space and Escape.
- Visible focus: many themes remove the focus outline in CSS; put it back.
- Headings: one H1, then H2 and H3 in order, not chosen for font size.
- Form labels and errors: visible labels, not placeholder-only fields; errors explained in text.
- Captions and transcripts for video and audio.
- Language: the correct lang attribute, including on translated pages.
How do you fix these in Elementor?
Use semantic HTML tags in each widget's settings (headings, buttons and links), set the menu widget's accessibility options, and check that icon-only buttons have an accessible label. Elementor V4 atomic elements output cleaner HTML, which helps. Avoid autoplaying sliders and check popups trap focus correctly and close with Escape.
How do you fix these in Divi?
Divi 5 improved its foundation, but older Divi 4 layouts often have heading levels chosen for style, low-contrast text over images and icon buttons without labels. Review module settings for heading levels and link text, add ARIA labels where needed, and test the mobile menu with a keyboard.
How do you fix these in the block editor?
Core blocks generally produce sensible HTML. The common problems come from themes and third-party blocks: removed focus styles, low-contrast palettes in theme.json, and sliders or tabs built without keyboard support. Set an accessible color palette and focus styles at the theme level so editors can't easily break them.
How should you test a WordPress site for WCAG 2.2?
- Run an automated checker such as WAVE or axe on key templates.
- Navigate every template with only a keyboard.
- Test with a screen reader (VoiceOver or NVDA) on the homepage, a content page, a form and the menu.
- Zoom to 200% and 400% to check reflow.
- Check forms, logins and checkout flows end to end.
- Repeat after major updates, because plugins and builder updates can reintroduce issues.
How The Silver Arc can help
We audit WordPress sites against WCAG 2.2 AA, fix the theme and builder issues, and build new sites accessibly from the start. See our WordPress development service, or read ADA website compliance in 2026 for the legal background.
Send us your store URL and we'll email you the fixes that matter most. No call needed.
Frequently asked questions
Is WordPress accessible by default?
WordPress core is built with accessibility in mind, but themes, page builders and plugins decide most of what visitors experience. An accessible site depends on how it's built and maintained.
What is the target size requirement in WCAG 2.2?
Success criterion 2.5.8 requires interactive targets to be at least 24 by 24 CSS pixels, or to have enough spacing around them, with some exceptions such as inline links in text.
Are accessibility plugins enough for WCAG 2.2?
No. Plugins can help with some checks or small fixes, but they can't fix layout, keyboard behaviour, heading structure or content. Overlays in particular don't make a site compliant.
Is Elementor or Divi more accessible?
Either can produce an accessible site if pages are built carefully, and both have improved with Elementor V4 and Divi 5. The block editor is usually the leanest starting point.
How often should I test my WordPress site for accessibility?
After launch, after major plugin or builder updates and whenever templates change, with a light check each month as part of maintenance.