Federal agencies
Section 508 program offices, CIO and digital service teams, and acquisition shops that need independent conformance evidence for systems they own, procure, or modernize.
Section 508 Audits
Reduce procurement risk with evidence-backed Section 508 evaluation. 508 Audit assesses agreed website, application, digital-service, and document scopes for public-sector and contractor teams, using the testing methods and qualified roles defined for the engagement.
Who this service is for
Section 508 audits at 508 Audit are scoped around the buyer who actually has to defend the conformance claim — whether that's a program office, a vendor in procurement review, or a prime contractor closing out a deliverable.
Section 508 program offices, CIO and digital service teams, and acquisition shops that need independent conformance evidence for systems they own, procure, or modernize.
Cities, counties, and state agencies adopting Section 508 by reference or preparing public-facing services for ADA Title II review.
Accessibility offices, web teams, and procurement leads validating LMS, student systems, and public sites against Section 508 and WCAG.
Primes and subs delivering ICT to federal customers that need audit-grade evidence behind their VPAT/ACR and contract deliverables.
SaaS and commercial software vendors that need a defensible Section 508 audit before a VPAT/ACR is submitted into a federal, state, or higher-ed procurement.
What 508 Audit evaluates
Page templates, components, navigation, and high-traffic content paths used by constituents, vendors, and applicants.
Logged-in workflows, dashboards, and case-management tools for staff, partners, and citizen-facing services.
Commercial SaaS used by federal, state, local, or higher-ed customers — evaluated in the configurations buyers will actually receive.
Multi-step applications, eligibility flows, registration, and intake — evaluated end-to-end with keyboard and assistive technology.
Tagged PDFs, forms, reports, and notices included in the audit scope when they support the user task under review.
A sampling plan that covers the page templates, component patterns, and user journeys most likely to drive procurement and user-impact risk.
What is included
Send the in-scope systems list. We will propose the audit scope, assigned roles, testing methods, deliverables, and schedule.
Testing approach
Each evaluation is mapped to the agreed Section 508 and WCAG requirements. The statement of work identifies the manual, automated, keyboard, assistive-technology, and responsive testing required for the scope.
Every finding is reproducible and traceable to a tested artifact — screen, document, or workflow.
Issues are tied to specific Section 508 and WCAG success criteria so reviewers can audit your audit.
Findings include who is affected (assistive-tech, keyboard, low-vision, cognitive) and why it matters for the user task.
Deliverables
Plain-language overview for program leadership, CORs, and Section 508 program offices — risk areas, severity distribution, and recommended next steps.
Every issue with location, evidence, severity, user impact, WCAG/508 criterion, and a remediation recommendation.
A line-of-sight from each finding back to the specific Section 508 standard and WCAG success criterion that grounds it.
Critical / Major / Minor calibrated to user impact and procurement risk — not just count or scanner score.
Concrete fix guidance: code patterns, ARIA usage, content changes, or structural updates — written for developers and content owners.
Optional retest pass with validation status, and optional VPAT/ACR preparation or refresh on the validated baseline.
Audit scope & timeline
Each Section 508 audit is scoped to the work that actually needs to be evaluated. There is no flat list of pages, and there is no inflated effort. Scope and timeline are sized to the buyer's procurement, remediation, or reporting calendar.
Pricing guidance
How engagements are scoped
Quoted from a short intake
A Conformance Audit is quoted from a short intake and scoped by templates, workflows, application complexity, document volume, and reporting requirements.
Complex applications, authenticated portals, multi-property environments, and procurement-driven accessibility reviews are typically scoped separately.
Why 508 Audit for Section 508 audits
Section 508 is what we do. Engagements are scoped around federal, state and local, higher-ed, and prime-contractor delivery — not generic web accessibility.
Findings come with fixes a developer or content owner can implement, not just a citation and a severity tag.
Deliverables are written for the people who actually have to defend them — CORs, OIG reviewers, Section 508 program offices, and prime compliance leads.
Responsibilities are fixed in the SOW, including who performs and reviews the evaluation and who signs when sign-off is contracted.
Tell us what's in scope and when it needs to be reviewed. We will propose the audit scope, assigned roles, testing methods, deliverables, and schedule.
Continue
Testing methodology
DHS Trusted Tester process mapped to Section 508 and WCAG 2.2.
VPAT / ACR services
Documentation backed by audit-grade testing for procurement review.
Remediation support
Help your team close findings — prioritization, guidance, validation.
Document accessibility
PDF, Word, and PowerPoint remediation across public-facing libraries.
Contact 508 Audit
Direct contact for federal proposals and procurement deadlines.