WCAG 2.1 AA on an Elementor site: what actually needed fixing
The fixes that took my Elementor V4 site to Lighthouse 100 and zero axe violations: focus ring, skip link, named navs, forms, contrast and reflow.
Service · WordPress accessibility
WordPress accessibility fixes to WCAG 2.1 AA
I find what gets in the way of keyboard and screen reader users on your WordPress or Elementor site, fix it in the theme and the templates, and document what changed.
=== WordPress accessibility ===
- Standard:
- WCAG 2.1 AA
- Checks:
- axe-core, Lighthouse, keyboard, 200% and 400% zoom, 320 px reflow
- Covers:
- forms, menus, cookie notices, light and dark mode
- Fixed in:
- the code, not with an overlay
- Quote:
- fixed, per project
- Reply time:
- under 24 hours
What you get
-
An audit with a prioritized list
An automated pass with axe-core and Lighthouse, plus manual keyboard, zoom and reflow checks, written up as a list ordered by impact.
-
Fixes in the code
Contrast, focus styles, headings, landmarks and the skip link, corrected in the theme and the templates.
-
Forms, menus and dialogs
Visible labels, announced errors, navigation that works by keyboard, and dialogs that keep and return focus, including the cookie notice.
-
A record of what was tested
Notes on what was checked, what changed and what’s left, so you can show your client the work.
The proof is this site
I rebuilt rolandowp.com with Elementor in 2026 and took it to WCAG 2.1 AA. You can run the same checks on it yourself.
- 0 WCAG 2.1 AA violations reported by axe-core, in light and dark mode
- 100 Lighthouse accessibility score
- 320 px wide, and pages still reflow with no horizontal scrolling
How it works
-
Send the URL
Tell me which pages or templates matter most. I reply within 24 hours with questions or a first read.
-
Fixed quote and plan
You get a fixed price, scope and timeline before any work starts, so there are no surprises on the invoice.
-
Fix on staging
I work in Git on a staging copy, so you can review each fix before it reaches the live site.
-
Retest and document
The same checks run again after the fixes, and you get the notes on what was tested and what changed.
Common questions
- Will this make our site ADA compliant?
- I can’t give legal advice or certify compliance. What I can do is fix the site against WCAG 2.1 AA and give you a written record of what was tested and what changed.
- Do you install an accessibility overlay?
- No. An overlay doesn’t change the underlying code, so the problems stay for keyboard and screen reader users. I fix the theme, the templates and the plugin output.
- Does it work with Elementor?
- Yes. This site is built with Elementor and axe-core reports no violations on it. Some fixes go in a child theme because the editor doesn’t expose them, such as the skip-link target and form autocomplete.
- Can you keep it accessible after launch?
- I can recheck after big changes, quoted the same way. I also leave notes so editors know what to watch, like heading order and alt text.
How I’ve done this before
Write-ups from the blog, with the code and the decisions behind it.
Have a project like this?
You’ll work directly with me, Rolando Escobar: a senior WordPress developer who has worked with US teams since 2019. Tell me what you need and I’ll reply within 24 hours with questions or a fixed quote.
Tell me about your project rolando@rolandowp.com
Working with an agency? See how I work under your brand. Other services: Figma to WordPress, plugins and integrations and Elementor.
Tell me about your project
A new build, a plugin, or a site that needs care: send me a few lines about it. I reply within 24 hours.