GitHub has published a one-year progress report on its 2025 pledge to build a more inclusive open source ecosystem, detailing hackathon outcomes, new accessibility tooling, and two upcoming 2026 community events for contributors and maintainers GitHub’s official pledge progress update.
The update covers work across three core pledge goals: empowering disabled contributors, expanding open source assistive technology, and improving accessibility in mainstream open source workflows, with concrete programs and open tooling shipped over the past 12 months.
Concrete steps toward a more inclusive open source ecosystem
The most visible program under the pledge was the May 2026 Open Source Assistive Technology Hackathon, hosted at GitHub’s San Francisco headquarters over two days. The event brought together contributors, maintainers, educators, accessibility advocates, and people with disabilities to build open source tools addressing real access barriers.
Participating project teams built a range of tools, including visual-sensor assistive systems for blind and low-vision users, automated pipelines that convert standard PDF files into screen-reader-accessible formats, open-source wheelchair control software and hardware, accessibility-focused route planning tools, screen reader pronunciation refinement tools, accessible gaming interfaces, tactile multiline braille display interfaces, and adaptable physical tools and accessories GitHub’s official pledge progress update.
To lower participation barriers for disabled contributors, GitHub hosted a dedicated GitHub Learning Room with hands-on guidance for GitHub workflows optimized for NVDA screen readers and keyboard-only navigation. The event also included office hours with the core NVDA screen reader development team to provide project-specific troubleshooting support for hackathon teams GitHub’s official pledge progress update.
GitHub also expanded its accessibility documentation for disabled contributors, with all guides co-authored and reviewed by people with lived experience to align with real-world usage patterns. The documentation covers step-by-step guidance for using GitHub products with screen readers and other assistive technologies, plus targeted recommendations for developers building Copilot and AI agent integrations with accessibility as a core requirement GitHub’s official pledge progress update.
Open source accessibility tooling for maintainers
In October 2025, GitHub hosted the first Open Source Accessibility Summit in Raleigh, North Carolina, in partnership with All Things Open. The one-day in-person event gathered disability, accessibility, and open source community members to define a shared, public roadmap for improving accessibility across open source software, which has already been translated to tangible, free tooling for maintainers who may lack dedicated accessibility expertise GitHub’s official pledge progress update.
To coordinate ongoing roadmap work, GitHub launched the public Open Source Accessibility organization on GitHub, which hosts all pledge-related tooling and tracks progress against the shared accessibility roadmap. The organization also released a free, open source accessibility best practices guide that includes step-by-step instructions for adding an ACCESSIBILITY.md file to repositories and integrating automated accessibility checks into existing CI pipelines GitHub’s official pledge progress update.
For code-level accessibility, GitHub released the GitHub Accessibility Scanner, an AI-powered open source tool that integrates directly with GitHub Actions and Copilot to automatically detect, file, and fix common accessibility barriers in codebases. For design teams, GitHub also released the open source Accessibility Annotation Toolkit for Figma, which adds pre-built accessibility annotation components to streamline accessibility-focused design handoffs GitHub’s official pledge progress update.
All released tooling is built to integrate into existing development workflows without requiring teams to adopt separate, time-consuming accessibility-specific processes GitHub’s official pledge progress update.
Upcoming events to grow inclusive participation
GitHub has announced two 2026 events to expand access to open source for disabled contributors and educate maintainers on accessibility best practices. The first event, the free virtual Open Source Accessibility Community Day, is scheduled for July 9, 2026, and is open to all contributors, maintainers, accessibility practitioners, and community members regardless of experience level GitHub’s official pledge progress update.
The event will feature live demos and progress updates from teams that participated in the May 2026 assistive technology hackathon, including breakdowns of completed builds, lessons learned during development, and specific contribution opportunities for attendees who want to support ongoing project work GitHub’s official pledge progress update.
The second event is the second annual Open Source Accessibility Summit, scheduled for October 19, 2026, in Raleigh, North Carolina, held again in partnership with All Things Open. The summit is designed to teach contributors of all experience levels how to contribute to open source while adhering to accessibility best practices, with all sessions grounded in the lived experiences of people with disabilities to ensure practical, real-world skill building GitHub’s official pledge progress update.
Unlike many open source accessibility events that focus exclusively on advocacy or high-level policy, the 2026 summit is structured to deliver actionable, hands-on skills for contributors who may be new to both open source and accessibility work. Community members can follow the Open Source Accessibility organization on GitHub and join its associated public Slack workspace to receive real-time updates on roadmap progress and year-round contribution opportunities GitHub’s official pledge progress update.
Bottom line: GitHub’s full suite of free open source accessibility tooling — including the AI-powered Accessibility Scanner, ACCESSIBILITY.md best practices guide, and Figma Annotation Toolkit — is available now for all maintainers to integrate into existing workflows, while the free July 9 virtual Community Day and October 19 in-person Raleigh Summit provide structured, skill-based entry points for contributors of all experience levels to start building more inclusive open source projects.
