Being Heumann: What a 1977 Sit-In Still Teaches Us About Access

There is no wheelchair ramp in the opening scene of the Being Heumann trailer. There are stairs. That absence — architectural, political, deliberate — is the whole story.

Apple Original Films is bringing Judy Heumann's life to theaters November 6, with a streaming release on Apple TV+ following November 13. The film premieres at the Toronto International Film Festival this week, directed by Siân Heder, who won an Academy Award for CODA. Ruth Madeley, an actor with spina bifida, plays Heumann — a casting decision that is itself a statement about who gets to tell these stories. The film centers on the 1977 San Francisco Federal Building sit-in, where Heumann led more than a hundred disabled people in a nearly month-long occupation demanding the federal government enforce Section 504 of the Rehabilitation Act (opens in new window), the first federal civil rights law explicitly protecting people with disabilities.

Heumann's line in the trailer is precise: "They see you in front of the stairs and they think that you're the problem. The stairs are the problem." That reframe — from individual deficit to systemic design failure — is the conceptual foundation of modern disability rights law. It's also the framing that practitioners in digital accessibility have been trying to operationalize for two decades.

Section 504: Law Without Enforcement Is Paper

The 1977 sit-in wasn't just a protest. It was a demand for implementation. Section 504 had been signed into law in 1973, but the Carter administration had not issued the regulations needed to enforce it. Heumann and her fellow activists weren't fighting for new legislation — they were fighting for the government to follow through on law that already existed.

That gap between policy and implementation is not a historical artifact. It's the central challenge of accessibility compliance today. Organizations routinely acknowledge WCAG standards, post accessibility statements, and sign settlement agreements — then fail to build the internal capacity to sustain what they've committed to. Our research on settlement implementation patterns documents exactly this: legal victories that produce compliance documents without producing accessible systems.

Heumann understood this dynamic intuitively. She spent her career not just winning legal protections but pushing for their enforcement — helping develop the Individuals with Disabilities Education Act (opens in new window), the Americans with Disabilities Act, and the U.N. Convention on the Rights of Persons with Disabilities. The pattern across her work was consistent: law without enforcement infrastructure is just paper.

Building Accessibility Under Constraint: The Operational Lesson

From an operational capacity standpoint, the 1977 protest is a masterclass in resource strategy under constraint. More than a hundred people with significant disabilities occupied a federal building for 28 days. They coordinated medical care, food delivery (the Black Panther Party famously provided meals), communications, and political pressure simultaneously. They built operational infrastructure on the fly, with no budget and no institutional support.

What that demonstrates — and what the film will likely dramatize — is that accessibility doesn't require perfect conditions. It requires clear priorities, community knowledge, and sustained commitment. Organizations that treat accessibility as a compliance checkbox are, structurally, making the same mistake the Carter administration made in 1976: acknowledging the law while declining to build the systems that make it real.

The operational parallel for development teams is direct. Accessibility integrated into design systems, component libraries, and CI/CD pipelines from the beginning costs a fraction of what retrofit remediation costs. The WCAG 2.1 success criteria (opens in new window) aren't obstacles to building good software — they're specifications for software that works for everyone. The stairs aren't the problem because disabled people exist. The stairs are the problem because someone chose to build stairs without thinking about who would need to use the building.

| Heumann's Historical Context | Modern Digital Parallel | Primary Standard | |---|---|---| | Section 504 signed 1973, unenforced until 1977 | WCAG published 1999, inconsistently implemented today | 28 CFR Part 35 (opens in new window) (Title II) | | Physical building access barriers | Digital interface access barriers | WCAG 2.1 SC 1.3.1 (opens in new window) | | Denied teaching license due to disability | Inaccessible employment portals blocking job applications | WCAG 2.1 SC 4.1.2 (opens in new window) | | Federal building sit-in to force enforcement | DOJ settlement agreements requiring remediation plans | ADA.gov enforcement (opens in new window) | | Heumann blocked a city bus to demand access | Screen reader users blocked by missing ARIA labels | WCAG 2.1 SC 1.1.1 (opens in new window) |

Why Casting Matters: Disabled Expertise in Decision-Making

Ruth Madeley has spina bifida. She is a wheelchair user playing a wheelchair user. This should be unremarkable. It isn't — and that gap between what should be normal and what is actually normal is worth examining.

The accessibility field has a version of this problem. Accessibility decisions are routinely made without disabled people in the room. Audits are conducted by non-disabled practitioners using automated tools that, by documented evidence, catch at most 37% of real barriers — a finding detailed in our analysis of automated testing methodology limitations. The remaining 63% of barriers — the ones that actually prevent people from using systems — require human judgment, and ideally, the judgment of people with direct experience navigating those barriers.

Heder's CODA cast primarily deaf actors in a film about a deaf family. Being Heumann casts a disabled actor as a disabled activist. The pattern suggests something about what authentic representation requires: not just good intentions, but structural decisions about who has authority in the creative process. Compliance teams building genuinely accessible systems face the same structural question. Who has decision-making authority? Whose experience is treated as expertise?

What This Film Could Actually Change

Cautious optimism is warranted here — not because a movie will fix systemic ableism, but because of what this particular film, from this particular platform, at this particular moment, might accomplish.

Apple has published accessibility commitments (opens in new window) and built significant accessibility features into its hardware and software ecosystem. An Apple Original film about the activist who helped create the legal framework for disability rights — premiering at TIFF, starring a disabled actor, directed by an Oscar winner — reaches audiences who may never have encountered the history of Section 504 or the 1977 sit-in.

Heumann died in 2023. The film is, in part, a record. But it's also an argument: that the barriers disabled people face are designed, not natural. That they can be redesigned. That the people most affected by those barriers are the ones who understand them most clearly — and who have the most at stake in changing them.

For practitioners working in Title II compliance or digital accessibility, that argument has direct operational weight. The compliance frameworks we navigate — Section 508 (opens in new window), WCAG, state-level digital accessibility laws — exist because people like Heumann refused to accept that exclusion was inevitable. Understanding that history doesn't make compliance work easier. But it clarifies what the work is actually for.

The Takeaway: Refuse the Gap Between Policy and Practice

The 1977 sit-in succeeded because it refused to accept the gap between law and implementation. That refusal is the right model for accessibility work today.

If your organization has an accessibility policy that isn't reflected in your actual products, you're in the same position as the Carter administration in 1976: you've acknowledged the standard and declined to enforce it. The compliance framework fragmentation that makes this easier to rationalize — too many standards, too many requirements, unclear priorities — is real, but it's also a reason to build clearer internal capacity, not a justification for inaction.

Watch Being Heumann when it opens. Not because it will teach you WCAG criteria, but because it will remind you what the criteria are protecting. Then go look at what your team actually shipped last quarter and ask whether someone using a screen reader, a switch device, or a voice interface can use it. The stairs are still the problem. The question is whether you're building them.