Turning Accessibility Commitments Into Open Source Practice

A year ago, GitHub laid out a pledge to make open source more accessible, built on three pillars: helping people with disabilities contribute, boosting assistive technology projects, and improving accessibility across mainstream open source. Since then, the work has moved from that public commitment into concrete programs, partnerships, and open tooling. Here is a look at what has happened and where help is still needed.

Building Pathways for Contributors With Disabilities

The Open Source Assistive Technology Hackathon took place at GitHub’s San Francisco headquarters in May 2026. Across two days, developers, maintainers, educators, advocates, and people with disabilities worked side by side on assistive technology projects aimed at removing real barriers.

To make the event genuinely inclusive, organizers offered a GitHub Learning Room focused on workflows using the NVDA screen reader and keyboard-only navigation, plus office hours with the NV Access team for troubleshooting support.

Complementing the event, GitHub’s accessibility documentation was developed so contributors can use GitHub products with assistive tech while also learning how to use Copilot and agents in ways that respect accessibility needs. People with lived experience helped write and review these guides, which means the material reflects actual day-to-day workflows.

Assistive Tech Projects in Motion

Hackathon participants split their effort across a wide range of challenges:

  • Camera-based assistance for blind and low vision users
  • PDF-to-accessible-format conversion
  • Open wheelchair software and hardware
  • Route planning with accessibility in mind
  • Screen reader pronunciation updates
  • Accessible game development
  • Tactile prototypes for a multiline braille display
  • Adaptable physical tools and accessories

Progress updates are tracked in the Open Source Assistive Technology Hackathon repository.

Accessibility in Mainstream Workflows

In October 2025, the first Open Source Accessibility Summit was held in Raleigh, NC alongside All Things Open. This one-day in-person gathering connected disability, accessibility, and open source communities to map a shared roadmap for improving software accessibility.

On the tooling side, a set of practical resources has been introduced to weave accessibility checks into the everyday development loop:

  • The Open Source Accessibility organization serves as a shared space for roadmaps and collaboration.
  • A best practices guide covers topics such as creating an ACCESSIBILITY.md file and folding accessibility checks into CI.
  • GitHub accessibility documentation helps teams use core products with assistive technologies.
  • The GitHub Accessibility Scanner, an AI-powered open source tool, leverages GitHub Actions and Copilot to detect and help fix accessibility issues.
  • The Accessibility Annotation Toolkit brings an open source Figma kit into design and handoff workflows.

These efforts are meant to cut friction: write clearer issues, collaborate better, and build accessibility in from the start rather than patching it on later.

Two Immediate Ways to Get Involved

Register for the Open Source Accessibility Community Day (July 9, 2026). This virtual event will bring together contributors, maintainers, accessibility practitioners, and community members. Expect demos and project updates from the hackathon teams, highlighting what they shipped, what they learned, and where they need new contributors.

Register for the Open Source Accessibility Summit (October 19, 2026). Back in Raleigh with All Things Open, this second summit aims to teach participants how to contribute to open source while following accessibility best practices, regardless of experience. Lived experiences of people with disabilities will anchor the sessions, and the takeaway is meant to be practical: attend and you should be ready to make accessibility-conscious contributions to the ecosystem.

To stay plugged in, follow the Open Source Accessibility organization and join the Open Source Accessibility Slack. There is momentum to build on.