GitHub gives accessibility statements a home on repository pages
An ACCESSIBILITY.md file now shows up on the repo overview and in Community Standards, with a default issue label for every new repository.
GitHub started recognising ACCESSIBILITY.md as a community health file on 5 November, the same way it already treats CONTRIBUTING.md or CODE_OF_CONDUCT.md. Put the file in a repository’s root, its .github/ directory, or docs/, and GitHub surfaces it on the repository overview page and lists it under Insights > Community Standards for public repos. A starter template is provided, and organisations can set one statement in their .github/ repository for every project to inherit.
Every new repository also gets an accessibility issue label by default, giving maintainers a standard place to route reports without inventing their own convention.
Why it matters: accessibility documentation has mostly lived wherever each maintainer felt like putting it, if it existed at all. Giving it the same visibility as a licence or a code of conduct makes it a normal expectation rather than an afterthought, and the default label means contributors reporting a barrier have somewhere obvious to file it. If you maintain a public repository, adding an ACCESSIBILITY.md costs little and now gets shown to anyone evaluating whether to depend on your project.
The caveat: this is a documentation convention, not an enforcement mechanism. Nothing stops a project from claiming conformance it doesn’t have, and GitHub isn’t checking.