Who Counts as a Section 504 Recipient?
For HHS's Section 504 accessibility framework, the first difficult question is often not whether access matters but whether the organization and program in front of us are the recipients to which the federal rule attaches. This chapter focuses on that coverage mechanism. Its practical value is straightforward: before applying a compliance date to a website, mobile application, or service provider, identify the funding relationship and the intended recipient instead of relying on labels such as “public,” “nonprofit,” or “government-facing.”
Start with the funding relationship, not the website
Section 504 protects qualified people with disabilities from discrimination under a program or activity receiving Federal financial assistance. That wording contains a boundary. It does not describe every organization that benefits from public spending or every service that happens to be important to the public. It points to a program or activity that receives assistance, and therefore requires the reader to identify who receives it and under what arrangement.
HHS's regulations apply Section 504 to programs and activities conducted by recipients of financial assistance from the Department. The agency's 2026 interim rule names a varied set of recipients: State and local governments, social-service providers, child-welfare organizations, public and private post-secondary institutions, and health-care providers ranging from large hospital systems to small local clinics. The range is important, but the list is illustrative. A hospital is not covered merely because it is a hospital, and a local government is not classified merely because it serves the public. The relevant question is which program or activity is connected to HHS assistance and who accepted the associated conditions.
The assistance itself can take several forms. HHS describes grants, cooperative agreements, loans, qualifying contracts, subgrants, contracts under grants, and other arrangements through which the Department makes assistance available. The value supplied may be funds, services of Federal personnel, real or personal property or an interest in property, or another thing of value provided through the listed forms of arrangement. This matters because “financial assistance” can sound narrower in ordinary conversation than it is in the regulatory setting. A recipient does not have to receive a check that says “accessibility obligation” on its face for the funding relationship to be relevant.
The relationship is also formal. HHS states that funding recipients must sign a contractual assurance of compliance with the Section 504 regulations. In practical terms, the assistance is not simply a free-standing benefit detached from conditions. The recipient's decision to accept the assistance is connected to obligations governing the program or activity supported by it. The assurance is an important sign of the funding relationship, but it is not a substitute for reading the underlying award or regulation. It does not answer every question about the size of the covered activity, the limits of the award, or the status of every participant.
The words “program or activity” matter as much as the word “recipient.” They caution against treating an organization as one undifferentiated object. An institution may conduct multiple activities, receive different forms of support, and provide services through more than one channel. The supplied authorities do not establish a universal rule for how every organization-wide question must be resolved. They do establish that the reader should identify the activity connected to the assistance rather than jump from the organization's public identity to a conclusion about every service it offers. The funding instrument and the applicable regulation supply the missing facts.
This starting point prevents a common category error. A service may be publicly important without being a recipient of HHS assistance. An organization may benefit economically from a federally supported system without having accepted the federal funds or the conditions attached to them. Conversely, a recipient may operate a program through several layers of contractors and platforms; the existence of those layers does not make the original funding relationship disappear. The analysis must preserve both facts: legal coverage follows the relevant assistance relationship, while practical delivery may involve many other actors.
Imagine, for example, a clinic that receives HHS assistance for a health program and uses a commercial scheduling platform. The platform may be the place where a patient encounters the service, but its visibility does not tell us who accepted the HHS assistance. The first inquiry remains the clinic's funding relationship and the program it conducts. The next inquiry is how the platform fits into that program: it may be a contractor delivering part of the service, a separate organization with its own funding relationship, or an actor whose exact legal status cannot be determined from the facts supplied here. Calling it “the website” or “the vendor” hides the distinctions that the coverage analysis needs.
The same method works when assistance travels indirectly. Suppose the government sends value through an intermediary to the entity the governing law intends to support. The intermediary may handle the transfer without becoming the covered recipient in its own right. The reader must ask whether the intermediary is a conduit or the intended recipient, rather than assuming that the most visible participant received the assistance. This is why the legal analysis starts with the source and terms of the assistance instead of with the final user experience.
A useful way to state the mechanism is: find the assistance, read the governing arrangement, identify the intended recipient, and then locate the program or activity conducted by that recipient. Only after those steps should a reader ask how the web or mobile accessibility requirements apply. Starting with the most visible website reverses the order. It encourages conclusions based on appearance rather than authority.
The diagram does not say that a beneficiary is irrelevant. A beneficiary may be the person or organization the program is designed to help, and a connected actor may control an important part of the service experience. The point is narrower: benefit, proximity, and control are not interchangeable with receipt of Federal financial assistance. They may generate other legal or practical questions, but they do not by themselves answer the Section 504 recipient question.
What the Supreme Court's airport case clarifies
The Supreme Court made this boundary concrete in United States Department of Transportation v. Paralyzed Veterans of America. The case concerned regulations governing commercial air travel and whether Section 504 reached commercial airlines because the federal government provided financial assistance to airports and operated a nationwide air-traffic-control system.
The Court began with the underlying funding statutes. Those statutes directed Trust Fund money to airport operators for airport development and planning. The funds could support facilities such as runways, taxiways, ramps, buildings, sidewalks, and parking. The Court held that the recipients for Section 504 purposes were the airport operators. The money was not given to the airlines. Airlines used and benefited from improved airports, but the economic benefit did not make them the recipients of the airport grants.
The distinction is not a technical trick. Section 504 coverage, the Court explained, operates in the nature of a contractual condition: the recipient accepts federal funds and, with that acceptance, takes on the nondiscrimination obligations attached to the assistance. Airport operators were in the position to accept or reject the funds and the conditions that accompanied them. Commercial airlines, as described in the case, were not in that position with respect to the airport-development grants.
That reasoning rejects the idea that federal coverage automatically follows every benefit downstream. Better runways helped airlines. Airport facilities were essential to commercial air travel. The businesses, passengers, employees, and communities connected to aviation could all experience economic effects. If those ripple effects were enough, the boundary would expand almost without limit. The Court therefore separated intended recipients from intended beneficiaries and treated the underlying grant statute—not a broad concept such as “commercial aviation”—as the controlling reference point.
The case also distinguishes indirect receipt from indirect benefit. The Court acknowledged that federal assistance may be received indirectly. For example, a government may send money through an intermediary to the entity Congress intended to support. In that situation, the intermediary is a conduit and the intended recipient remains the relevant recipient even though the money does not arrive by the most direct path. But an airport operator was not a mere conduit passing airport grants to an airline. The operator was the intended recipient, and the airline benefited from the operator's use of the money. Those are different relationships.
The Court reached a similar conclusion about the federally operated air-traffic-control system. Because that system was owned and operated by the United States, the Court treated it as a federally conducted program with beneficiaries, not as Federal financial assistance received by the airlines. Government operation of a public system can create substantial benefits without creating a recipient relationship with everyone who uses or depends on that system.
The holding was specific to the Section 504 theory presented in that case. It did not mean that commercial airlines could never face accessibility or nondiscrimination requirements under another source of authority. Indeed, the opinion describes regulatory authority that the aviation agency claimed outside the federal-assistance hook. The narrower lesson is that one must identify the legal authority being invoked and the factual relationship that authority requires. A conclusion under Section 504 should not silently become a conclusion under every other accessibility regime.
That limitation is especially important when the case is used to think about digital services. A platform may be indispensable to a recipient's service in the same way that an airport facility was indispensable to air travel, but indispensability is not the legal test announced by the Court. The relevant questions are whether the platform or its operator is the intended recipient under a particular assistance arrangement, whether the recipient is using the platform to conduct a covered program, and which rule supplies the alleged obligation. Those questions may lead to different answers in different funding structures. The opinion supports the method of separating them; it does not supply facts that are missing from a modern contract.
The case also shows why a boundary can protect both precision and accountability. If every person or business touched by a federally supported system were automatically a recipient, Section 504 coverage could become almost limitless and difficult to administer. If only the organization that receives money directly mattered, a conduit or an arrangement deliberately structured to pass value indirectly could be misread. The Court's distinction avoids both extremes by asking who Congress or the funding instrument intended to receive the assistance. That is a narrower rule than “everyone connected is covered,” but a more careful rule than “only whoever receives a check is covered.”
For a recipient managing a digital service, this means that coverage analysis should produce a map, not a slogan. The map should identify the assistance, the activity, the accepted conditions, the actors involved in delivery, and the legal authority being applied. It should mark what the available facts establish and what they do not. That discipline matters before a recipient decides whether a delayed technical date changes its own work, a vendor's role, or a person's access to the program.
Applying the boundary to modern service chains
Consider a generic HHS-funded clinic that uses an outside company for appointment scheduling. The clinic's public-facing service may involve the clinic's grant relationship, its program, its own website, a licensed scheduling platform, and the patient's attempt to book care. Those facts may all matter, but they answer different questions.
First, what HHS assistance does the clinic receive, and what does the governing arrangement identify as the recipient and supported program? Second, what program or activity does the clinic conduct? Third, is the platform an outside provider delivering part of the clinic's service, a contractor within the clinic's arrangement, a conduit for some assistance, or an entity with a separate funding relationship? Fourth, what legal rule is being applied to the patient's access problem? The supplied authorities do not classify every modern platform. They do establish why the questions must be asked in that order.
This approach also avoids the opposite mistake: assuming that an organization outside the recipient category has no role in accessibility. A vendor may control a feature that determines whether people can use a recipient's service. A beneficiary may be the person who experiences exclusion. A public agency may depend on a contractor to publish information. Those practical relationships can affect what the recipient needs to investigate, procure, or correct. But the Supreme Court's reasoning cautions against converting practical importance into an unsupported statement that every connected actor is the statutory recipient.
The same caution applies to noncash assistance. The fact that no money changes hands directly does not settle the question. HHS's description includes property, services of Federal personnel, and other things of value. The Supreme Court likewise recognized that nonmoney assistance can qualify when the governing grant statute extends it. The decisive questions remain what was supplied, by what legal arrangement, and to whom it was supplied. “Not cash” is not a complete answer; “useful to the public” is not a complete answer either.
The recipient boundary therefore does two jobs. It narrows the field so that Section 504 is not treated as a free-floating rule over every economic connection. At the same time, it directs attention to the organization that accepted the federal relationship and conducts the affected program. For accessibility planning, that is a more useful starting point than counting only the number of visible digital actors. It tells a recipient to understand its funding terms and service chain, while telling a reader not to make a legal classification from a vendor's prominence alone.
Once the recipient and program relationship is identified, the next boundary comes into view. The question is no longer only who bears the federal relationship, but what that recipient provides or makes available through its digital channels. That is where the WCAG 2.1 requirement, mobile applications, and content delivered through contracts or licenses become relevant—and where the moved date must be separated from the technical scope it governs.