Everything we are asked about making a WordPress site meet WCAG 2.2 Level AA, answered in plain words. If your question is not here, write to us and we will answer it in writing. The short version of this list lives on our WordPress accessibility and ADA compliance theme page.
Is WordPress accessible out of the box?
The WordPress admin and the default block themes are reasonably good, and the project has an accessibility coding standard. Your public site is another matter: the theme, the page builder, the plugins and the content decide whether a visitor using a screen reader can actually use it. That is what a website accessibility audit measures.
Can you fix my existing theme, or do I need a new one?
Most sites are remediated in place. We fix the theme templates, the block patterns and the plugin output your site already uses, so your design and your content stay exactly as they are. A rebuild is only worth suggesting when the theme is abandoned, or when a page builder has produced markup that cannot be repaired without touching every page.
Do you work with Elementor, Divi and other page builders?
Yes. Page builders can reach WCAG 2.2 AA, but not by accident. It takes correct widget choices, custom HTML tags where the builder offers them, corrected heading levels, added ARIA where a widget offers no setting, and a small amount of theme-level CSS and JavaScript for focus and motion. We tell you honestly when a particular widget cannot be repaired and what to use instead.
Will an accessibility plugin or overlay make my site compliant?
No. A toolbar that changes font size and colours does not turn a div into a button, label a form field, manage focus in your pop-up or write meaningful alternative text. Overlays are one reason many sites still receive demand letters after paying for “compliance”. Our own free plugins are different in kind: they replace a broken component with a correct one rather than painting over it.
Do you also make WooCommerce stores accessible?
Yes. WooCommerce is where the highest risk sits, because a blocked checkout is the easiest failure for a claimant to demonstrate and the most expensive for you. We test the whole path: product page, variation selection, cart updates, coupons, address forms, payment step and order confirmation, with a keyboard and with screen readers.
What do I receive at the end?
A written audit report with screenshots, severity, WCAG 2.2 references and the fix for every issue; the remediated theme and plugin code; a re-test after the changes; an honest accessibility statement for your footer; and a VPAT where a buyer asks for one.
How do you keep the site accessible after launch?
Sites drift. A plugin update, a new landing page or an image posted without alternative text can undo careful work in a week. We provide a short written rule set for your editors, and offer monitoring and maintenance so regressions are caught before a visitor meets them.
Who does the testing?
Testing is carried out by a DHS Trusted Tester on accessibility, working with IAAP-certified colleagues. We test by hand with JAWS, NVDA, VoiceOver and TalkBack, keyboard only, at 200% and 400% zoom, with the Colour Contrast Analyser, and use Deque axe, Lighthouse and WAVE only as a first pass. Automated tools alone catch a small share of real barriers.