GitHub's accessibility program turns five, and the company is publishing its results. The pull request files-changed page was rebuilt from scratch with consistent keyboard navigation, landmarks, and adjustable line spacing, shipping seven updates over seven months before becoming the default for all users in January 2026. In April 2026, semantic search for GitHub Issues reached general availability. In June 2025, enhanced contrast controls rolled out across all GitHub themes, including for logged-out users, a first for the platform.
The program is now turning outward. GitHub hosted the first Open Source Assistive Technology Hackathon at its San Francisco headquarters, with participants contributing to 16 projects including tools for the Monarch refreshable tactile display and AI-powered PDF accessibility conversion. The October 2025 Open Source Accessibility Summit at All Things Open drew 300 registered attendees and 500 on the waitlist, producing six identified challenge areas and a public collaborative roadmap now living in the open-source-accessibility GitHub organization. Maria Lamardo co-authored a new accessibility best practices guide on opensource.guide covering semantic HTML, keyboard navigation, and accessibility statements for open source maintainers.
The full strategy document, published at accessibility.github.com, is worth reading for the internal accountability mechanisms, specifically how accessibility is tracked as an engineering fundamental through scorecards, and for the CLI team's work introducing screen reader support and ANSI 4-bit color palette customization, a section the article was cut off before finishing. The numbers and the scope of the open source community push make this more than a progress report.
[READ ORIGINAL →]