The problem this solves
Federal procurement and ICT accessibility questions require more than a generic accessibility statement. They require consistent testing and accurate documentation.
Who needs this
Government vendors
Scope, evidence and recommendations are adapted to this context.
Software and web product teams
Scope, evidence and recommendations are adapted to this context.
Organizations preparing procurement responses
Scope, evidence and recommendations are adapted to this context.
Teams updating accessibility documentation
Scope, evidence and recommendations are adapted to this context.
What we evaluate
Web and software workflows
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
WCAG criteria referenced by the Revised 508 Standards
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Forms, documents and dynamic interactions in scope
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
ACR support when requested
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Technical examples
Map issues to applicable criteria
Findings include evidence, impact, fix guidance and verification steps.
Test representative product workflows
Findings include evidence, impact, fix guidance and verification steps.
Document known limitations
Findings include evidence, impact, fix guidance and verification steps.
Avoid legal conclusions outside technical evaluation
Findings include evidence, impact, fix guidance and verification steps.
Methodology
Test
Define scope and evaluate representative workflows.
Find
Record barriers with reproducible evidence.
Explain
Connect issues to user impact and technical criteria.
Fix
Recommend source-level remediation.
Verify
Retest fixes and update status.
Deliverables
Section 508-focused test notes
Prepared for product, design, engineering and QA conversations.
Findings mapped to applicable criteria
Prepared for product, design, engineering and QA conversations.
Remediation guidance and retest options
Prepared for product, design, engineering and QA conversations.
Procurement documentation support
Prepared for product, design, engineering and QA conversations.
Related resources
Section 508 vs. ADA Title II
Different requirements, different covered entities and different timelines.
Accessibility in procurement
How audits, VPAT templates and ACRs support technology procurement.
FAQ
Is this legal advice?
No. The service provides technical accessibility information and does not constitute legal advice.
Does Section 508 use WCAG?
The Revised 508 Standards incorporate WCAG 2.0 Level A and AA for many web requirements. Some contracts may name additional targets.
Can this support an ACR?
Yes, when ACR support is included in scope.
Audit, fix, verify.
Tell us about your website or application, the scope and your accessibility goals. We'll recommend an approach — audit only, or audit plus remediation — and send a written proposal.