Hale Accessibility Dossier for EAA
Country-specific accessibility statement (BFSG, ACM, DGCCRF), axe-core scan of your WooCommerce checkout, fix list and dated evidence log for the EAA.
Use with caution
Hale Accessibility Dossier for… 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 & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Hale Accessibility Dossier… stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| Accessibility statement | >100 |
| bfsg | #16 |
| EAA | #32 |
| european accessibility act | #61 |
| woocommerce | >100 |
About Hale Accessibility Dossier for EAA
From the official readme · v1.0.2Description
Since 28 June 2025 online shops that sell to consumers in the EU must meet the accessibility requirements of the European Accessibility Act (EAA). Besides fixing barriers, shops have paperwork: an accessibility statement with content prescribed by national law, in written and oral form, kept for as long as the service runs, and a duty to inform the market surveillance authority about non-conformities.
Hale Accessibility Dossier for EAA keeps that file inside WordPress. “EAA” stands for the European Accessibility Act; the plugin is an independent tool and not affiliated with the European Union or any authority. It is not an overlay and does not hide problems behind a widget. It helps you find them, decide what to fix first, describe them honestly and prove what you did and when.
Made for shop owners in Germany (BFSG), Austria (BaFG), the Netherlands (ACM, toegankelijkheidsverklaring), Belgium, France (déclaration d’accessibilité; the scan checks WCAG 2.1 AA rules and is not a full RGAA audit) and Ireland.
Accessibility statement for your country
- Statement content follows the national rules: Germany (BFSG Anlage 3), Austria (BaFG Anlage 3), the Netherlands (ACM), Belgium (Boek VIII WER, Dutch or French), France (Code de la consommation, annexe à l’article D412-57), Ireland (S.I. 636/2023) and a generic EU version based on Annex V of the directive.
- Written in the language of the country: Barrierefreiheitserklärung, toegankelijkheidsverklaring, déclaration d’accessibilité or English statement. The admin interface is fully translatable, and German, Dutch and French translations are prepared for translate.wordpress.org.
- Names the correct market surveillance authority with its published contact details (MLBF, Sozialministeriumservice, ACM, FOD Economie / SPF Economie, DGCCRF, CCPC). You can override them.
- Known limitations are written for you in plain language from your open scan findings and failed manual checks, with the affected pages (checkout, cart, product page …).
- Oral format: a read-aloud button that uses the speech synthesis built into the visitor’s browser, and/or your own audio recording.
- Publishes into a normal WordPress page that you can edit with the block editor. The page stays when you remove the plugin.
- Every published version is archived with date, author and SHA-256 fingerprint.
axe-core scan of your purchase path
- Runs axe-core 4.13 in your own browser. Pages are loaded in a frame while you are logged in, so the cart, checkout and customer account are tested too. Nothing is sent to an external service.
- Detects home, shop, top category, latest product, cart, checkout, account, terms, privacy and statement pages automatically. Add your own URLs.
- Optional: puts an in-stock product into your own cart first, so the checkout is tested with content.
- Desktop (1280 px) or mobile (390 px) viewport. WCAG 2.1 A/AA rules (EN 301 549), optionally WCAG 2.2 AA and best-practice rules.
- Rule messages in German and French when your admin uses those languages.
- Flags focusable elements that show no visible change on focus, for human review.
Prioritised fix list
- Findings grouped by rule and ordered by impact and by how close the page is to the purchase. Problems in the checkout come first.
- WooCommerce and WordPress specific hints for the most common problems (contrast, missing labels, product image alt text, quantity fields, variation selectors and more).
- Each finding keeps its history: first found, fixed (automatically when a later scan no longer finds it), reopened, dismissed as false positive or exempt with a logged reason.
Notification duties and deadlines
- For the Netherlands: the ACM deadlines (critical and serious problems within 1 week, moderate and minor within 1 month unless fixed) are calculated from the date a problem was first found.
- For the other countries: shows which findings must be reported “without delay” (unverzüglich, immédiatement, immediately).
- Drafts the notification in the authority’s language from your findings and measures. You send it yourself; the plugin records when, how and the reference number.
Dated, tamper-evident evidence log
- Every scan, decision, checklist result, statement version, notification and export is logged with date, user and a SHA-256 hash that includes the previous entry. Editing or deleting entries in the database breaks the chain, and the built-in verification shows where.
- Microenterprise self-check (fewer than 10 staff and at most EUR 2 million turnover or balance sheet total) with the result recorded. Belgium does not exempt microenterprises automatically, and the check says so for Belgian shops.
- 18 manual checks for what automated tests cannot decide: keyboard-only purchase, screen reader announcements in the cart, checkout error messages, payment providers, CAPTCHA, cookie banner, zoom, emails, documents and more.
Reports
- Print or save as PDF, download as HTML, JSON or CSV.
- The report contains the summary, deadlines, fix list, manual checks, finding history, statement versions and the full evidence log, with a fingerprint of the exported data.
What Hale Accessibility Dossier for EAA does not do
- It does not make your site accessible or compliant by itself, and it is not legal advice. Automated tests find only part of all barriers; the manual checks and your fixes do the rest.
- It does not change your shop’s front end, except the read-aloud button on the statement page and an optional footer link (off by default).
- It never contacts an authority or any other service.
Privacy
Hale Accessibility Dossier for EAA makes no external HTTP requests, loads no remote scripts or fonts, sets no cookies and collects no usage data. All data stays in your WordPress database: scan results (including short HTML snippets of your own pages), the evidence log (with the user IDs of administrators who performed actions), manual check notes and statement versions. Links to rule explanations on dequeuniversity.com are only opened if you click them.
Third-party code
- axe-core 4.13.0 by Deque Systems, Mozilla Public License 2.0, bundled in
assets/vendor/axe-core/with its licence and the unminified source (axe.js). Source: https://github.com/dequelabs/axe-core
Sources used for the statement content
- EAA, Directive (EU) 2019/882, Annex V and Art. 13: https://eur-lex.europa.eu/eli/dir/2019/882/oj
- Germany, BFSG Anlage 3 and § 14: https://www.gesetze-im-internet.de/bfsg/anlage_3.html
- Austria, BaFG § 14: https://www.ris.bka.gv.at/eli/bgbl/i/2023/76/P14/NOR40254374
- Netherlands, ACM: https://www.acm.nl/nl/toegankelijkheid/toegankelijkheid-van-e-handelsdiensten-en-elektronische-communicatiediensten
- Belgium, FOD Economie guidelines: https://economie.fgov.be/sites/default/files/Files/Entreprises/Guidelines-toegankelijke-e-handelsdiensten.pdf
- France, francenum: https://www.francenum.gouv.fr/guides-et-conseils/developpement-commercial/site-e-commerce/accessibilite-des-sites-de-e-commerce
- Ireland, S.I. 636/2023: https://www.irishstatutebook.ie/eli/2023/si/636/
Installation
- Install and activate the plugin through the Plugins screen.
- Open Accessibility Dossier in the admin menu.
- Under Settings, choose your country and answer the microenterprise self-check.
- Under Scan & fix list, run the first scan and keep the tab open until it is finished.
- Work through the fix list and the Manual checks.
- Under Statement, complete the fields and click Save and publish statement page. Link the page from your footer or menu.
- Check Notification duties after every scan and export a dated report when you need to show your work.
Changelog
New name: Hale Accessibility Dossier for EAA. Your data and settings are kept.
1.0.2
- New name: Hale Accessibility Dossier for EAA (slug and text domain
hale-accessibility-dossier-for-eaa). Settings and data are unchanged. - The report stylesheet is added through the WordPress style API.
- Translations are no longer bundled; they come from translate.wordpress.org.
1.0.1
- Microenterprise self-check: Belgian law does not exempt microenterprises automatically (Art. VIII.59 § 2 Code of Economic Law), so the check no longer reports Belgian microenterprises as exempt and keeps their notification duties active.
1.0.0
- First release.
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 Hale Accessibility Dossier fo… alternatives
All Accessibility statement plugins →FAQ
Hale Accessibility Dossier for EAA: quick answers
Straight answers, pulled from live WordPress.org data.
Source: WordPress.org
Is Hale Accessibility Dossier for… free?
Yes. Hale Accessibility Dossier for… is free to download and use from the official WordPress.org plugin directory.
Is Hale Accessibility Dossier for… safe to use in 2026?
Hale Accessibility Dossier for… 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 Hale Accessibility Dossier for…?
Hale Accessibility Dossier for… is active on <10 WordPress websites and has been downloaded 185 times since it launched in October 2026. It was downloaded 100 times in the last 30 days.
Does Hale Accessibility Dossier for… work with WordPress 7.1?
Yes. The developer has tested Hale Accessibility Dossier for… up to WordPress 7.1.5, the latest release. It requires WordPress 6.4 or newer.
What PHP version does Hale Accessibility Dossier for… need?
Hale Accessibility Dossier for… requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Hale Accessibility Dossier for… last updated?
The latest version, 1.0.2, was released on October 14, 2026 (1 month ago).
Who makes Hale Accessibility Dossier for…?
Hale Accessibility Dossier for… is developed and maintained by Adam Hale.
What are the best alternatives to Hale Accessibility Dossier for…?
The most popular alternatives to Hale Accessibility Dossier for… are Web Accessibility (formally… (500K+ installs), EDigital Accessibility Tool… (40+ installs) and Vouchlog (20+ installs).
Powered by PageForge
One template and a spreadsheet. A real page for every search.
PageForge turns each row of a CSV into a WordPress page with its own title, URL, SEO fields and schema, built on the layout you already designed. Free on WordPress.org.
- CSV and XLSX, plus Google Sheets on Professional and Enterprise
- Its own title, URL, SEO fields and schema for every page
- Works with the block editor, Elementor, Divi and Avada
- Free on WordPress.org, no credit card
