SECTION 504 DIGITAL ACCESSIBILITY

Section 504
Digital Accessibility Compliance

Prepare your website, digital services, and documents for the accessibility requirements affecting recipients of HHS federal financial assistance.

EqualAccess. helps healthcare organizations and other covered teams identify barriers, fix the underlying code and content, verify the work, and document what was tested.

Tell us what digital properties you need reviewed and which deadline you are preparing for.

FROM ASSESSMENT TO VERIFICATION

The technical work behind
Section 504 readiness.

Meeting an accessibility requirement takes more than running a scanner. We help you understand the barriers, make or guide the corrections, retest the work, and maintain a clear record of what was reviewed.

  • Audits & Testing

    Automated analysis and human evaluation of real experiences.

  • Code-Level Remediation

    Corrections to website code, templates, components, and interactions.

  • PDF & Document Remediation

    More accessible documents within your digital services.

  • Verification & Documentation

    Retesting and evidence of findings, fixes, and remaining work.

  • Ongoing Monitoring & Support

    Continued review as your website and content change.

Explore Our Accessibility Services

WHAT IS IN SCOPE?

Access to a service goes beyond the main website.

For organizations subject to HHS’s rule, covered digital experiences can include web content and mobile apps provided directly or through contractual, licensing, or other arrangements. That makes it important to look beyond the homepage.

  • Public websites

    Service information, provider directories, navigation, forms, and interactive functionality.

  • Appointment and intake journeys

    Scheduling, registration, applications, and other workflows used to access a program.

  • Patient- or participant-facing platforms

    Experiences used to access your services, including relevant third-party systems.

  • Electronic documents

    PDFs and other documents used to apply for, access, or participate in programs and services.

  • Mobile experiences

    Where apps form part of the scope, we help identify the testing requirement and determine the appropriate next step.

  • Third-party technology

    Vendor, contracted, or licensed functionality that forms part of the covered experience.

DIGITAL SERVICE MAP
A patient or participant
Access your servicesOne experience. Multiple systems.
  • WebsiteOwned
  • Forms & documentsOwned
  • Appointment toolThird party
  • Patient portalThird party
  • Mobile experienceNeeds review
  • Embedded toolsNeeds review
Illustrative scope discovery. Ownership and legal applicability depend on your actual systems and arrangements.

Specific exceptions exist for some archived content, pre-existing electronic documents, and independent third-party content. For example, the pre-existing-document exception does not apply to documents currently used to apply for, gain access to, or participate in a recipient’s programs. Scope depends on the facts; your advisers determine applicability.

Official sources: 45 CFR § 84.84 — web and mobile requirements · 45 CFR § 84.85 — exceptions.

WHO WE SUPPORT

Built for teams responsible for essential services.

Technical accessibility support for organizations preparing digital experiences connected to HHS-funded health and human services.

Explore Accessibility Compliance
  • Healthcare providers

    Hospitals, clinics, health systems, and other providers reviewing websites, patient information, and digital service journeys.

  • Community health organizations

    Teams making service information, appointment tools, and important documents easier to access.

  • Health and human services programs

    Organizations reviewing applications, participant resources, portals, and other program-access experiences.

  • Education organizations receiving HHS assistance

    The HHS-funding condition matters. These HHS dates do not automatically apply to every school receiving other federal funding. Public entities may also have separate ADA Title II obligations.

SECTION 504 ACCESSIBILITY SERVICES

Find the barriers.
Fix the cause. Verify the change.

Practical work across your website, content, and critical user journeys. We agree the testing methods, remediation responsibilities, and deliverables before the project begins.

UNDERSTAND THE BARRIERS

Accessibility Audits & Testing

Start with an evidence-based picture of your digital experience. We combine automated analysis with expert manual evaluation of agreed pages, components, and user journeys.

Testing can cover keyboard operation, focus, page structure, forms, interactive components, text alternatives, and assistive-technology behavior. Findings are mapped to the relevant WCAG 2.1 criteria; broader WCAG 2.2 AA testing can be scoped while retaining that regulatory mapping.

WHAT YOU GETPrioritized findings, affected locations, reproduction detail, WCAG mapping, and recommended next steps.

Explore Accessibility Audits & Testing
ACCESSIBILITY FINDING

Appointment form

The error is visible, but its relationship to the field is not conveyed programmatically.

