Waysill tests each post or page you edit against WCAG 2.2 AA from inside the editor. Every finding says what is wrong, who is affected and how to repair it, with short examples plus a link to W3C guidance.<\/p>\n\n
Pro is a separate plugin sold through Freemius. The free plugin never expires and never counts checks.<\/p>\n\n
Checks run inside your browser while you are logged in: Waysill loads a preview from this same installation, tests it with the bundled open-source axe-core engine (MPL-2.0), then saves results as post meta in your database. Visitors see nothing; no code or credit is added to public pages.<\/p>\n\n
Automated testing finds only part of all WCAG failures, so combine results with keyboard plus screen reader testing. Waysill does not make sites compliant and changes nothing by itself.<\/p>\n\n
The free plugin contacts no outside server: checks run in your browser against your own site, and results stay in your database.<\/p>\n\n
Freemius, which handles Pro sales, licences and updates, receives data only if an administrator clicks Allow and Continue on its opt-in screen. That screen lists what is sent: the admin's name and email address, the site URL, the WordPress, PHP and plugin versions and plugin events such as activation and deactivation. Skip sends nothing and keeps every feature working. Freemius terms: https:\/\/freemius.com\/terms\/ \u2013 Freemius privacy policy: https:\/\/freemius.com\/privacy\/<\/p>\n\n
The editor scripts in Automated checks find only part of all WCAG failures. They cannot judge whether alt text describes an image well, whether link texts make sense, whether the reading and focus order are logical, whether everything works with a keyboard alone, or whether videos have correct captions. Test your pages with a keyboard and a screen reader too. A result without issues does not mean a page is accessible.<\/p><\/dd>\n In your own database. Each check stores its result with the post as post meta ( To delete stored results only, use Delete all stored results in Settings \u2192 Waysill. To remove everything, deactivate and delete the plugin on the Plugins screen: Waysill then removes its settings, all stored results and the user choices.<\/p><\/dd>\n Users who can edit the post and have a role chosen in Settings \u2192 Waysill (administrators always can). Show in preview works only for these users; visitors never see any outline or other output from Waysill.<\/p><\/dd>\n No. When it is on, the check starts in your browser after the post has been saved. Saving and publishing never wait for it.<\/p><\/dd>\n Some security plugins forbid framing. Waysill then opens the preview in a new tab, checks it there and closes the tab. It never changes your security headers.<\/p><\/dd>\n\n<\/dl>\n\n\n First release for WordPress.<\/p>\n\nassets\/js\/<\/code> are built from the TypeScript sources in src\/<\/code> (the shared Waysill core is in src\/core\/<\/code>). They are bundled with esbuild, not minified, and use the React, components and data packages that WordPress loads; src\/package.json<\/code> lists the build tools. assets\/vendor\/axe\/axe.js<\/code> is the unmodified axe-core 4.14.0 release file with its licence.<\/p>\n\n\n\n
\n
What can automated checks not find?<\/h3><\/dt>\n
Where are the results stored?<\/h3><\/dt>\n
_waysill_result<\/code> and _waysill_counts<\/code>). Your settings are stored in the option waysill_settings<\/code>, and each user's check on save choice in user meta. Nothing is sent anywhere else.<\/p><\/dd>\nHow do I remove all data?<\/h3><\/dt>\n
Who can see the results?<\/h3><\/dt>\n
Does check on save slow down saving?<\/h3><\/dt>\n
What if my site does not allow its pages in frames?<\/h3><\/dt>\n
1.1.1<\/h4>\n\n
\n
vendor\/freemius\/<\/code>, where Freemius' integration instructions put it, so the wordpress.org upload scan accepts the plugin. No change in behaviour.<\/li>\n<\/ul>\n\n1.1.0<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n