Section 508 is a provision of the Rehabilitation Act of 1973 that requires U.S. federal agencies to make their information and communication technology (ICT) accessible to people with disabilities. That covers websites, software, mobile apps, electronic documents, kiosks, and even hardware like copiers and phones. The core idea is simple: federal employees with disabilities and members of the public with disabilities should have access to information that is comparable to the access everyone else enjoys.
If your business never touches the federal government, Section 508 does not directly regulate your website — the Americans with Disabilities Act (ADA) is the law most private-sector sites need to think about. But Section 508 still matters far beyond Washington. It is written into federal procurement, which means any company that sells software, websites, or digital services to a federal agency must show its products conform. Many states, universities, and large enterprises have also adopted Section 508 or its underlying standards as their own accessibility baseline.
The good news is that Section 508 is one of the clearest accessibility laws to comply with, because since its 2017 "Refresh" it points directly to a well-known technical standard: the Web Content Accessibility Guidelines (WCAG) 2.0 at Level AA. If you understand WCAG, you understand most of what Section 508 asks for.
Who it binds
Federal agencies must develop, procure, maintain, and use accessible ICT. Vendors and contractors are pulled in through procurement — agencies can only buy products that conform.
The technical standard
The 2017 Section 508 Refresh incorporates WCAG 2.0 Level AA for web content, and applies those same success criteria to non-web software and electronic documents.
Proof of conformance
Vendors typically document conformance in an Accessibility Conformance Report (ACR) based on the VPAT template — a standard artifact requested in federal purchasing.
Beyond the letter of the law
Section 508 aligns closely with the EU's EN 301 549 standard and with ADA expectations, so meeting it strengthens your accessibility posture across markets.
What Section 508 is and why it exists
The Rehabilitation Act of 1973 was one of the first U.S. laws to address disability rights, prohibiting discrimination in federal programs and employment. Section 508 was added later and substantially strengthened by amendments in 1998, which gave it enforceable standards and a complaint process. Its purpose is to ensure that when the federal government builds or buys technology, that technology works for people with disabilities — whether they are agency employees doing their jobs or members of the public using government services.
In practice, Section 508 turned accessibility from a nice-to-have into a purchasing requirement for the world's largest technology buyer. That leverage is why the standard has shaped commercial software far beyond government: products that want federal customers must be accessible, and those improvements benefit every user.
Who has to comply
Section 508 directly applies to federal departments and agencies, including the U.S. Postal Service. It covers ICT that agencies develop, procure, maintain, or use — public-facing websites, internal tools, documents, multimedia, and hardware alike.
It reaches the private sector indirectly but powerfully. If you sell to a federal agency — software, a SaaS platform, web development services, training content — your product's accessibility becomes part of the deal. Agencies evaluate conformance during procurement, usually by requesting an Accessibility Conformance Report (ACR) prepared using the Voluntary Product Accessibility Template (VPAT). A weak or missing ACR can cost you the contract.
Note that recipients of federal funding — such as many universities and state programs — are covered by Section 504 of the same Act, which prohibits disability discrimination in their programs. Many of these organizations voluntarily apply the Section 508 technical standards to their websites as the practical way to meet that obligation.
The technical requirements: WCAG at the core
The original Section 508 standards had their own checklist of provisions, but the 2017 Refresh (issued by the U.S. Access Board, with enforcement beginning in January 2018) modernized everything by incorporating WCAG 2.0 Level AA by reference. For websites and web applications, conforming to WCAG 2.0 AA is conforming to Section 508's content requirements. The Refresh also applies WCAG success criteria to non-web contexts, so desktop software and electronic documents like PDFs are held to the same principles.
- Perceivable: text alternatives for images, captions for video, sufficient color contrast, content that adapts to different presentations.
- Operable: full keyboard access, no keyboard traps, enough time to complete tasks, clear navigation and page titles.
- Understandable: readable text, predictable behavior, labeled form fields, helpful error messages.
- Robust: clean markup that works reliably with assistive technologies such as screen readers.
- Plus 508-specific requirements for hardware, closed-functionality devices (like kiosks), and support documentation.
Enforcement and consequences
Section 508 gives individuals with disabilities the right to file a complaint against a federal agency whose technology is inaccessible, using the same complaint process as Section 504, and to pursue civil action under the Rehabilitation Act's remedies. Enforcement targets agencies rather than private companies — there are no direct fines against vendors under Section 508 itself.
For businesses, the consequences are commercial: lost bids, contract disputes, and remediation obligations written into agreements. An inaccurate ACR can also create legal exposure, since misrepresenting conformance to a government buyer is a serious matter. And remember that an inaccessible public website can still draw ADA claims regardless of Section 508, so accessibility gaps carry risk on more than one front.
Practical steps toward Section 508 compliance
Whether you are a federal webmaster or a vendor preparing for a government bid, the path to conformance is well established. Treat it as an ongoing program rather than a one-time project — products change with every release, and so does their accessibility.
- Audit against WCAG 2.0 AA (auditing to WCAG 2.1 or 2.2 AA gives you headroom and covers other laws too).
- Combine automated scanning with manual testing — keyboard-only navigation and screen reader checks catch issues tools miss.
- Fix foundational issues first: semantic headings, form labels, alt text, contrast, focus management.
- Make documents accessible, not just pages — PDFs and Office files are squarely in scope.
- Prepare and maintain an honest ACR/VPAT if you sell to government, updating it with each major release.
- Train content authors and developers so new content ships accessible by default.
- Tools like AccessWiser can help you find and address issues and monitor your site continuously, as part of a broader accessibility program rather than a substitute for remediation.
How Section 508 relates to WCAG, the ADA, and EN 301 549
Think of WCAG as the technical yardstick and Section 508 as one of the laws that adopts it. The ADA governs private businesses and state and local governments — and a 2024 Department of Justice rule requires state and local government websites to meet WCAG 2.1 AA, a sign that U.S. law continues converging on WCAG. In Europe, EN 301 549 plays a role similar to Section 508's standards and was deliberately harmonized with them, which is why a product built to WCAG AA travels well: one solid implementation supports Section 508 conformance, ADA risk reduction, and European requirements at the same time.
Frequently asked questions
Does Section 508 apply to my private business website?
Not directly, unless you sell technology or services to the federal government. Private-sector websites are primarily covered by the ADA. That said, agencies require Section 508 conformance from vendors, and meeting WCAG AA — the standard behind both laws — protects you on all fronts.
What is a VPAT and do I need one?
A VPAT (Voluntary Product Accessibility Template) is the standard template for documenting how a product meets accessibility criteria; the completed document is called an Accessibility Conformance Report (ACR). If you bid on federal contracts, buyers will almost certainly ask for one, and an honest, detailed ACR is a genuine competitive advantage.
Which WCAG version does Section 508 require?
The current Section 508 standards incorporate WCAG 2.0 Level AA. Many organizations target WCAG 2.1 or 2.2 AA anyway, because newer versions include everything in 2.0 plus additional criteria required by other laws and expected by many buyers.
Can an accessibility widget alone make me Section 508 compliant?
No single tool can guarantee legal compliance. Conformance depends on how your underlying pages, apps, and documents are built. Widgets and automated tools are valuable for finding issues, improving usability, and monitoring over time, but they work best alongside remediation, manual testing, and accessible development practices.
What happens if a federal agency's website is not accessible?
Individuals can file administrative complaints with the agency or pursue legal action under the Rehabilitation Act. Agencies are then expected to remediate. For vendors, the practical consequence of non-conformance is losing procurement opportunities or facing contract remediation requirements.
This article is provided for general information about accessibility regulations and standards. It is not legal advice — consult a qualified professional about your specific compliance obligations.