Barrier identifiedWCAG 1.3.1
Illustrative finding. Actual testing is scoped to your experience.
CORRECT THE IMPLEMENTATION

Code-Level Remediation

Move from a report to changes in the underlying website. We can make agreed corrections directly, work alongside your developers, or divide responsibilities with your agency.

Work may include HTML structure, forms and validation, keyboard interactions, focus management, accessible names, ARIA, navigation, menus, dialogs, and other front-end components.

WHAT YOU GETTechnical corrections tied to documented findings, with retesting included in the agreed engagement.

Explore Code-Level Remediation
FORM MARKUP · UPDATED
<input id="email"
  aria-invalid="true"
  aria-describedby="email-error">

<p id="email-error">
  Enter a valid email address.
</p>

Error relationship added

Illustrative excerpt. Labels, validation behavior, and the full interaction also need testing.
MAKE INFORMATION USABLE

PDF & Document Remediation

Documents can be part of the accessibility problem too. We assess and remediate agreed documents, addressing structure, headings, reading order, lists, tables, alternative text, and other accessibility considerations.

Prioritize documents by how they are used. HHS’s exception for certain pre-existing documents does not extend to those currently used to apply for, access, or participate in a recipient’s programs.

Explore PDF & Document Remediation

Read the HHS document exception.

PATIENT INTAKE · DOCUMENT

A structure people can follow.

  • H1Patient information
  • H2Before your appointment
  • PWhat to bring
  • LIRequired documents

Logical reading order

Illustrative document structure, not a client deliverable.
CLARIFY OWNERSHIP

Third-Party Digital Experience Review

Your accessibility plan should include the relevant experiences supplied by others. Within scope, we review booking, payment, portal, or embedded functionality and identify barriers that need vendor involvement.

HHS’s requirements can cover contractual and licensed experiences, while a separate exception addresses some independent third-party content. Your advisers determine the legal scope.

WHAT YOU GETA clearer view of issues in your codebase, vendor dependencies, and the coordination needed to address them.

Book an Accessibility Review
REMEDIATION OWNERSHIP
  • Website navigationInternal team
  • Scheduling widgetVendor
  • Portal transitionCoordinate
Illustrative responsibility map. Dependencies are documented during scoping.
CLOSE THE LOOP

Verification & Accessibility Documentation

A code change needs to be checked in the actual experience. After agreed fixes, we retest affected issues and document whether they are resolved, remain open, or require further work.

WHAT YOU GETIssue-level notes, retest status, a remediation record, and an executive summary of the technical work completed.

Discuss Your Accessibility Needs
APPOINTMENT FORM · RETEST
  • Keyboard interactionRetested
  • Error associationVerified
  • Finding recordUpdated
Illustrative result. Verification records also show unresolved issues and limitations.
WHEN FORMAL REPORTING IS NEEDED

VPAT & ACR Support

If your digital product needs formal accessibility conformance documentation for customers or procurement, we can connect its technical evaluation to a separate VPAT/ACR engagement.

A VPAT/ACR is not a universal Section 504 requirement. We scope this work when it fits your product, customers, or procurement process.

Explore VPAT & ACR Services

GSA guidance on ACRs in federal ICT procurement.

OPTIONAL DOCUMENTATION
Accessibility
Conformance Report
Product · Version · Evaluation scope
A separately scoped deliverable when formal product reporting is appropriate.
SUPPORT WHAT COMES NEXT

Ongoing Monitoring & Support

Accessibility work continues as your digital properties change. New content, templates, integrations, and releases can introduce new barriers.

We can support periodic testing, monitoring, change reviews, and remediation after the initial project, helping your team keep accessibility in its publishing and development process.

Explore Ongoing Monitoring & Support
ACCESSIBILITY CHANGE REVIEW
  • New service pagesReview content
  • Updated formsRetest journey
  • Vendor releaseCheck changes
Illustrative ongoing review plan. Frequency and coverage are agreed with your team.

WHAT YOU RECEIVE

A technical record
your team can act on.

