Skip to main content
📚 Cite this page

AMA
Weru Lawrence. Untitled. The ENABLE Model website. Published 2026. Accessed 2026-04-01. https://enablemodel.com/docs/manifestations/gaad-foundation

APA
Weru, L. (2026). Untitled. The ENABLE Model. https://enablemodel.com/docs/manifestations/gaad-foundation

MLA
Weru, Lawrence. "Untitled." The ENABLE Model, 2026, https://enablemodel.com/docs/manifestations/gaad-foundation.

Chicago
Weru, Lawrence. "Untitled." The ENABLE Model. 2026. https://enablemodel.com/docs/manifestations/gaad-foundation.

BibTeX

@misc{enable2026gaad-foundation,
              author = {Weru, Lawrence},
              title = {Untitled},
              year = {2026},
              url = {https://enablemodel.com/docs/manifestations/gaad-foundation},
              note = {The ENABLE Model}
            }

GAAD Foundation

Digital product teams organize GAAD-related bug-bash events and other GAAD activities to identify and fix accessibility barriers before major releases; GAAD events and community/company activities are catalogued on the official GAAD site.2

ENABLE Model location

What it is​

The GAAD Foundation is a nonprofit organization dedicated to advancing digital accessibility worldwide. It launched in May 2021 to mark GAAD’s 10th anniversary and to drive systemic change in how organizations approach accessibility. The Foundation convenes product teams, developers, and designers to participate in focused activities -- including bug-bashes, the GAAD Pledge, and other programs -- where teams audit, triage, and remediate accessibility issues in their products. These activities encourage organizations to prioritize accessibility testing, triage, and iteration as part of their development cycle.1

Why it matters​

When builders neglect accessibility, disabled users are forced to compensate for inaccessible digital products, increasing their burden and excluding them from full participation. The GAAD Foundation's bug-bash model represents a builder-side intervention, shifting responsibility upstream by making accessibility a recurring, visible priority. Instead of relying on users to report barriers or invent workarounds, teams proactively seek out and fix issues, redistributing labor away from navigators. This approach addresses forces-that-disable such as abandonment and precarity, and helps embed accessibility into organizational culture.

Real-world example​

GAAD draws a wide range of community and corporate participation: the GAAD events site catalogs hundreds of community- and company-run activities each year, and the GAAD Foundation documents programs such as the GAAD Pledge -- which GitHub has taken as an ongoing commitment to improve the accessibility of open-source software.2 Individual organizations frequently run internal bug-bashes and remediation sprints around GAAD to audit, triage, and fix accessibility issues discovered during those events.

What care sounds like (builder-side interventions)​

Care at the qa-testing, triage, and iteration stages involves:

  • "We're running a GAAD bug-bash to catch accessibility issues before launch."
  • "We prioritize accessibility bugs alongside other critical defects."
  • "We review user feedback and iterate on our solutions to ensure access."

What neglect sounds like (builder-side interventions)​

Neglect involves:

  • "Accessibility isn't part of our release checklist."
  • "We'll fix accessibility bugs if users complain."
  • "We don't have time to test for accessibility this cycle."

What compensation sounds like (navigator-side compensations)​

Compensation describes the labor disabled users undertake when upstream care is absent:

  • "I have to use a third-party extension just to read this content."
  • "I report accessibility issues every release, but they rarely get fixed."
  • "I rely on colleagues to help me navigate inaccessible features."

All observations occur within the context of digital product development and accessibility advocacy.


Edited by Lawrence Weru S.M. (Harvard)

📝 Disclaimer

The ENABLE Model draws on the principles of anthropology and the practice of journalism to create a public ethnography of accessibility, documenting how people intervene or compensate for accessibility breakdowns in the real world. Inclusion here does not imply endorsement. It chronicles observed use -- how a tool, organization, or strategy is actually used -- rather than how it is marketed. References, when provided, are for verification and transparency.


📚 Cite this page

AMA
Weru Lawrence. Untitled. The ENABLE Model website. Published 2026. Accessed 2026-04-01. https://enablemodel.com/docs/manifestations/gaad-foundation

APA
Weru, L. (2026). Untitled. The ENABLE Model. https://enablemodel.com/docs/manifestations/gaad-foundation

MLA
Weru, Lawrence. "Untitled." The ENABLE Model, 2026, https://enablemodel.com/docs/manifestations/gaad-foundation.

Chicago
Weru, Lawrence. "Untitled." The ENABLE Model. 2026. https://enablemodel.com/docs/manifestations/gaad-foundation.

BibTeX

@misc{enable2026gaad-foundation,
              author = {Weru, Lawrence},
              title = {Untitled},
              year = {2026},
              url = {https://enablemodel.com/docs/manifestations/gaad-foundation},
              note = {The ENABLE Model}
            }