I will write your accessibility statement and eaa compliance documentation
Here to dent the Fiverr
About this Gig
Regulators, enterprise buyers and public-sector tenders all want the same thing: written proof of where your site stands on accessibility. I write that documentation accurately, in the format they expect.
WHAT YOU GET
- A published-ready accessibility statement page, supplied as HTML and plain text
- A conformance report mapping your site against WCAG 2.2 AA
- Known issues documented honestly, with target remediation dates
- An accessible feedback mechanism, which the EAA requires
- VPAT 2.5 documentation on the Premium package, for procurement and tenders
WHY THIS MATTERS
A statement that overclaims is worse than no statement at all it becomes a documented admission. Mine describe your real position, which is what actually demonstrates good faith to a regulator or a buyer's compliance team.
IMPORTANT
I'm a developer, not a lawyer. This is technical documentation of your site's accessibility status, not legal advice. Have your legal advisor review it before publishing if you have real compliance exposure.
Send me your URL and any existing audit report and I'll tell you which package you need.
Testing platform:
Website testing
Device:
PC
•
Mac
•
Linux
FAQ
Is this legal advice?
No. I'm a developer, not a lawyer. I write accurate technical documentation of your site's accessibility status in the format regulators and procurement teams expect. Have your legal advisor review it before publishing if compliance exposure is a real concern.
What is a VPAT and do I need one?
A Voluntary Product Accessibility Template documents how your product meets accessibility standards. US federal agencies, universities and large enterprises usually require one before they will buy. If you sell B2B or to the public sector, you very likely need it.
Can you write a statement without auditing my site?
I can, but I'd rather not. A statement claiming conformance you don't have is worse than none — it's a documented admission. Every package includes at least a light check first. If you have a recent audit report, send it and I'll build from real findings.
What is EN 301 549?
The European accessibility standard the EAA points to. The current version incorporates WCAG 2.1 AA; version 4.1.1, expected during 2026, moves to WCAG 2.2. The Compliance Pack maps your site against it so your documentation survives the update.
How often does the statement need updating?
Whenever your site changes materially, and at minimum annually. Most regulators expect a review date on the page. I offer quarterly refreshes as an extra if you'd rather not track it yourself.

