Websites & web apps
Review content, forms, navigation, components, and complete tasks against the applicable WCAG requirements.
Electronic content · E205SECTION 508 COMPLIANCE
Turn federal accessibility requirements into practical improvements—and a clear record of how your product performs.
EqualAccess. combines automated analysis, expert manual testing, code-level remediation, and verification. We help agencies and suppliers evaluate websites, software, and digital content, with VPAT®-based ACR reporting when included in scope.
Revised Section 508 · WCAG 2.0 Levels A & AA
Additional requirements depend on the ICT and procurement scope.
THE FEDERAL STANDARD
Section 508 addresses information and communication technology developed, procured, maintained, or used by U.S. federal agencies. For suppliers, the solicitation and contract define the accessibility requirements for the ICT being delivered.
Review content, forms, navigation, components, and complete tasks against the applicable WCAG requirements.
Electronic content · E205Define platform coverage, user journeys, and the relevant WCAG and software requirements before testing.
Software · E207 + Chapter 5Evaluate the applicable requirements for PDFs, office documents, and media. Include support documentation where relevant.
Electronic content + support documentationIdentify additional needs for tools, hardware, or specialist interfaces. Confirm testing coverage as part of scoping.
Functionality determines coverageThe scope comes first. Native-app testing, hardware, and specialist ICT coverage are agreed before the engagement. Section 255 telecommunications requirements are considered separately when relevant. Agency officials determine applicable exceptions.
Official guidance: U.S. Access Board Revised 508 Standards · Applicability and conformance. Sources reviewed October 4, 2026.
BUILT AROUND YOUR ROLE
Evaluate digital services, address barriers, and maintain evidence for your accessibility program.
Connect the accessibility requirements in your contract to testing, remediation, and a clear technical handoff.
Prepare product-specific testing and ACR documentation for federal procurement and customer reviews.
Understand conformance evidence, testing scope, reported gaps, and the questions to ask a supplier.
How federal buyers use ACRs · Section 508 laws and policies.
OUR FIVE-STEP PROCESS
Human experts lead the work. Testing tools support the assessment, while findings, fixes, and verification remain connected to the agreed scope.
01 · Assess
Review your website or product, procurement requirements, existing reports, and technology stack. Identify the versions, pages, platforms, documents, and user journeys to evaluate, then begin automated analysis.
02 · Manual Testing
Evaluate keyboard operation, structure, forms, focus, and assistive-technology behavior. Record reproducible barriers against the relevant criteria, with user impact, severity, and practical remediation priorities.
03 · Code-Level Remediation
Fix scoped barriers in code, content, configuration, or components. We can implement changes or guide your developers, agency, or product team through the corrections.
<input id="email" aria-invalid="true"
aria-describedby="email-error">
<p id="email-error">Enter a valid email.</p>Output Implemented fixes or actionable developer guidance.
04 · Retest & Verify
Retest the affected components and journeys with appropriate manual, keyboard, assistive-technology, and automated checks. Record what now works, what still fails, and the environment used.
05 · Documentation
Bring the scope, findings, remediation status, and retest evidence together. When an ACR is included, use the appropriate VPAT® edition and explain the reported conformance levels and remaining limitations.
The engagement defines the stages and deliverables included. An audit-only project does not automatically include code changes or an ACR.
YOUR TECHNICAL HANDOFF
Depending on the engagement, your project can include the following deliverables.
Findings by page, feature, or document, connected to the relevant WCAG or Section 508 criteria and their effect on users.
A practical order for addressing barriers, with recommendations based on impact and implementation needs.
A completed VPAT®-based report for the agreed product, with applicable criteria, conformance levels, and meaningful explanations.
Technical recommendations and relevant code examples to help your developers resolve the issues accurately.
A record of the changes tested, the methods used, results, and any issues that remain unresolved.
When implementation is included, corrections within the website or product—not just a list of problems to address.
UNDERSTANDING THE ACR
The VPAT® is ITI’s reporting template. The completed document is an Accessibility Conformance Report: a record of how the evaluated product supports the relevant criteria.
For federal ICT, use an edition that includes the Revised Section 508 Standards, such as the 508 edition or the International edition when additional standards are needed.
Good remarks describe the tested functionality, explain gaps, and make the scope clear. A remediation plan provides context; a planned fix does not change the product’s current result.
These simplified examples explain reporting. A complete ACR covers the applicable requirements, product scope, methods, and limitations.
Learn more about VPAT & ACRITI’s VPAT® editions and terminology · Section508.gov ACR guidance.
SECTION 508 FAQ
About federal requirements, procurement, testing, and documentation.
Section 508 directly governs federal agencies’ ICT. It does not automatically cover every private website, or every website owned by a federal contractor.
A supplier may need to meet Section 508 requirements for ICT delivered under a federal contract. Review the solicitation, contract, and product scope. Other laws or funding requirements may also apply; federal funding alone should not be treated as proof that Section 508 covers the site.
Expect to provide an Accessibility Conformance Report for ICT procurement. Federal buyers use it to evaluate accessibility against the requirements in their solicitation.
The VPAT® is a common way to create that report, but the template itself is not the only reporting format. Confirm the buyer’s requested edition, scope, and format before preparing the ACR.
An accurate ACR can disclose gaps and allow a buyer to evaluate the product. It should describe current support honestly, with remediation plans clearly separated from completed work.
That does not guarantee acceptance. The agency evaluates its requirements, available products, and any applicable exceptions or best-meets provisions. Those determinations belong to the agency, not the vendor or testing provider.
Equal Access provides digital accessibility services, not legal advice. Our work is technical: testing, remediation, verification, and documentation.
Discuss legal obligations with qualified counsel and procurement or program questions with the responsible agency officials. An ACR is not a guarantee of legal protection.
Keep the report aligned with the product version and evaluated state. Releases, bug fixes, content changes, or new functionality may require retesting and an updated ACR.
Review significant changes before reusing an older report. EqualAccess. can support continued checks through Ongoing Monitoring & Support.
Yes. When remediation is included, we can implement code-level corrections or work alongside your developers and agency. Technology coverage is confirmed during scoping.
After the changes, we retest the affected functionality and document the results. Explore Code-Level Remediation.
START WITH YOUR REQUIREMENTS
Preparing for an RFP, responding to an accessibility inquiry, or updating an existing ACR? Start with a review of your website or product and the requirements you need to address.
Get a Free Review