Browse categories
Explore
Fiverr Pro
English
$
USD
I will do a manual website accessibility audit for wcag ada and section 508
About this Gig
Most websites are unusable with a screen reader or keyboard only, and the owner never knows until a complaint, lawsuit or procurement questionnaire arrives.
I test your site against WCAG 2.1 AA, the standard behind the ADA, the European Accessibility Act and Section 508.
WHAT YOU GET
Every page in scope scanned against WCAG 2.1 AA
Manual testing with NVDA and keyboard only
Findings ranked by severity, not raw tool output
The exact element at fault and the code-level fix
Screenshots and screen recording (Standard, Premium)
Accessibility statement and call (Premium)
WHY MANUAL TESTING
Automated scanners catch barely half of real failures. They miss keyboard traps, broken focus order, unlabelled controls and empty alt text. Those are the barriers real users hit. I check them by hand.
NO OVERLAY WIDGETS
Overlays do not change your code, courts do not accept them, and the FTC fined one vendor over compliance claims.
Send your URL and I will tell you what I find.
This identifies WCAG 2.1 AA failures. It is not legal advice and does not guarantee compliance.
Testing application:
Website
Device:
PC
•
Android mobile phone
FAQ
What do you need from me to get started?
Just your website URL. If you want specific pages covered, send the list. If any pages sit behind a login, send test credentials and I will cover those too.
Will this make my website ADA compliant?
This audit identifies the WCAG 2.1 AA failures on your site and tells you exactly how to fix each one. Compliance is a legal determination, so no vendor can promise it. What I can tell you is precisely what is broken and what it takes to fix it.
Do you fix the issues or only report them?
This gig is the audit. The report is written so your developer can act on it directly, with the failing element and the fix for each issue. If you would rather I implement the fixes, message me and I will quote it.
How many pages should I choose?
Pick your highest-traffic and highest-risk pages: home, a product or service page, contact, and checkout or signup. Most issues are in shared templates, so 5 well-chosen pages usually surface the majority of problems.
How is this different from an accessibility plugin or widget?
Widgets sit on top of your site and do not change the underlying code. Courts have rejected them and the FTC fined a major overlay vendor over compliance claims. Everything I report is a real code-level finding.
