GitHub joins the GAAD Pledge for open source accessibility

GitHub has signed the Global Accessibility Awareness Day (GAAD) Pledge, making a public commitment to improve accessibility in open source software. The pledge, launched by the GAAD Foundation in 2020, asks organizations to embed accessibility into the core of their open source work. GitHub's participation centers on three interdependent objectives: enabling people with disabilities to contribute to open source, expanding the availability of open source assistive technologies, and raising the accessibility bar for mainstream open source projects.

Why contributor diversity matters

Roughly 16% of the global population — about 1.3 billion people — live with a disability, yet barriers in development platforms and tools often exclude them from shaping the software everyone uses. GitHub points to contributors like Becky Tyler, a University of Dundee student with quadriplegic cerebral palsy who interacts with her computer using only her eyes. Tyler's path into coding began with Minecraft and led her into open source development, illustrating what becomes possible when accessibility barriers are removed.

The blockers are often mundane: missing keyboard operability, insufficient color contrast, and incompatibility with screen readers and other assistive technologies. Removing those obstacles allows every developer to continue practicing their craft regardless of disability.

The assistive technology gap

Many people with disabilities rely on assistive technology to use computers at all, but proprietary options can be prohibitively expensive. That cost problem is compounded by employment and education disparities — people with disabilities are less likely to be employed or hold advanced degrees, according to U.S. Bureau of Labor Statistics data cited by GitHub.

Open source offers an alternative path. There are no financial or bureaucratic hurdles to creating an assistive tool on GitHub, and open source licenses let anyone use and improve them. A notable example is NVDA, the free Windows screen reader built by Jamie Teh and Michael Curran, which has grown a community of hundreds of blind developers and contributors alongside more than 250,000 users over the past 15 years. GitHub argues more such projects are needed, along with greater awareness of them among people with disabilities and the professionals who support them.

Upstream accessibility is infrastructure work

Open source underpins the modern software economy: 90% of companies use it, 97% of codebases contain it, and estimates place its global value at $8.8 trillion. When frameworks, libraries, and infrastructure projects are inaccessible, every downstream application built on them inherits those flaws. Fixing accessibility problems upstream makes it possible — and affordable — for consuming applications to be accessible. Neglecting it upstream can make downstream accessibility impossible or prohibitively expensive.

There's a secondary benefit. Popular open source communities set industry norms. When those communities treat accessibility as a core requirement rather than an afterthought, they raise expectations for developers across the wider industry.

GitHub breaks down the need for accessible mainstream projects along three user groups:

  • End users: people with disabilities using applications built on open source.
  • Consumers: developers and IT professionals with disabilities who must access documentation, videos, and enablement materials to build on projects.
  • Contributors: developers and others with disabilities who want to join open source communities and participate in creation and learning.

Strategy and next steps

GitHub acknowledges that accessibility work is never finished; technology evolves continuously, so the effort must be treated as an ongoing practice. Its strategy has three prongs.

Platform improvements

GitHub says it has resolved more than 4,400 accessibility issues on its platform since January 2022 and has integrated accessibility into its product development life cycle (PDLC). Going forward, it will continue shifting accessibility earlier in the PDLC so that features ship accessible by default, and will seek opportunities to make default options accessible with gentle guidance toward better outcomes.

Partnerships

GitHub frames its pledge as a call to action for the broader technology industry. It specifically wants to work with Open Source Program Offices (OSPOs) across the private sector, public sector, academia, and NGOs, noting that strengthening accessibility regulations — like the European Accessibility Act and the recent Title II rule under the Americans with Disabilities Act — make this work relevant for every sector. The company also emphasizes collaboration "with" rather than "for" the global community of people with disabilities, and invites them into the open source movement as leaders and contributors.

Community enablement

GitHub plans to engage open source maintainers to help build communities where accessibility is a shared value, meeting projects of all sizes — from single-contributor efforts to large foundations — wherever they are on their accessibility journey.

As a concrete next step, GitHub is organizing an Open Source Accessibility Summit to bring together disability advocates, accessibility professionals, and the open source community to define shared next steps. Details are expected on the GitHub Blog.