Skip to content
Theme
OnDevice Tools

SoftwareOpen Source & Linux

Open Source Accessibility Framework arrives on GitHub

GitHub has introduced the Open Source Accessibility Framework and a project called Replica, alongside new support for ACCESSIBILITY.md files in repositories. The company says the work is aimed at collaboration and inclusion.

Illustration of a code repository page showing an accessibility document beside open source project files

Key takeaways

  • GitHub announced the Open Source Accessibility Framework and a project called Replica on 19 November 2026.
  • GitHub describes both as open source projects for collaboration and inclusion.
  • GitHub now highlights ACCESSIBILITY.md files in repositories.
  • The file can record accessibility goals, known barriers, supported environments, contributor expectations and reporting processes.
In this article
  1. What GitHub announced
  2. Accessibility statements get a home
  3. Why the file matters to maintainers
  4. What comes next

What GitHub announced

Illustration: code, GitHub logo, storage, building and the labels Accessibility, GitHub, Open Source Accessibility Framework

GitHub used a post on its blog on 19 November 2026 to introduce the Open Source Accessibility Framework and a second project called Replica. According to the GitHub Blog, both are new open source projects intended to support collaboration and inclusion. The post presents the releases as an example of the idea that the best things in open source are made together.

The announcement did not set out how Replica works, what it is built with or when it will be available. Readers who want those technical details will need to follow GitHub's own project pages and blog for later posts.

Accessibility statements get a home

Alongside the two projects, GitHub now highlights ACCESSIBILITY.md files in repositories. The file gives maintainers a fixed place to set out their accessibility aims and the barriers users already know about.

GitHub says the file can also record which environments a project supports, what is expected of contributors and how people should report accessibility problems. That turns a scattered set of issues and emails into one document that sits with the code.

Why the file matters to maintainers

A named file is easy to find, which helps contributors and users check a project's position before they open an issue. It also gives newcomers a clear route for reporting problems, rather than leaving them to guess where to post.

Documenting known barriers may also help maintainers be honest about what does not work yet, instead of implying that a project is fully accessible. The approach fits a wider pattern in open source, where shared conventions let many separate projects handle the same problem in a similar way.

What comes next

The framework and Replica are presented as starting points for community work, so their direction will depend on the people who take part. Maintainers who want to adopt the convention can add an ACCESSIBILITY.md file to a repository and fill in the sections GitHub describes.

Anyone affected by accessibility problems in a project should still use that project's own reporting process. GitHub's blog post is the official source for the announcement and for any later changes to the guidance.

Sources

  1. The best things in open source are built togetherGitHub Blog

Tags

Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.