WordPress plugin · Accessibility
Plainramp: accessibility statement generator and checker for WordPress
Coming soonFreeNo overlayPlainramp is a free WordPress plugin that helps you write an accessibility statement step by step, for the European Accessibility Act (EN 301 549), UK public sector bodies (PSBAR, following the GOV.UK sample) or a voluntary WCAG 2.2 statement, and checks your pages for common machine-detectable issues, including an axe-core browser check. It adds no overlay or widget to your site. It is an aid, not legal advice, and it does not make a site accessible by itself.
It will be listed at wordpress.org/plugins/plainramp/ once WordPress.org approves it. Until then that link shows "not found".
- Platform
- WordPress 6.5+, PHP 7.4+
- Status
- Built and tested; not yet submitted to WordPress.org (slug
plainramp) - Statement types
- European Accessibility Act / EN 301 549; UK public sector (PSBAR, GOV.UK sample); voluntary WCAG (W3C model)
- Standards
- WCAG 2.2 or 2.1, level A, AA or AAA
- Checks
- Server check of published pages; axe-core 4.14 browser check in the admin
- Front end
- The statement only. No overlay, no CSS or JavaScript added for visitors
- Data
- No external services; nothing sent to the plugin author
- Price
- Free. Optional Pro add-on planned
Who it is for
- EU businesses with services covered by the European Accessibility Act (applied from 28 June 2025), such as online shops.
- UK public sector bodies that must publish a statement under the Public Sector Bodies Accessibility Regulations 2018.
- Agencies and freelancers who maintain statements for client sites.
- Anyone who wants an honest, plain-language statement rather than an overlay.
What it does
- Six guided steps: website and rules, standard and status, known issues, feedback and contact, dates and testing, publish.
- Publishes an "Accessibility statement" page in one click, or use the block or
[plainramp_statement]shortcode. The page updates when you change your answers. - "Still missing" list points out gaps, such as no contact method or no review date.
- Checker results per page with WCAG success criterion, severity, selector, code snippet and a how-to-fix line; "Add findings from the latest check" turns them into draft known-issue lines.
- Dashboard widget with the last-reviewed date and issue counts.
Quick start
- Install and activate Plainramp.
- Optional: Plainramp → Checker, select your main pages, run the server check, then the browser check on the most important ones.
- Plainramp → Statement: work through the six steps. In step 3, add draft lines from the checker.
- In step 6, click Save and publish a statement page.
- Link to the statement from every page, for example in your footer.
Pricing
The free plugin is complete: all three statement types, the block and shortcode, review date, contact fields, the server check on any number of pages and the axe-core browser check. Plainramp Pro is planned but not on sale yet. Planned annual prices:
| Licence | Price per year | For |
|---|---|---|
| 1 site | $49 | Small business |
| 5 sites | $99 | Freelancers, small agencies |
| 25 sites | $199 | Agencies (white-label PDF for client sites) |
Pro will add scheduled re-checks with a summary email, statements in several languages, PDF export of the statement and an issue tracker. A 14-day money-back guarantee is planned.
How it compares
| Plugin | Active installs | Rating | What it is | How Plainramp differs |
|---|---|---|---|---|
| Plainramp (this) | Not yet released | – | Statement generator (EAA, UK PSBAR, WCAG) plus server and axe-core checks | – |
| Web Accessibility, formerly Ally (pojo-accessibility) | 500,000+ | 2.9 (163) | Overlay widget plus scanner | No overlay or front-end script; statement-first |
| UserWay Accessibility Widget | 80,000+ | 4.0 | SaaS overlay | Nothing leaves your site; no account needed |
| WP Accessibility (Joe Dolson) | 60,000+ | 4.8 (68) | Fixes common theme accessibility issues | Complementary: it fixes, Plainramp documents and checks |
| Equalize Digital Accessibility Checker | 10,000+ | 4.9 (80) | In-editor accessibility checker with reports | Plainramp is lighter and centres on the statement |
| Plugins tagged accessibility-statement | Under 50 each | – | Statement generators, mostly one framework | Three statement types; checker findings feed the statement |
UserWay figures are from our listing research; the rest are live WordPress.org figures. Longer write-up: Accessibility statement plugins for WordPress compared. Or write one without WordPress using a template such as the GOV.UK sample statement or the W3C statement generator.
Frequently asked questions
Does this make my website compliant?
No. No plugin can. Plainramp helps you write a statement with the structure and information the rules ask for, and helps you find some common issues. Whether your website is accessible depends on your website and your own testing. This is not legal advice.
Is this an accessibility overlay?
No. Plainramp adds nothing to your visitors' pages except the statement itself. It does not try to fix your site automatically, and the statement page loads no scripts.
Which statement type should I choose?
European Accessibility Act if you provide a covered service to consumers in the EU, such as an online shop. UK public sector if you are a UK public sector body. Voluntary WCAG statement for any other website. If you are unsure, ask an adviser.
Which standard does it use?
WCAG 2.2 level AA by default; you can choose WCAG 2.1 and level A or AAA. For the European Accessibility Act you can enter the EN 301 549 version you tested against.
What does the checker find?
The server check finds images without alt attributes, links and buttons without accessible text, unlabelled form fields, empty or skipped headings, duplicate ids, a missing lang attribute and a missing title. The browser check runs axe-core (WCAG 2.0, 2.1 and 2.2 A and AA rules), which adds colour contrast and more.
What does the checker not find?
Many things: whether alt text is meaningful, keyboard traps, focus order, captions, reading order and error handling. Treat it as a starting point and test with a keyboard and a screen reader.
How often should I review the statement?
At least once a year and after major changes. Plainramp shows the last-reviewed date and reminds you when it is more than a year old.
Disclaimer. Plainramp helps you write an accessibility statement and find some common issues. It is not legal advice, and it does not guarantee that your website is accessible or meets the European Accessibility Act, EN 301 549, the UK accessibility regulations, WCAG or any other law or standard.
It will be listed at wordpress.org/plugins/plainramp/ once WordPress.org approves it. Until then that link shows "not found".
Last updated 8 November 2026. Questions or corrections: [email protected].