Integrations
Accessibility right where you work in WordPress
Block editor, Media Library, publishing, cookie banners and Multisite: EZZE WCAG Pro fits into the workflows you already know.
- No AI key of your own needed
- Cookie banner hiding for tests, also on the Free plan
- Status of every integration at a glance in the dashboard
Right in WordPress
Six places where you don’t have to relearn anything
Tests and alt texts appear where you already edit content. What you see depends on your settings and your role.
Cookie and consent banners
The banner stays for visitors – and covers no test
A consent overlay can hide large parts of a page from automated checks. With “Cookie banners during tests”, your website hides the banner only for the cloud test run. Regular page views stay unchanged.
Built-in connections
External loaders, detected by script domain
Status as checked on September 11, 2026. Not a promise for every product version or embedding method; custom banners can be connected with a developer filter.
Feature hub
Every integration with its real status
In the plugin dashboard, switch from the “Features” tab to the “Integrations” tab. There you see whether AI Alt Text is working in the Media Library and upload workflow, and the Accessibility Test in the admin bar, editors, publishing workflow and cookie banners.
-
Real settings, not claims
The overview reads your saved settings and shows Active, Partial, Inactive or Attention for each integration.
-
Scheduled batch tests with next run
From Basic, the interval and next run appear. If a scheduled run is missing despite being enabled, the overview points this out explicitly.
-
One click to the right setting
The gear icon in each group header leads straight to the feature or settings page. Nothing is maintained twice in the dashboard.
In the background
Works together with your installation
Queues, schedules, Multisite, caches and mail delivery: EZZE WCAG Pro uses what WordPress provides and needs no extra services on your server.
Honestly put
What is integrated – and what you check yourself
We only list connections that are built into the plugin and documented. Anything else is best checked on your own installation.
Built in
- Panels in the block editor, Classic Editor, Media Library and admin bar
- Automatic tests after publishing and scheduled batch tests (from Basic)
- Connections to the cookie banners listed, Action Scheduler and Multisite
What you check yourself
- Custom or differently embedded cookie banners and banners from your theme or tag manager
- Upstream caches and CDNs that ignore URL parameters
- Multilingual plugins such as WPML: not explicitly tested
Tip
The pricing overview shows which integrations your plan includes. The Free plan does not include the upload workflow or scheduled batch tests.
Good to know
Questions about integrations?
Themes and page builders, cookie banners, AI keys, Multisite, caching and requirements.
1. Which themes and page builders does the Accessibility Test work with?
The Accessibility Test checks the page as it reaches the browser – by its URL. The editor panels exist for the block editor and the Classic Editor. In page builders, you add breadcrumbs with a shortcode.
2. Which cookie banners are hidden during the test?
Built-in connections cover Borlabs Cookie 2.x and 3.x, Complianz, Cookiebot, Real Cookie Banner, iubenda and CookieYes. External loaders from OneTrust, Osano, Termly, Quantcast Choice, Didomi, TrustArc, Usercentrics, CookieScript and CookieFirst are removed based on known script domains. Status as checked on September 11, 2026; this is not a promise for every product version. Hiding is also available on the Free plan.
3. Do regular visitors still see the cookie banner?
Yes. The plugin adds a secret key to the URL only for the cloud test run. Regular page views stay unchanged, and the plugin never accepts a cookie banner. With hiding enabled, the banner itself is not tested.
4. Do I need my own AI key, for example from OpenAI?
No. AI Alt Text and the other AI features run through the managed EZZE cloud proxy. Which data is transferred is explained in the documentation on privacy and outbound requests.
5. Does EZZE WCAG Pro work with Multisite and caching plugins?
Yes. With Multisite, each site has its own site ID, its own data and its own limits. The plugin is compatible with caching plugins without special rules. Only if an upstream cache or CDN ignores URL parameters entirely do you need to exclude requests with the test key from caching there.
6. What do I need for installation?
WordPress 5.8 or later and PHP 7.4 or later. You’ll find all other requirements in the documentation under Requirements and compatibility.
Get started
Ready for accessibility without new tools?
Install EZZE WCAG Pro and see right away in the “Integrations” tab what already works together on your website.
WordPress integrations for accessibility
Accessibility works best when it is part of everyday work. That is why EZZE WCAG Pro starts where content is created in WordPress: in the block editor and Classic Editor, in the Media Library, when uploading images, in the admin bar and when publishing. You see test results next to your content, start new tests with one click and create AI alt texts right at the image.
To keep automated tests meaningful, the Accessibility Test works with common cookie and consent banners and hides them only for the test run. Batch tests and scheduled checks run through Action Scheduler and WP-Cron, and Multisite networks keep their own data and limits per site.
The “Integrations” tab in the plugin dashboard shows which integrations are active on your website – with the real status from your settings.