What is the difference between Section 508 and ADA Title II?

Section 508 applies to federal agencies and their ICT procurement. ADA Title II applies to state and local government entities. They are separate laws with some overlap in requirements. Section 508's 2018 Refresh references WCAG 2.0 AA; ADA Title II's 2024 final rule references WCAG 2.1 AA. Federal agencies must comply with both Section 508 and the ADA where applicable.

Do government social media accounts need to be accessible?

Government agencies are responsible for content they post on social media platforms. While Section 508 and ADA Title II apply to government-controlled content, social media platforms themselves are third-party systems. Best practice is to post accessible content (captions on videos, alt text for images, accessible document downloads) and not rely solely on social media for essential service information.

Are there specific requirements for government PDFs?

Yes. Both Section 508 and ADA Title II require electronic documents including PDFs to be accessible. PDFs must be tagged, have a reading order, include alt text for images, have accessible forms, and include document metadata. Legacy pre-existing documents may qualify for exceptions under the ADA Title II final rule, but new documents must be accessible.

What happens when a citizen files a Section 508 or ADA complaint?

Complaints can be filed with the agency's Section 508 coordinator or ADA coordinator, or with oversight agencies (DOJ, HHS Office for Civil Rights, others). Federal agencies may also receive complaints through the General Services Administration. The agency must respond, investigate, and remediate documented barriers. Repeated failures can result in DOJ investigation and formal legal action.

All Guides

Government Web Accessibility Guide

Federal, state, and local government agencies face some of the strictest digital accessibility requirements. Section 508, ADA Title II, and state-level laws mandate accessible websites and services for all citizens.

Overview

Government agencies at all levels are among the most legally obligated organizations when it comes to digital accessibility. The principle is fundamental: government services must be available to all citizens, including the 61 million Americans with disabilities. When government websites are inaccessible, it is not just an inconvenience — it is a denial of equal access to essential services.

At the federal level, Section 508 of the Rehabilitation Act requires all federal agencies to ensure their electronic and information technology is accessible to people with disabilities. The 2018 Section 508 Refresh aligned federal requirements with WCAG 2.0 Level AA and extended coverage to software, hardware, and documentation. Federal agencies must also ensure that technology they procure from vendors meets Section 508 standards, requiring vendors to submit VPATs.

State and local governments face their own mandate under ADA Title II. The DOJ's 2024 final rule requires state and local governments to conform their websites and mobile apps to WCAG 2.1 Level AA, with deadlines in April 2026 and 2027 depending on population size. Additionally, many states have enacted their own accessibility laws that layer additional requirements on top of federal mandates.

Applicable Regulations

Section 508 of the Rehabilitation Act (federal agencies and contractors)
ADA Title II (state and local governments, WCAG 2.1 AA required)
Section 504 of the Rehabilitation Act (entities receiving federal funding)
State-level accessibility laws (California, Colorado, Texas, New York, and others)
EN 301 549 (for US agencies with international operations)
VPAT/ACR requirements for federal procurement

Common Challenges

Legacy systems built before modern accessibility standards — retrofitting is costly
Limited accessibility expertise and budget in government IT departments
Complex procurement processes that historically did not prioritize accessibility
PDF-heavy document libraries that require retroactive tagging and restructuring
Third-party vendor portals and embedded tools that may not meet WCAG requirements
Multiple stakeholders and approval chains slow down remediation efforts
Aging content management systems with limited accessible theme options
High volume of online forms with complex logic and multi-step processes

Best Practices

Incorporate accessibility requirements into all technology procurement contracts
Request and validate VPATs from all technology vendors before purchase
Establish an agency-wide accessibility policy with a designated ADA/508 coordinator
Implement automated scanning in CI/CD pipelines to catch regressions early
Conduct annual accessibility audits with both automated and manual testing
Prioritize high-traffic pages (benefit applications, contact forms, emergency info) for immediate remediation
Train all web content creators on WCAG principles and accessible document creation
Publish an accessibility statement with contact information for reporting barriers
Build a remediation roadmap with measurable milestones and executive sponsorship

How VPATify Helps

Government agencies use VPATify to establish a baseline accessibility posture across their web properties and generate the VPAT documentation required for Section 508 procurement compliance. Automated scanning provides a continuous monitoring capability that is difficult to achieve manually at government scale.

For state and local governments facing ADA Title II compliance deadlines, VPATify provides a structured scanning workflow that maps findings to WCAG 2.1 AA criteria — the exact standard required by the DOJ rule. Exportable ACR reports help agencies demonstrate to oversight bodies and citizens that they have a documented, evidence-based approach to accessibility compliance.

Frequently Asked Questions

Want deeper accessibility insights?

Scan your entire website and generate an official VPAT document — free, in minutes.

Scan Your Site — It's Free