GitHub expands accessibility push with new open-source tools

GitHub has expanded its accessibility programme beyond its own platform with new open-source tools, product updates and customer initiatives, broadening its work across software development workflows.

The changes include accessibility updates to GitHub CLI, the open-source release of an AI-based accessibility scanner, a Figma annotation toolkit for design teams, and the creation of the GitHub Enterprise Accessibility Advisory Panel for customers. GitHub is also hosting its first Open Source Assistive Technology Hackathon at its San Francisco headquarters.

The announcement marks a shift for a programme that began five years ago as an internal effort to address accessibility issues in GitHub's own products. It now extends to the wider developer community and to open-source projects that are often widely used but not always designed with disabled users in mind.

Ed Summers, head of accessibility at GitHub, outlined that direction in a company update. "What began as a small team addressing accessibility debt has grown into a company-wide discipline, woven into our engineering fundamentals, our design system, our AI tools, and our culture," he said.

One practical change is in the company's command-line tools. GitHub has introduced a dedicated screen reader mode in GitHub CLI, along with a theme picker that includes colour-blind-friendly variants, keyboard-first navigation, and layouts designed for narrower terminal windows and different screen setups.

The updates reflect a wider push into an area of software development that has often received too little attention on accessibility. The terminal remains a central tool for many developers, but command-line interfaces can create problems for screen readers and users with low vision if prompts, status indicators and colour choices are not designed carefully.

GitHub has also published guidance on using Git, GitHub CLI and GitHub Copilot CLI with a screen reader. The material includes installation notes and workflow steps intended to help blind developers work more independently in terminal environments.

Design and scanning

Alongside the command-line updates, GitHub has made two internal tools available more broadly. One is a Figma Annotation Toolkit that lets design teams record accessibility intent inside design files, including heading structure, keyboard navigation, ARIA semantics and screen reader announcements.

Its audit work found that 48% of accessibility issues could have been avoided at the design stage. By releasing the toolkit, GitHub aims to make that documentation method available beyond its own teams.

The second tool is an AI-powered accessibility scanner built with the GitHub Copilot Cloud agent. GitHub says it is designed to help teams identify, file and fix accessibility issues inside CI/CD workflows. It uses the open-source axe-core library from Deque Systems for static DOM analysis and now includes a plugin architecture, with an initial plugin aimed at WCAG reflow violations.

The release fits GitHub's wider effort to share more of its internal accessibility processes with customers. It has also published accounts of how its teams automate accessibility governance and handle incoming reports, including a workflow in which GitHub Copilot fills in much of the issue metadata.

According to GitHub, that process has cut resolution time by 62% and helped 89% of issues close within 90 days.

Open-source focus

GitHub is also trying to expand accessibility work in open source. Its assistive technology hackathon brings contributors together around 16 projects, including tools for blind students using refreshable tactile displays, software that converts PDF files into more accessible formats, and technology linked to power wheelchairs.

The event also includes office hours for the NVDA screen reader and practical support for people learning open-source workflows on the platform.

GitHub has also backed a broader effort to establish accessibility best practice for maintainers. Work published with contributors to the Open Source Guides project covers topics such as accessibility statements, accessible documentation, keyboard navigation and semantic HTML.

Customer panel

For business users, GitHub has created the GitHub Enterprise Accessibility Advisory Panel, known as GAAP. The forum is intended to bring together GitHub and accessibility professionals at enterprise customer organisations to discuss software development workflows and platform needs.

The panel is meant to connect customers' day-to-day accessibility problems with the features available on the platform, while also helping identify gaps.

The wider programme also includes internal measures for staff, including mandatory accessibility training and updates to employee self-identification categories related to disability. GitHub says employee groups such as NeuroCats and AccessCats also help shape policy and support inside the company.

Summers said the company sees the latest work as part of a wider cultural change rather than a completed project. "Accessibility is never done. Publishing our strategy is not the finish line-it is the starting line for the next chapter. We are building in public, sharing our tools, and inviting the global developer community to join us," he said.