The exact deliverables depend on your scope. A Section 504 digital accessibility engagement can include:

  • Accessibility Findings Register

    Identified barriers, affected locations, priority, reproduction detail, and technical context.

  • WCAG Mapping

    Relevant criteria, with the HHS WCAG 2.1 baseline distinguished from any additional WCAG 2.2 testing.

  • Remediation Recommendations

    Actionable guidance for corrections made by your internal developers or vendors.

  • Code-Level Fixes

    Agreed changes to applicable website code, templates, components, and interactions.

  • Document Remediation

    Accessibility corrections to the PDFs or other documents included in the engagement.

  • Verification Results

    Retest status showing resolved findings, open issues, and items needing further action.

  • Remediation & Verification Log

    A working record for your technical, compliance, and project teams to track progress.

  • Executive Summary

    Scope, key findings, completed work, remaining dependencies, and recommended next steps.

  • Optional ACR/VPAT

    A separate product-conformance documentation scope when appropriate for your needs.

Deliverables are defined in the engagement scope. EqualAccess. documents technical accessibility work; it does not issue legal certifications or guarantee legal compliance.

THE RIGHT SCOPE FOR YOUR TEAM

Start with what you need.
Build from what we find.

Readiness Assessment

For teams that need to understand the accessibility gap before committing to remediation.

  • Discovery and scope definition
  • Agreed pages and journeys tested
  • WCAG findings and priorities
  • Roadmap and executive summary
Request an Accessibility Review

Assessment + Remediation

For teams that want us to identify barriers and take on the agreed technical fixes.

  • Readiness assessment
  • Agreed code-level remediation
  • Applicable document work
  • Retesting and a verification log
Discuss Your Accessibility Needs

Section 504 Readiness Program

For organizations coordinating multiple properties, documents, teams, and vendors.

  • Multi-property assessment
  • Prioritized program roadmap
  • Remediation and vendor coordination
  • Repeated verification and support
Request an Accessibility Review

Every engagement is scoped around the properties, templates, user journeys, documents, and remediation involved. We define that technical scope before pricing the project.

HOW IT WORKS

From uncertainty to
documented technical progress.

One consistent five-step process, scoped around your systems, your responsibilities, and the work you need us to perform.

  1. 01

    Assess

    Map the websites, journeys, documents, and vendor systems in scope. Establish ownership, requirements, and detectable barriers.

  2. 02

    Manual Testing

    Experts evaluate real interactions and assistive-technology behavior, reproduce barriers, and prioritize findings.

  3. 03

    Code-Level Remediation

    Make agreed website and content corrections directly, with your developers, or alongside the responsible vendors.

  4. 04

    Retest & Verify

    Repeat the affected journeys and check the fixes against the relevant criteria and agreed testing methods.

  5. 05

    Documentation

    Record what was tested, corrected, and verified, together with remaining limitations and dependencies.

Keep progress going. After the initial project, ongoing support can add monitoring, periodic review, and remediation as your digital services change.

Send us the digital properties you are preparing. We will help scope the technical assessment. An assessment-only engagement does not automatically include remediation or every deliverable.

PREPARING FOR THE HHS DEADLINE?

Know the work ahead.
Leave time to get it right.

The time-consuming part is often working through recurring components, critical journeys, documents, and vendor dependencies—and then verifying the fixes. Start with a clear view of what needs attention.

HHS WCAG-SPECIFIC COMPLIANCE DATES

Recipients with 15 or more employees

Recipients with fewer than 15 employees

The extension concerns the specific web/mobile WCAG provisions. Other Section 504 obligations continue.
Read the HHS update.

UNDERSTAND THE LANDSCAPE

Related requirements.
Different responsibilities.

A healthcare or education organization can encounter more than one framework, depending on who operates it, where its funding comes from, and which technology is involved.

A comparison of the primary scope and technical benchmarks discussed on this page.
At a glanceSection 504
HHS rule
ADA Title IISection 508
Primarily relevant toRecipients of applicable HHS federal financial assistance.State and local public entities.Federal agencies and federal ICT procurement.
Technical benchmark discussed hereWCAG 2.1 Level A and AA for covered web content and mobile apps.WCAG 2.1 Level AA for covered web content and mobile apps.Revised 508 Standards, incorporating WCAG 2.0 A and AA for electronic content and software.
Explore the requirementYou are hereADA Title II Compliance →Section 508 Compliance →

Your organization may be subject to more than one requirement. EqualAccess. explains technical standards and testing work; your legal or compliance advisers determine which obligations apply.

Official sources: HHS Section 504 · DOJ Title II guidance · GSA Section 508 laws and standards.

WHY EQUALACCESS.

