Stepless Accessibility Audit
Scan your site for WCAG 2.1 AA accessibility issues, see which post caused each one, and generate your accessibility statement. No overlay widget.
Use with caution
Stepless Accessibility Audit works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.
- Tested with the latest WordPress (7.1)
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Stepless Accessibility Audit stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| a11y | #97 |
| accessibility | >100 |
| accessibility checker | #69 |
| ada | >100 |
| wcag | >100 |
About Stepless Accessibility Audit
From the official readme · v1.0.2Description
Accessibility Audit checks your pages against WCAG 2.1 level AA and tells you exactly what to fix — and, crucially, which piece of your content caused it.
It does not add a widget, a toolbar or an overlay to your site, and it does not claim that installing it makes you accessible. It reports issues in your admin so you can fix them in your content and theme.
What it actually tells you
Every finding includes:
- The WCAG success criterion it breaks (1.4.3, 2.4.4, and so on)
- How severe it is — critical, serious, moderate or minor
- The exact element on the page, with its HTML
- A link to edit the post or page that caused it
- A plain-language explanation and how to fix it
That last pair is what makes a finding actionable. Knowing “an image is missing alt text” is a start; knowing it is in this post, click here to edit it is what lets you actually fix it.
Honest about what automated testing can do
Automated tools reliably detect roughly half of WCAG issues. No scanner, including this one, can judge whether your alt text is meaningful, whether your focus order makes sense, whether captions match the audio, or whether an error message actually helps.
So this plugin will not tell you that you are compliant, because no software can. It reports what automated testing can demonstrate is wrong, clearly, so you can fix those issues and then carry out the human review that the remaining criteria require.
Your data never leaves your site
The scan runs in your own browser, against your own pages, using a copy of the rule engine served from your own server.
- No external requests. None. Not for the scan, not for telemetry, not for licence checks.
- Nothing is sent to us, because there is no “us” to send it to.
- No account, no API key, no signup.
If you are in the EU and have been nervous about accessibility tools shipping your visitors’ data to third-party servers, that is precisely why it is built this way.
Built for the EU Accessibility Act
The European Accessibility Act has applied since 28 June 2025, and e-commerce is explicitly in scope — including sellers outside the EU serving EU customers. The standard is WCAG 2.1 AA.
Accessibility Audit helps you work toward it: scan, fix, rescan, and generate the accessibility statement the legislation expects, built from your real scan results rather than a fill-in-the-blanks template.
Works with WooCommerce
When WooCommerce is active, the scan automatically includes your shop, a product page, the cart and the checkout — the templates that carry the most legal risk and that merchants test least.
Deliberately small
- Admin-only in practice: no scripts, styles or queries are added for visitors.
- No dashboard widgets, no menus added to unrelated screens, no upsell notices.
- Under 1MB. No bundled framework.
- Removes all of its own data when you uninstall it.
Credits
Accessibility testing is powered by axe-core by Deque Systems, used under the Mozilla Public License 2.0. axe-core is bundled with this plugin and served from your own server; it makes no outbound connections.
Installation
- Install and activate the plugin.
- Go to Accessibility in your admin menu.
- Click Run a scan.
There is no setup, no wizard and no account.
Nothing is locked
Every limit in the plugin is a default, not a restriction, and each one can be
changed with a filter — no licence, key or paid version involved:
stepless_accessibility_audit_recent_limit— how many recent posts/pages are scannedstepless_accessibility_audit_history_limit— how many past scans are keptstepless_accessibility_audit_findings_per_page— findings stored per pagestepless_accessibility_audit_nodes_per_finding— example elements per finding
Frequently asked questions
Will this make my site compliant?
No, and no plugin can. Automated testing catches roughly half of WCAG issues; the rest needs human judgement. This plugin finds and explains what a machine can detect, which is real, useful progress — but treating any scanner’s clean result as legal compliance would be a mistake.
Does it add a toolbar or accessibility widget to my site?
No. This plugin adds nothing to your front end. It reports issues in the WordPress admin so that you can correct them in your content, theme or templates.
Does it send my data anywhere?
No. The scan runs in your browser against your own pages, and the rule engine is served from your own site. The plugin makes no external HTTP requests of any kind.
Will it slow down my site?
No. Nothing is enqueued on your front end — no scripts, no styles, no extra queries. The plugin registers exactly one front-end filter, which hides the admin toolbar during a scan and returns immediately on every ordinary page view.
Which pages get scanned?
Your home page, your five most recently edited posts and pages, and — if WooCommerce is active — your shop, a product, the cart and the checkout.
Why does a page say it could not be scanned?
Some pages send headers that stop them being loaded in a frame, which is how the scan reads them. When that happens the plugin says so plainly rather than reporting the page as clean, because a page that was not checked is not the same as a page with no problems.
What accessibility standard does it use?
WCAG 2.1 levels A and AA, which is the standard referenced by the European Accessibility Act, EN 301 549, and Section 508.
Does it work with page builders and cache plugins?
Yes. The scan reads your pages as a browser renders them, so it sees the final output regardless of how it was built.
Changelog
Display name change only.
1.0.2
- Display name shortened to “Stepless Accessibility Audit”.
1.0.1
- Scan history now keeps 30 entries by default instead of 3, and every limit in
the plugin is filterable, so nothing is restricted. - Description rewritten to describe only this plugin.
- Translation files removed; translations come from translate.wordpress.org.
1.0.0
- First release.
- WCAG 2.1 AA scanning, run locally in your browser with no external requests.
- Every finding linked to the post or page that caused it.
- WooCommerce shop, product, cart and checkout included automatically.
- Accessibility statement generator, built from your real scan results.
- Scan history.
- English and German.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Stepless Accessibility Audit alternatives
All a11y plugins →
FAQ
Stepless Accessibility Audit: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 4, 2026
Is Stepless Accessibility Audit free?
Yes. Stepless Accessibility Audit is free to download and use from the official WordPress.org plugin directory.
Is Stepless Accessibility Audit safe to use in 2026?
Stepless Accessibility Audit works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.
How many websites use Stepless Accessibility Audit?
Stepless Accessibility Audit is active on <10 WordPress websites and has been downloaded 132 times since it launched in August 2026. It was downloaded 64 times in the last 30 days.
Does Stepless Accessibility Audit work with WordPress 7.1?
Yes. The developer has tested Stepless Accessibility Audit up to WordPress 7.1.2, the latest release. It requires WordPress 6.5 or newer.
What PHP version does Stepless Accessibility Audit need?
Stepless Accessibility Audit requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Stepless Accessibility Audit last updated?
The latest version, 1.0.2, was released on August 25, 2026 (1 month ago).
Who makes Stepless Accessibility Audit?
Stepless Accessibility Audit is developed and maintained by nicodiangelo.
What are the best alternatives to Stepless Accessibility Audit?
The most popular alternatives to Stepless Accessibility Audit are Web Accessibility (formally… (500K+ installs), WP Accessibility (60K+ installs) and AccessibleWP (20K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
