HHS’s section 504 web, mobile and kiosk accessibility rule (45 CFR part 84, subpart I), explained

HHS’s 2024 section 504 rule requires recipients of its funding to make web content and mobile apps meet WCAG 2.1 Level A and AA. A May 2026 interim final rule moved the compliance dates to May 11, 2027 and May 10, 2028.

Section 504 of the Rehabilitation Act sets nondiscrimination requirements tied to the receipt of Federal financial assistance, and HHS’s regulations implementing it are in 45 CFR part 84 [3]. A final rule published on May 9, 2024 (89 FR 40066), effective July 8, 2024, added subpart I, which adopts version 2.1 of the Web Content Accessibility Guidelines (WCAG) as the technical standard for recipients’ web content and mobile apps [3]. The rulemaking began with a proposal published on September 14, 2023, which drew 5,269 public comments [3].

The 2024 rule did not require immediate conformance. It set one compliance date for recipients with fifteen or more employees and a later one for smaller recipients [3]. Both dates have since moved once, and HHS has said it may revisit the substance of the rule, so the status below is as checked on November 14, 2026.

Who is covered, and what counts as their content

Subpart I applies to all programs or activities that receive Federal financial assistance from HHS [1]. The part’s definition of “recipient” is broad: any State or political subdivision, any instrumentality of either, any public or private agency, institution or organization, or any person to which Federal financial assistance is extended directly or through another recipient, excluding the ultimate beneficiary of the assistance [2].

The duty reaches web content and mobile apps that a recipient provides or makes available directly or through contractual, licensing or other arrangements [1]. Content a vendor runs for the recipient under contract is therefore inside the rule’s wording, not outside it. The definitions are wide as well:

  • Web content is the information and sensory experience communicated to the user by means of a user agent, including the code or markup that defines its structure, presentation and interactions; text, images, sounds, videos, controls, animations and conventional electronic documents are given as examples [2].
  • Mobile apps are software applications downloaded and designed to run on mobile devices such as smartphones and tablets [2].
  • Conventional electronic documents are web or app content in PDF, word processor, presentation or spreadsheet formats [2].
  • Kiosks are self-service transaction machines that recipients make available at set physical locations for patients or program participants to use on their own, for example to check in, provide information, procure services or have vital signs taken [2].

The standard and the current compliance dates

Recipients must ensure that their web content and mobile apps are readily accessible to and usable by individuals with disabilities [1]. The measurable test is conformance with the Level A and Level AA success criteria and conformance requirements of WCAG 2.1, which the regulation incorporates by reference [1]. The current text sets these dates [1]:

  • Recipients with fifteen or more employees: beginning May 11, 2027.
  • Recipients with fewer than fifteen employees: beginning May 10, 2028.

Those dates come from an interim final rule published on May 11, 2026 (91 FR 25496). It states that it took effect on May 7, 2026, and it accepted comments until July 6, 2026 [3]. It replaced the 2024 rule’s dates of May 11, 2026 and May 10, 2027, and HHS says it changes no other provision of the 2024 rule [3].

Kiosks are treated differently. Section 84.83 bars excluding a qualified individual with a disability from, or discriminating against them in, any program or activity provided through kiosks, and it names no technical standard and no compliance date [1].

Five kinds of content the standard does not reach

The WCAG requirement in section 84.84 does not apply to [1]:

  • Archived web content, which the definitions limit to content created before the recipient’s compliance date (or reproducing paper or other media from before then), kept only for reference, research or recordkeeping, not altered after archiving, and organized and stored in a dedicated area clearly identified as archived [2].
  • Preexisting conventional electronic documents available before the compliance date, unless they are currently used to apply for, gain access to or participate in the recipient’s programs or activities [1].
  • Content posted by a third party, unless the third party posts it because of contractual, licensing or other arrangements with the recipient [1].
  • Individualized documents that are about a specific person, their property or their account and are password-protected or otherwise secured [1].
  • Social media posts made before the recipient’s compliance date [1].

The exceptions are narrower than they first appear. A PDF intake form posted years ago is still in scope if people use it today to apply for services, and content a third party posts because of contractual, licensing or other arrangements with the recipient falls outside the third-party exception [1].

Alternatives, burden limits and minor gaps

  • Conforming alternate versions, as WCAG 2.1 defines them, may be used only where it is not possible to make the content directly accessible because of technical or legal limitations [1].
  • Equivalent facilitation: other designs, methods or techniques are allowed if they give substantially equivalent or greater accessibility and usability [1].
  • Fundamental alteration or undue burden: the recipient carries the burden of proof. The decision must be made by the head of the recipient or a designee after considering all resources available for the program, with a written statement of reasons, and the recipient must still take other action that gives people with disabilities the benefits or services to the maximum extent possible [1].
  • Minimal impact: a recipient that is not in full conformance is treated as meeting the requirement if it can show the gap does not affect people’s ability to get the same information, make the same interactions and transactions, and otherwise take part, with substantially equivalent timeliness, privacy, independence and ease of use [1].

Why HHS moved the dates, and what it said comes next

In the interim final rule, HHS said the 2024 compliance dates were unlikely to be met by a significant number of recipients, especially local governments and small and medium-sized recipients, for reasons beyond the control of HHS and of recipients [3]. It cited comments from a representative of primary health care associations that federally qualified health centers were working toward conformance but having trouble with specific criteria, such as making electronic documents fully accessible and ensuring web content can be operated with a keyboard alone, without a mouse [3]. It also cited letters from associations of counties and cities, sent to the Office of Management and Budget during a Justice Department rulemaking, describing remediation costs, especially for PDF documents [3].

HHS also tied its decision to the Americans with Disabilities Act. The Justice Department’s 2024 rule under title II of the ADA imposes substantially similar requirements on State and local government entities, many of which also receive HHS funding, and on April 20, 2026 the Justice Department published an interim final rule delaying that rule’s compliance dates by one year (91 FR 20902) [3]. Our ADA title II explainer covers that rule.

On what comes next, the interim final rule says HHS plans future rulemaking on the substance of the 2024 rule and will consider issuing a proposal during the extension, including changes that would affect the web and mobile requirements [3]. It also says that if no such proposal is issued and no circumstances suggest further delay, HHS fully anticipates implementing the regulation at the new deadlines [3]. Separately, it states that recipients have an ongoing obligation to make programs offered through web content and mobile apps accessible under their other section 504 obligations, whatever the compliance dates [3]. As checked on November 14, 2026, the eCFR text, current to November 12, 2026, carries the 2027 and 2028 dates [1].

What this means for a health system’s digital front door

In our view, the practical scope is the whole patient journey that runs through screens: appointment booking, bill payment, intake forms, the patient portal and the mobile app, including the parts a vendor hosts. The extension gives time, and the HHS statement about possible changes adds uncertainty, but the WCAG 2.1 test, the vendor coverage and the narrow document exceptions are what the current text says [1]. Procurement is where much of the work lands: contracts and acceptance testing for portals, scheduling tools and kiosks are where conformance evidence can be asked for before go-live. Kiosks deserve separate attention because subpart I gives them a nondiscrimination duty without a technical standard [1].

This explainer describes the regulation; it is not legal advice, and organizations should confirm with counsel how it applies to their programs.

Moraph’s teams help organizations with work like this. See our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • HHS
  • section 504
  • 45 CFR part 84
  • web accessibility
  • WCAG 2.1
  • mobile apps
  • kiosks
  • patient portals