Section 508 and Section 504 are both part of the Rehabilitation Act of 1973, and people mix them up constantly — but they do different jobs. Section 504 is a broad anti-discrimination rule for anyone who takes federal funds; Section 508 is a narrower rule about the accessibility of technology federal agencies build, buy, or use. For PDFs, both can land on your desk, just from different directions.
This guide explains how each rule works, where the 2024 HHS Section 504 rule fits, and how both ultimately reach your documents.
Same law, two different sections
Think of the Rehabilitation Act as the foundation, with two sections that point at different audiences:
- Section 504 is a civil-rights provision. It says no qualified person with a disability can be excluded from, or denied the benefits of, any program or activity that receives federal financial assistance. It's about equal access to programs and services.
- Section 508 is a procurement-and-technology provision. It requires federal agencies to make their information and communication technology (ICT) accessible — what they develop, procure, maintain, and use. It's about technology and content.
The simplest way to keep them straight: Section 504 asks "are people with disabilities being shut out of your program?" Section 508 asks "is the technology accessible?"
Section 504: broad program access for funding recipients
Section 504 reaches a huge population — hospitals, universities, K-12 schools, state and local agencies, nonprofits, and any other entity that accepts federal money. The obligation is general nondiscrimination and equal program access, not a single technical spec.
Historically, "program access" was applied to physical spaces and services. But programs increasingly run on websites, portals, and PDFs — benefit forms, enrollment packets, notices, statements. If a critical document is an untagged, screen-reader-hostile PDF, a recipient can be denying program access just as surely as with a flight of stairs and no ramp.
The 2024 HHS Section 504 rule made the digital part explicit
For years, Section 504's application to digital content was inferred rather than spelled out. That changed for health and human services recipients.
The HHS final rule under Section 504, published May 9, 2024 (effective July 8, 2024), explicitly requires the web and mobile content of HHS-funded recipients to meet WCAG 2.1 Level AA. After a May 2026 extension, the compliance deadlines are:
| Recipient size | Compliance deadline |
|---|---|
| 15 or more employees | May 11, 2027 |
| Fewer than 15 employees | May 10, 2028 |
This is a big deal for the healthcare sector specifically — clinics, hospitals, insurers handling federal programs, and the documents they push to patients. We go deeper on that in healthcare PDFs and HHS Section 504. The key shift is that a vague nondiscrimination duty now has a concrete technical benchmark (WCAG 2.1 AA) and a deadline attached.
Section 508: accessible technology inside the federal government
Section 508 is narrower in who it binds — primarily federal agencies — but very specific in what it requires. Agencies must ensure the ICT they develop, procure, maintain, or use is accessible to people with disabilities, including their own employees and members of the public.
The technical standard is the Revised Section 508 Standards (the "508 Refresh," finalized 2017 and effective January 2018), which incorporate WCAG 2.0 Level A and AA by reference. That covers websites, software, and — squarely — electronic documents like PDFs an agency publishes or distributes.
508 also reaches the private sector through procurement. When an agency buys software, services, or documents, vendors are expected to deliver accessible products and to back up their claims with an Accessibility Conformance Report. For the full picture, see our Section 508 PDF compliance guide, the pillar for this topic.
Side-by-side comparison
| Section 504 | Section 508 | |
|---|---|---|
| What it is | Broad nondiscrimination / equal program access | Accessibility of ICT in the federal government |
| Who's covered | Anyone receiving federal financial assistance | Federal agencies (and, via procurement, their vendors) |
| Technical standard | General duty; HHS rule sets WCAG 2.1 AA for covered web/mobile content | Revised 508 Standards → WCAG 2.0 A and AA |
| How it reaches PDFs | PDFs are part of the "program" people must be able to access | PDFs are ICT the agency develops/procures/uses |
| Enforcement | Funding agency oversight, complaints, and civil-rights enforcement; loss of federal funds | Agency compliance obligations, complaints, and procurement review |
How each rule actually reaches your PDFs
Both roads end at the same place — an accessible PDF — but they get there differently:
- Under Section 504, the question is functional: can a person with a disability actually use your program? An inaccessible enrollment form or benefits notice is a program-access problem regardless of file format.
- Under Section 508, the question is technical and procurement-driven: does this document (and the technology that made it) conform to the Revised Standards? Agencies must publish accessible PDFs, and they push that requirement onto vendors through contracts.
If you're a funding recipient, you may face Section 504. If you sell to the government, you face Section 508. Many organizations — a university hospital, say — face both at once.
What about the ADA?
It's worth noting these aren't the only federal accessibility rules touching PDFs. The ADA Title II web rule (published April 24, 2024) requires state and local governments to meet WCAG 2.1 AA for web content and conventional electronic documents, with deadlines in 2027 and 2028 depending on population size. We cover that separately in the ADA Title II web rule and its PDF deadlines. A given organization can be subject to the ADA, Section 504, and Section 508 simultaneously — which is one more reason to standardize on accessible documents rather than chase each rule individually.
The practical upshot: one accessible-PDF goal
The good news is that the technical target is broadly the same across all of these — well-formed, tagged, WCAG-conformant PDFs with logical reading order, alt text, accessible tables, and accessible forms. You don't need a different PDF for Section 504, Section 508, and the ADA. You need one genuinely accessible PDF that satisfies all of them.
This is general information, not legal advice.
Key takeaways
- Section 504 and Section 508 are both in the Rehabilitation Act but do different jobs: 504 is broad nondiscrimination for funding recipients; 508 is technology accessibility inside the federal government.
- The 2024 HHS Section 504 rule put a concrete benchmark (WCAG 2.1 AA) and deadlines (2027/2028) on what was previously a general duty.
- Section 508 incorporates WCAG 2.0 A and AA and reaches vendors through procurement.
- Both rules reach PDFs — 504 as a program-access question, 508 as a technical/procurement one — and the ADA may apply on top.
- A single, genuinely accessible PDF satisfies all of them, so build to one standard rather than per-rule.
