Your WCAG 2027 Runway Plan: HHS Extended the Section 504 Web Deadline to May 11, 2027 — Use the Year Well

Two rules. Two extension tracks. One FQHC obligation.

There are two federal web-accessibility rules in play right now, and both reference the same WCAG 2.1 Level AA technical standard. They sound interchangeable. They are not.

• ADA Title II (DOJ-administered): Covers state and local governments — counties, public hospital districts, city public health departments. Original deadlines were April 24, 2026 (50K+ population) and April 24, 2027 (under 50K). DOJ extended these on April 20 to April 26, 2027 and April 26, 2028 respectively.
• HHS Section 504 (HHS-OCR-administered): Covers any entity that receives HHS funding — which is every FQHC. HHS later extended the web/mobile compliance dates to May 11, 2027 for entities with 15 or more employees and May 10, 2028 for those with fewer than 15.

The April guidance was right at the time: DOJ's extension did not itself change HHS Section 504. The current answer changed only after HHS OCR issued its own interim final rule in May. Do not mix those two events together in board materials.

If your FQHC takes any HHS dollars — Section 330 grant, Medicaid PPS, Medicare, BHCIP, ARP, NHSC — you are governed by HHS Section 504, not DOJ Title II. The web/mobile date moved, but the responsible regulator and the technical standard did not.

Why the confusion risk is still dangerous

The risk has changed shape. In April, the danger was thinking the DOJ extension applied to FQHCs. After HHS's May interim final rule, the danger is treating the extra year as permission to defer. OCR did not repeal the accessibility obligation; it gave covered entities more implementation time.

There is also a separate signal worth flagging. On April 22, Converge Accessibility published what it called a 'Red Alert' suggesting the HHS Section 504 rule itself may be subject to administration review. Nothing has been formally proposed. No rulemaking notice. Legal advisors uniformly recommend assuming the rule holds.

Translation: do not plan around rumors, and do not plan around stale April guidance. Plan around the current HHS interim final rule, the July 6 comment close, and the operating reality that inaccessible digital front doors still create patient-access risk today.

What Section 504 Actually Requires

The revised May 11, 2027 deadline applies to web content and mobile applications used to deliver programs, activities, and services for entities with 15+ employees. For FQHCs, that scope is broad. The compliance bar is still WCAG 2.1 Level AA.

• Public website (homepage, location finder, services, hours, contact, ADA notice).
• Patient portal — including any portion patients log into for appointments, messaging, prescription refills, or visit records.
• Online appointment scheduling, intake forms, and registration flows.
• Pre-visit forms, post-visit summaries, and any patient-facing PDF documents (sliding-fee scale forms, financial assistance applications, consent forms).
• Mobile apps tied to patient access, telehealth, or care coordination — including third-party apps you direct patients to use.
• Marketing pages, blog posts, and educational content if they are part of how patients access services.
• Job application portals and careers pages — these are 'programs' offered by your organization, even when handled through a third-party ATS.

Holland & Knight's April 2026 guidance specifically called out the 'digital front door' — virtual visits, online intake, e-prescribing, telehealth platforms — as the highest-risk surface area for Section 504 review. If a patient with a disability cannot complete an online appointment booking with a screen reader, that is the kind of fact pattern that becomes an OCR complaint.

What an OCR Complaint Actually Looks Like

OCR enforcement of Section 504 historically follows a standard pattern: complaint filed, OCR opens investigation, voluntary resolution agreement (VRA) negotiated. The VRA typically requires the FQHC to remediate within a defined timeline, train staff, designate an ADA coordinator, post grievance procedures, and submit periodic compliance reports for 1–3 years.

Resolution agreements are public. Recent OCR healthcare actions have included six-figure remediation costs, third-party accessibility audits, mandatory annual reporting, and — in HIPAA cases — eight-figure settlements (PIH Health: $600K phishing settlement in 2025; Metropolitan Community Health Services: $25K for a 1,263-patient breach).

Section 504 will follow the same enforcement architecture: deficiency letter, VRA, public docket entry. Any FQHC facing a VRA loses the ability to claim 'we didn't know' going forward — which makes any subsequent complaint more expensive.

The 12-Month Runway Plan

If your FQHC is not yet in compliance, the extra year should become a documented remediation program, not a calendar snooze. Below is a defensible runway plan that focuses first on the surfaces that get patients through the door and the documentation OCR will look for first.

• First 30 days: run WAVE or axe DevTools scans on the homepage, location finder, services, contact, patient-portal entry page, online scheduling, PDFs, and careers pages. Tag each issue by type: keyboard navigation, color contrast, alt text, form labels, focus indicators.
• Days 31–90: fix the top three issue categories sitewide. Missing alt text and form labels are usually high-volume and low-effort. Color-contrast failures often require design-token updates. Keyboard traps and missing focus indicators are higher impact and should be owned explicitly.
• Quarter 2: test the patient portal login + scheduling flow with a screen reader (NVDA on Windows is free; VoiceOver on macOS is built in). Document every blocker, vendor dependency, remediation owner, and expected release date.
• Quarter 3: publish or refresh your accessibility statement. Designate an ADA/Section 504 coordinator and post their contact info. Establish a documented grievance procedure. These are programmatic compliance items independent of the technical fixes.
• Quarter 4 through May 2027: close vendor issues, retest with users, remediate PDFs/forms, and keep a dated remediation roadmap for remaining items. OCR distinguishes between no effort and imperfect but documented effort.

If you outsource your website to an EHR vendor (OCHIN, NextGen, eClinicalWorks portals): request their Section 504 conformance documentation and remediation roadmap in writing this quarter. You are accountable for content delivered through your domain even if a vendor renders it.

Why This Hits FQHCs Disproportionately

FQHC patient panels are weighted toward people with disabilities, older adults, and limited-English-proficiency populations — exactly the groups Section 504 was designed to protect. According to UDS data, roughly 1 in 4 FQHC patients has at least one disability that affects daily function.

Many use assistive technology to access health information online. A patient who cannot read your appointment portal with a screen reader cannot get care.

There is also a workforce dimension. A patient-portal screen-reader failure is a patient-care failure, but a careers-page accessibility failure is a workforce equity failure. FQHCs that cannot make their job application portals accessible are systematically excluding candidates with disabilities from the safety-net workforce — including the candidates most likely to share lived experience with the patient panel.

What This Connects To: Section 1557 Is Coming Right Behind

The web/mobile runway is not the only HHS civil rights item on FQHC executives' calendars. The HHS Section 1557 Annual Notice of Availability (free language assistance services in English plus the 15 most common LEP languages in your state) has been in effect since July 5, 2025 — meaning the Year 1 compliance review window approaches July 5, 2026.

California's 15 LEP languages include Spanish, Chinese, Vietnamese, Tagalog, Korean, Armenian, Russian, Persian, Arabic, Punjabi, Khmer, Hmong, Hindi, Japanese, and Mon-Khmer. The Notice has to be posted, distributed, and translated.

Two HHS OCR workstreams now overlap: digital accessibility and language access. The same compliance officer likely owns both, so the correct plan is a single civil-rights readiness calendar that separates web/mobile remediation, medical-equipment access, and language-access notice requirements.

The Bottom Line

HHS extended the Section 504 web/mobile deadline by a year, but it did not make accessibility optional. The single most useful action you can take now is to email your IT lead, communications lead, patient-experience lead, and compliance officer with the question: 'Do we have a dated Section 504 web/mobile remediation plan for May 11, 2027, and have we separated it from the July 8, 2026 medical-equipment deadline?' If the answer is hesitant, that is the next operating priority.