Title: Waysill – Accessibility Checks for Posts and Pages Author: Saffo Published: November 12, 2026 Last modified: November 12, 2026 --- Search plugins ![](https://ps.w.org/waysill/assets/banner-772x250.png?rev=3798794) ![](https://ps.w.org/waysill/assets/icon-256x256.png?rev=3798794) # Waysill – Accessibility Checks for Posts and Pages By [Saffo](https://profiles.wordpress.org/saffodev/) [Download](https://downloads.wordpress.org/plugin/waysill.1.1.1.zip) * [Details](https://wordpress.org/plugins/waysill/#description) * [Reviews](https://wordpress.org/plugins/waysill/#reviews) * [Installation](https://wordpress.org/plugins/waysill/#installation) * [Development](https://wordpress.org/plugins/waysill/#developers) [Support](https://wordpress.org/support/plugin/waysill/) ## Description 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. #### What gets checked * Colour contrast of text, buttons as your theme renders them, with a suggested colour that passes * Images, linked images without alt text * Form fields lacking labels; links, buttons with no accessible name * Skipped heading levels, empty headings, empty links * ARIA misuse within blocks, shortcodes or page builder output #### Free, without limits * Check now button in the block editor sidebar or classic editor box * Optional check on save * Highlight any issue on a preview * Contrast details, headings outline, explanations for every rule * Unlimited checks; no account, no sign-up #### Pro: paid, $79 per year for one site * Site scan of all posts, pages, custom post types plus archives, run from your dashboard * Site-wide issue list, an accessibility column for admin lists * CSV export, scan history, optional weekly digest email Pro is a separate plugin sold through Freemius. The free plugin never expires and never counts checks. #### How it works 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. #### Limits 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. #### Privacy The free plugin contacts no outside server: checks run in your browser against your own site, and results stay in your database. 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/ – Freemius privacy policy: https://freemius.com/privacy/ #### Source code and build The editor scripts in `assets/js/` are built from the TypeScript sources in `src/`( the shared Waysill core is in `src/core/`). They are bundled with esbuild, not minified, and use the React, components and data packages that WordPress loads; `src/package. json` lists the build tools. `assets/vendor/axe/axe.js` is the unmodified axe-core 4.14.0 release file with its licence. ## Screenshots [⌊The Accessibility sidebar in the block editor: issue counts by impact and issues grouped by WCAG criterion.⌉⌊The Accessibility sidebar in the block editor: issue counts by impact and issues grouped by WCAG criterion.⌉[ The Accessibility sidebar in the block editor: issue counts by impact and issues grouped by WCAG criterion. [⌊An opened issue: what is wrong, who it affects, and fix steps for editors and for developers.⌉⌊An opened issue: what is wrong, who it affects, and fix steps for editors and for developers.⌉[ An opened issue: what is wrong, who it affects, and fix steps for editors and for developers. [⌊Show in preview outlines the failing element with its issue number.⌉⌊Show in preview outlines the failing element with its issue number.⌉[ Show in preview outlines the failing element with its issue number. [⌊Settings → Waysill: WCAG level, best-practice rules, roles that see results, check on save and deleting stored results.⌉⌊Settings → Waysill: WCAG level, best-practice rules, roles that see results, check on save and deleting stored results.⌉[ Settings Waysill: WCAG level, best-practice rules, roles that see results, check on save and deleting stored results. ## Installation 1. In the dashboard, go to Plugins Add New Plugin, search for Waysill and click Install Now, then Activate. 2. Allow or skip the Freemius opt-in screen. Everything works either way. 3. Open a post or page in the editor and click the Accessibility icon in the top bar( in the classic editor, use the Accessibility box beside the post), then Check now. 4. Optional: choose the WCAG level, best-practice rules and the roles that see results in Settings Waysill. ## FAQ ### What can automated checks not find? 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. ### Where are the results stored? In your own database. Each check stores its result with the post as post meta (` _waysill_result` and `_waysill_counts`). Your settings are stored in the option ` waysill_settings`, and each user’s check on save choice in user meta. Nothing is sent anywhere else. ### How do I remove all data? To delete stored results only, use Delete all stored results in Settings 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. ### Who can see the results? Users who can edit the post and have a role chosen in Settings Waysill (administrators always can). Show in preview works only for these users; visitors never see any outline or other output from Waysill. ### Does check on save slow down saving? No. When it is on, the check starts in your browser after the post has been saved. Saving and publishing never wait for it. ### What if my site does not allow its pages in frames? 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. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Waysill – Accessibility Checks for Posts and Pages” is open source software. The following people have contributed to this plugin. Contributors * [ Saffo ](https://profiles.wordpress.org/saffodev/) [Translate “Waysill – Accessibility Checks for Posts and Pages” into your language.](https://translate.wordpress.org/projects/wp-plugins/waysill) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/waysill/), check out the [SVN repository](https://plugins.svn.wordpress.org/waysill/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/waysill/) by [RSS](https://plugins.trac.wordpress.org/log/waysill/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.1.1 * The Freemius SDK now ships in `vendor/freemius/`, where Freemius’ integration instructions put it, so the wordpress.org upload scan accepts the plugin. No change in behaviour. #### 1.1.0 * Renamed to Waysill (was Curbcut). #### 1.0.1 First release for WordPress. * WCAG 2.2 checks (axe-core 4.14.0) of the post or page you edit, from the Accessibility panel in the block editor or the Waysill box in the classic editor. * Issues counted by impact and grouped by WCAG criterion, each with what is wrong, who it affects, fix steps for editors and for developers, and the W3C guidance. * Show in preview: outline and numbered badge on the failing element, for logged- in users who can edit the post. * Optional check after each save, per user, off by default. * Settings Waysill: WCAG level, best-practice rules, roles that see results, check on save default, delete all results. * Pro: site scan with pause and resume, site-wide issue list with filters, accessibility column in post lists, CSV export, 12-month scan history and an optional weekly digest email. ## Meta * Version **1.1.1** * Last updated **3 days ago** * Active installations **Fewer than 10** * WordPress version ** 6.6 or higher ** * Tested up to **7.1.4** * PHP version ** 7.4 or higher ** * Tags * [a11y](https://wordpress.org/plugins/tags/a11y/)[accessibility](https://wordpress.org/plugins/tags/accessibility/) [Alt Text](https://wordpress.org/plugins/tags/alt-text/)[contrast](https://wordpress.org/plugins/tags/contrast/) [wcag](https://wordpress.org/plugins/tags/wcag/) * [Advanced View](https://wordpress.org/plugins/waysill/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/waysill/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/waysill/reviews/) ## Contributors * [ Saffo ](https://profiles.wordpress.org/saffodev/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/waysill/)