Some websites use JavaScript optimization plugins that can interfere with the functionality of Accessibility Checker fixes.
We specifically chunk our fix scripts up so that only the code required for each specific fix is included in the page and that code not required is not output. We have already done this optimization so that Accessibility Checker fixes are performant by default.
Script optimization plugins often move, combine, or otherwise edit the entry points of scripts, which can break the import calls used by Accessibility Checker.
This issue can be tested for by looking in the console log and seeing various notes about Uncaught (in promise) ChunkLoadError referencing the frontendFixes.bundle.
WP-Rocket
If you are using WP-Rocket for JavaScript optimization, follow these steps to exclude Accessibility Checker scripts from being minified and combined:
Access WP-Rocket Settings:
- Log in to your WordPress admin dashboard.
- Navigate to Settings > WP-Rocket.
Exclude Accessibility Checker Scripts:
- Go to the File Optimization tab.
- Scroll down to the JavaScript Files section.
- In the Excluded JavaScript Files fields for both combine and defer, add the following paths, each on their own line:
/wp-content/plugins/accessibility-checker/assets/(.).js/wp-content/plugins/accessibility-checker-pro/assets/(.).js
- Save your changes.
By excluding these scripts, you ensure that WP-Rocket does not move or alter the source of the Accessibility Checker fix scripts, allowing the fixes to function correctly on your website.
Other JavaScript Optimisation Plugins
If you are using a different JavaScript optimization plugin, the process will be similar. Look for settings related to JavaScript minify or combine, and add the same exclusion paths:
/wp-content/plugins/accessibility-checker/assets/(.*).js
/wp-content/plugins/accessibility-checker-pro/assets/(.*).jsRefer to your plugin’s documentation for specific instructions on how to exclude scripts from optimization.