Accessibility work that goes beyond identifying problems.

  • Human-led testing

    Automated tools work alongside expert manual evaluation appropriate to the engagement.

  • Code-Level Remediation

    We can move beyond reporting to address barriers in the underlying website.

  • Clear WCAG mapping

    Findings connect to the relevant criteria so developers and project owners understand the technical requirement.

  • Verification after remediation

    Where retesting is in scope, we check corrected issues in the experience and document the result.

  • Document accessibility

    Website work can be coordinated with documents that form part of the service journey.

  • Ongoing support

    Monitoring, reviews, and remediation support can continue after the initial project.

See All Accessibility Services

SECTION 504 FAQ

Common questions.
Clear starting points.

Understand the technical work, the scope, and where your legal or compliance team comes in.

Talk to EqualAccess.

HHS’s Section 504 regulation applies to programs or activities receiving federal financial assistance from the Department of Health and Human Services, including assistance received through another recipient. Your legal or compliance team should determine applicability to your organization.

EqualAccess. focuses on the technical digital accessibility work. Read the regulation’s application provision.

Under the current HHS regulation, recipients with 15 or more employees must meet the specified web/mobile WCAG requirements beginning May 11, 2027. Recipients with fewer than 15 employees have until May 10, 2028.

HHS extended the original dates by one year in May 2026. The extension does not suspend other Section 504 obligations. Read the HHS update.

The current HHS rule incorporates WCAG 2.1 Level A and AA success criteria and conformance requirements for covered web content and mobile apps.

WCAG 2.2 adds newer criteria and removes the obsolete parsing criterion. We can scope broader WCAG 2.2 AA testing while retaining the mapping to WCAG 2.1 relevant to HHS’s rule. HHS requirement · W3C’s WCAG 2.2 explanation.

They can be. Conventional electronic documents include PDFs, word-processing documents, presentations, and spreadsheets.

Certain documents available before the applicable compliance date are excepted, but that exception does not apply to documents currently used to apply for, gain access to, or participate in the recipient’s programs or activities. Prioritize document review by its actual use. Read the exceptions.

The web/mobile provisions include covered experiences provided through contractual, licensing, or other arrangements. There is also a separate exception for some independent third-party content.

We can test the technical experience within scope and document vendor dependencies. Your legal team determines applicability to your arrangement. HHS web/mobile requirements · Exceptions.

The HHS web/mobile rule does not generally require every covered recipient to produce a VPAT or Accessibility Conformance Report.

An ACR describes product conformance and is commonly relevant to ICT procurement. We can scope VPAT/ACR work separately when your product, customers, or procurement process needs it. Explore VPAT & ACR · GSA’s ACR guidance.

No. The HHS regulation discussed here applies based on receipt of HHS federal financial assistance. ADA Title II applies to state and local public entities.

Their current web/mobile rules use closely related WCAG 2.1 requirements, and some organizations can be covered by both. Explore ADA Title II Compliance.

No. Section 508 applies to federal agencies when they develop, procure, maintain, or use information and communication technology.

The Revised Section 508 Standards have their own requirements, incorporating WCAG 2.0 Level A and AA for electronic content and software. Explore Section 508 Compliance.

An audit identifies barriers within the tested scope. By itself, it does not remediate them or determine your organization’s legal compliance.

Our technical process is Assess → Manual Testing → Code-Level Remediation → Retest & Verify → Documentation.

We can support the agreed stages while your advisers determine the legal obligations. Ongoing support can help maintain progress afterward.

No. Accessibility needs to be maintained as new content, documents, features, and integrations are introduced.

Consider ongoing testing, change reviews, and monitoring after the initial remediation project. Explore Ongoing Monitoring & Support.

HHS’s regulation includes provisions on fundamental alterations, undue financial and administrative burdens, equivalent facilitation, and limited nonconformance with minimal impact on access. Each has specific conditions that your legal or compliance advisers should evaluate.

We document technical issues, remediation work, and remaining limitations so your organization has a clearer factual record. We do not make those legal determinations.

START WITH THE DIGITAL EXPERIENCE

Know what needs to be fixed.
Make a plan to move forward.

Whether you are preparing a hospital website, patient-facing forms, community health services, or multiple digital properties, start by understanding the actual barriers and the work needed to address them.

Tell us the websites, digital services, and documents you need reviewed. We will help define the appropriate technical testing and remediation scope.

Opens in a new tab.