A careful WordPress widget installation, step by step.
Install through a site-wide script setting, keep theme changes reversible, and test the pages your visitors actually use. This is a manual integration, not a WordPress.org plugin listing.
By the ComplyWCAG team · Updated 13 October 2026
Prepare a safe place for the script
Record your theme, WordPress version, cache plugins, consent setup, and any content security policy. Test on a staging copy first. Obtain the exact site-specific snippet from your ComplyWCAG dashboard for the domain you will deploy.
Use a maintained header/footer code tool or your theme's supported script setting. Avoid editing WordPress core or a parent theme file that an update can overwrite. A code-injection plugin is an installation method, not an official ComplyWCAG plugin.
Install and verify
1. Add the site-specific snippet
Paste the dashboard snippet into the site-wide footer script setting. Keep the script attributes and site ID intact. Add it once; first remove duplicate copies from your theme or tag manager.
2. Publish and clear caches
Save the script setting, clear page/CDN caches, and open a logged-out page. Confirm that the published HTML contains the snippet once.
3. Check the actual delivery
Inspect the browser network and console. Verify the loader, domain-bound configuration, launcher, and panel. A copied snippet alone does not establish a successful installation.
4. Test critical pages
Review a post, navigation menu, search, and contact form on desktop and mobile. For WooCommerce, include product, cart, and checkout; theme and third-party checkout markup need their own tests.
Troubleshooting and removal
If the launcher is missing, check the site ID, allowed hostname, duplicate snippets, consent rules, blocked network requests, and CSP. If an optimization plugin delays or rewrites scripts, test the original snippet without that rewrite on staging. Do not weaken your whole CSP to make a single integration work.
If a preference breaks a layout, reset it, capture the affected page and steps, and report the issue. To remove the integration, delete the snippet from the same site-wide setting and clear caches. Confirm that the loader no longer appears on a fresh logged-out page.
Multisite installations need an explicit per-domain plan. Do not reuse one site configuration across unrelated client domains without checking account limits and origin policy. Manual guide coverage is not an assertion that every theme, plugin, or release has been tested.
Your next step