What Happened
The Department of Health and Human Services (HHS) has extended the compliance deadlines for web content and mobile app accessibility under Section 504 of the Rehabilitation Act by one year. Organizations with 15 or more employees now have until May 11, 2027, while those with fewer than 15 employees have until May 10, 2028. Despite the delay, the requirements remain the same: web content and mobile apps must meet WCAG 2.1 Level AA standards.
This extension follows a similar delay for ADA Title II entities. During the comment period, some argued that compliance would impose financial burdens without benefits. HHS disagreed, stating that inaccessible telehealth systems deny healthcare to people with disabilities.
Timeline
- 2018: WCAG 2.1 published by W3C
- 2024: HHS finalizes Section 504 web accessibility rule with 2026 and 2027 compliance dates
- 2025: WebAIM Million documents accessibility state of top one million websites
- 2026: WebAIM Million shows 10% increase in WAVE-detected accessibility errors from prior year
- Late 2024/Early 2025: HHS receives comments citing implementation challenges
- 2025: HHS announces one-year extension, pushing deadlines to 2027 and 2028
Which Controls Failed or Were Missing
The extension highlights systemic issues in accessibility implementation:
Procurement controls: Organizations often purchased systems like patient portals and mobile apps without ensuring WCAG 2.1 conformance. There were no requirements for Accessibility Conformance Reports or contract language for remediation, nor Web Accessibility Specialist there pre-deployment testing of workflows.
Content governance: Inaccessible PDFs and documents continued to be published. There were no controls to prevent new barriers, no review checkpoints, and no training for content authors on creating accessible documents.
Third-party oversight: Tools like embedded widgets and media players introduced barriers that weren't tested or controlled by the primary organization. There were no vendor accountability mechanisms or accessibility requirements in service agreements.
Design and development standards: Websites were redesigned without incorporating WCAG 2.1 requirements. Each redesign Web Accessibility Specialist a missed opportunity to build accessibility from the start.
Resource allocation: Accessibility responsibilities were often added to staff already handling other duties, with no dedicated program manager or budget for audits and training.
The comment about "financial burdens without benefits" underscores a fundamental issue: viewing accessibility as a cost rather than a civil rights obligation. When disabled users are overlooked, spending on accessibility seems unnecessary.
What the Relevant Standard Requires
Section 504 of the Rehabilitation Act prohibits discrimination based on disability by programs receiving federal financial assistance. For web content and mobile apps, this means conforming to WCAG 2.1 Level AA standards.
WCAG 2.1 Level AA includes 50 success criteria under four principles: perceivable, operable, understandable, and robust. These criteria are mandatory, not optional. For example, Success Criterion 1.4.3 requires sufficient color contrast, 2.1.1 requires keyboard access to all functionality, and 4.1.2 requires programmatically determinable names, roles, and values for user interface components. These have been available since 2018.
Organizations receiving HHS funds must ensure program accessibility. If a person with a disability can't access your telehealth platform or complete a benefit application, you're denying them service. The standard requires good-faith efforts to remove barriers and prevent new ones.
Lessons and Action Items for Your Team
Stop creating new barriers immediately. With 18 to 36 months until your deadline, focus on fixing authoring workflows and templates now. Train content authors on accessible document creation and implement pre-publication review checkpoints.
Prioritize critical services. Focus on areas like appointment scheduling, patient intake forms, and benefit applications. Barriers that block access to care or participation can't wait until the last minute.
Require accessibility documentation in procurement. Demand Accessibility Conformance Reports from vendors and include WCAG 2.1 Level AA conformance in contracts. Test critical workflows before deployment.
Assign clear responsibility and resources. Accessibility shouldn't be a low priority. Designate a program owner and allocate budget for audits, remediation, and ongoing monitoring. Build accountability into performance expectations.
Measure progress honestly. By your deadline, document what you've tested, fixed, and what's left. Track your backlog and report progress quarterly. Treat accessibility as an ongoing program.
The disability community has heard "we need more time" before. This extension is only justifiable if it's used for real progress. The deadline moved, but the civil rights obligation did not.
