Our Milestones
What an Audit Is, and What a Scan Is Not
A scan is a starting point. It is not the service, and buyers who have been sold one usually do not know the difference yet.
- An automated scan finds a portion of the issues
- A manual tester finds the rest, including keyboard and focus order
- False positives are stripped before delivery
- Every finding names the success criterion it fails
- You get an effort estimate, not just a problem list
What You Get
Every audit ships with the same six things, whatever the size of the site.
Mapped issue list
Each issue tied to the WCAG 2.2 AA success criterion it fails.
Severity score
Ranked by user impact so you can fix in a defensible order.
Affected templates
Which page types and components carry each issue, not just URLs.
Screenshots
Annotated evidence so your team can see the failure.
Code-level fix guidance
Written by the developers who would make the fix.
Effort estimate
Hours per issue band, so the remediation budget writes itself.
How It Runs
Recent Projects
Awards & Recognitions
With a focus on creating outstanding recognitions for our clients and one we are proud of.
Scope and Coverage
Naming what is out of scope builds more trust than hiding it. Here is exactly what an audit covers.
- Tested: templates, user flows, assistive tech, browsers, breakpoints
- Out of scope: third-party embeds not under your control
- Out of scope: archived content and pre-existing documents
- Document remediation is quoted separately
- Anything excluded is listed by name in the report
Susan Thomas
CEO, 10FOLD
Trusted by the World’s Leading Brands
Global brands trust us as their technology partner, thanks to our expertise in building custom web and mobile solutions that perfectly fit their unique needs.
- 5-star ratings across multiple platforms.
- 1000+ satisfied clients and growing!
- We serve small businesses to large corporations with a combined market cap over $5 trillion!
Create. Innovate. Thrive with Plego.
Let's bring your site up to standard. Ready to start?
ADA Audit vs WCAG Audit vs 508 Audit
ADA is the law
The statute names no technical standard. Courts and the DOJ point to WCAG in practice.
WCAG is the standard
The testable criteria. 2.1 AA is what the Title II rule requires; 2.2 AA is current.
508 is procurement
The federal rule for what agencies may buy. Still references WCAG 2.0 A and AA.
Why Partner with Plego
Manual and automated
Both, on every engagement. Not one sold as the other.
Assistive-tech testing
Real screen readers, not a simulation.
Credentialed testers
IAAP WAS and CPWA on the people doing code work.
Severity scoring
So you fix in an order you can defend.
Effort estimates
Hours per issue band for budgeting.
Developer-written guidance
Fix notes from people who ship code.
Mobile apps included
iOS, Android, Flutter and React Native.
Retest included
We verify the fixes against the original findings.
No overlay upsell
We do not sell a widget on the way out.
Adam Urbanczyk
Founder, Koloden
Mobile App Accessibility
- The Title II rule names mobile apps explicitly and almost no agency sells testing for them
- iOS, Android, Flutter and React Native, all already in Plego’s stack
- Tested with VoiceOver and TalkBack against WCAG 2.1 AA
- Reported in the same format as the web findings