SECTION 508 COMPLIANCE

Federal accessibility.
Tested, fixed,
and documented.

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.

  • Automated + manual testing
  • Code-level fixes
  • Clear ACR documentation

Revised Section 508 · WCAG 2.0 Levels A & AA
Additional requirements depend on the ICT and procurement scope.

Visual demo of work carried out by human experts, supported by testing tools. Findings and results are illustrative; project scope varies.

THE FEDERAL STANDARD

Start with the requirements
that apply to your ICT.

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.

Websites & web apps

Review content, forms, navigation, components, and complete tasks against the applicable WCAG requirements.

Electronic content · E205

Software & mobile apps

Define platform coverage, user journeys, and the relevant WCAG and software requirements before testing.

Software · E207 + Chapter 5

Documents & multimedia

Evaluate the applicable requirements for PDFs, office documents, and media. Include support documentation where relevant.

Electronic content + support documentation

Authoring tools & other ICT

Identify additional needs for tools, hardware, or specialist interfaces. Confirm testing coverage as part of scoping.

Functionality determines coverage

The 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

For the teams building,
supplying, and buying ICT.

Federal agencies & departments

Evaluate digital services, address barriers, and maintain evidence for your accessibility program.

Government contractors & vendors

Connect the accessibility requirements in your contract to testing, remediation, and a clear technical handoff.

SaaS & product companies

Prepare product-specific testing and ACR documentation for federal procurement and customer reviews.

Procurement teams

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

A clear path from requirements
to documented results.

Human experts lead the work. Testing tools support the assessment, while findings, fixes, and verification remain connected to the agreed scope.

01 · Assess

Define the product. Agree the scope.

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.

Requirements
Revised Section 508 + contract needs
Coverage
Product, version, and environment
Output
Agreed evaluation scope

02 · Manual Testing

Test the experience and prioritize barriers.

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.

Methods
Manual + assistive technology + tools
Finding detail
Criterion, location, impact, evidence
Output
Findings and remediation priorities

03 · Code-Level Remediation

Address the underlying implementation.

Fix scoped barriers in code, content, configuration, or components. We can implement changes or guide your developers, agency, or product team through the corrections.

EXAMPLE · FIELD AND ERROR RELATIONSHIP<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

Repeat the task after the fix.

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.

Verification
Issue-linked retest evidence
Remaining work
Open items and limitations
Output
Verification summary

05 · Documentation

Make the technical record usable.

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.

Assessment record
Scope, methods, and findings
ACR when scoped
Ratings with remarks and explanations
Output
A clear accessibility handoff

The engagement defines the stages and deliverables included. An audit-only project does not automatically include code changes or an ACR.

YOUR TECHNICAL HANDOFF

Clear findings.
Useful documentation.

Depending on the engagement, your project can include the following deliverables.

EqualAccess.Accessibility
Conformance Report
Revised Section 508 Edition
Product & version
Identified
Evaluation methods
Documented
Criteria & remarks
Evidence-backed
Known limitations
Explicit
Illustrative report structure. The actual ACR reflects your product, evaluation scope, and findings.
  • Accessibility assessment report

    Findings by page, feature, or document, connected to the relevant WCAG or Section 508 criteria and their effect on users.

  • Prioritized remediation plan

    A practical order for addressing barriers, with recommendations based on impact and implementation needs.

  • Accessibility Conformance Report

    A completed VPAT®-based report for the agreed product, with applicable criteria, conformance levels, and meaningful explanations.

  • Implementation guidance

    Technical recommendations and relevant code examples to help your developers resolve the issues accurately.

  • Verification summary

    A record of the changes tested, the methods used, results, and any issues that remain unresolved.

  • Code-level remediation

    When implementation is included, corrections within the website or product—not just a list of problems to address.

UNDERSTANDING THE ACR

More than a checkbox.
Explain the result.

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.

EXPLORE A CONFORMANCE RATING Illustrative examples, not a product assessment

The finding is supported by testing.

State what was evaluated and why the reported result is supported.

Illustrative ACR excerpt — keyboard operation
CriteriaConformance levelRemarks and explanations
2.1.1 KeyboardWCAG 2.0 · Level ASupportsThe evaluated navigation, forms, and dialogs can be operated using a keyboard. The tested journeys and environment are identified in the report.

Some functionality does not meet the criterion.

Explain the barrier and its location so a buyer understands the limitation.

Illustrative ACR excerpt — keyboard operation
CriteriaConformance levelRemarks and explanations
2.1.1 KeyboardWCAG 2.0 · Level APartially SupportsPrimary navigation and standard forms work with a keyboard. The date picker in the booking flow requires a mouse, preventing keyboard-only completion of that task.

Most functionality does not meet the criterion.

Describe the current limitation accurately, even when remediation is planned.

Illustrative ACR excerpt — keyboard operation
CriteriaConformance levelRemarks and explanations
2.1.1 KeyboardWCAG 2.0 · Level ADoes Not SupportMost application controls in the evaluated workspace require a mouse. Keyboard users cannot complete the primary request, editing, or submission journeys.

The criterion is not relevant to this product.

Explain the product context. Not Applicable does not mean the criterion was skipped.

Illustrative ACR excerpt — prerecorded media
CriteriaConformance levelRemarks and explanations
1.2.1 Audio-only and Video-only (Prerecorded)WCAG 2.0 · Level ANot ApplicableThe example product contains no prerecorded audio-only or video-only media. This conclusion is specific to the evaluated product and its documented scope.

These simplified examples explain reporting. A complete ACR covers the applicable requirements, product scope, methods, and limitations.

Learn more about VPAT & ACR

ITI’s VPAT® editions and terminology · Section508.gov ACR guidance.

SECTION 508 FAQ

Your questions.
Clearer next steps.

About federal requirements, procurement, testing, and documentation.

Read the official ACR/VPAT FAQ.

Is Section 508 compliance mandatory for private websites?

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.

Do we need a Section 508 VPAT to sell to the federal government?

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.

What if our product isn’t fully accessible? Will the government still consider it?

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.

What about legal liability or interpretations?

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.

How often should we update our Section 508 documentation?

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.

Can you help us actually fix the issues you find?

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

Bring the product.
We’ll help map the work.

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
Opens in a new tab.