FAQ and Compliance

Does it work in Divi 5?

Yes. It loads a native panel on a Divi 5 site and the matching panel on a Divi 4 site, automatically.

What engine does it use?

The open-source axe accessibility engine, running locally against the page in the builder. It checks against WCAG 2.1 A and AA by default; you can switch to WCAG 2.2 or the full axe rule set in Settings.

Does it call any external service?

No third-party accessibility service. Scheduled scans fetch your own published URLs to check their HTML. There is no external accessibility API and no tracking.

Can it break my content?

The guided fixes are limited and safe (alt text, marking images decorative, and a focus-outline helper). Nothing is changed without you clicking to apply it, and scans are read-only.

Does this make my site WCAG compliant?

No, and no automated tool can. It identifies common issues, helps you fix many of them, and gives you a repeatable record. Real compliance requires manual review and assistive technology testing. The plugin is built to support that process, not replace it.

Tip

We are deliberately honest about this: automated scans catch part of what matters. Use the results as your starting point, then verify the rest with a keyboard and a screen reader.

Was this page helpful?