GitHub announced on November 5, 2026 that it now treats ACCESSIBILITY.md as a recognized community health file. When a repository has one, the file appears as its own Accessibility tab on the repository overview, and the About section links to it, much like a README, license or security policy.
The change gives open source projects a predictable place to record accessibility goals, known barriers and the way users can report problems. It also comes with a starter template in Community Standards and a new default issue label, so maintainers can begin with very little setup work.
What changed on GitHub
Until now, accessibility notes in a project were usually scattered across issues, contributing guides, audit documents and chat threads. A person who hit a barrier had to hunt for any information, and that knowledge often faded as maintainers came and went.
GitHub now detects the file and surfaces it next to the other community health files. The main parts of the update are:
- Repository overview tab: a repository with an ACCESSIBILITY.md file now shows a dedicated Accessibility tab on its main page, plus a link from the About panel.
- Three supported locations: GitHub checks the .github directory first, then the repository root, then the docs directory.
- Organization default: a repository without its own file can inherit one from the organization's .github repository.
- Starter template: public repositories can create or suggest the file through the Community Standards page under Insights, where an Accessibility entry now sits under additional community files.
- Default label: newly created repositories include an accessibility issue label out of the box.
How the feature works
The file is plain Markdown, so there is no special syntax to learn. The template from Community Standards holds its guidance inside comments, which GitHub hides when it renders the page. Maintainers replace those prompts with details about their own project and commit the result.
The new label is meant to work together with the statement. The document tells people how to raise a barrier and what will happen next, while the label lets maintainers sort and follow those reports in the issue tracker.
Organization owners get the most reach from the inheritance rule. A single file in the shared .github repository can cover every project that does not define its own, which is handy for companies with dozens of small repositories.
What GitHub suggests putting in the file
GitHub says there is no required format, because a tiny library and a large web app have very different users and resources. Its guidance lists several areas worth covering:
- Priorities, and which user journeys get accessibility attention.
- Checks or review steps expected from contributors, including coding agents.
- A direct reporting route that does not ask anyone to disclose a disability or attach screenshots and recordings.
- How maintainers acknowledge, triage and follow up on reports.
- The platforms, browsers, input devices and assistive tools that are supported or tested.
- Known limitations with workarounds and links to tracked fixes.
- Who owns the statement and how people can suggest changes to it.
The post also warns about one common mistake. Naming a WCAG version and level as a goal is fine, but it is not the same as proven conformance, which needs a real evaluation with a stated scope, date, method and evaluator.
As live examples, GitHub points to the statements in GitHub CLI and the GitHub Annotation Toolkit. The CLI file gives screen reader users a way to print pull request data one item per line, and the toolkit file openly says it has never been checked with only a keyboard or with a screen reader.
What it means for developers
For maintainers, this is a cheap way to cut repeated questions. Users who rely on screen readers or keyboard navigation can see right away what works, what does not, and where to report a problem. That saves both sides time compared with a vague issue thread.
My practical advice is to start small and honest. List the environments you have really tested, name the gaps you already know, and describe a reporting path you can keep up with. A short, accurate file is far better than a long policy page that nobody maintains.
The contributor section deserves attention as more pull requests come from AI coding agents. Stating which accessibility checks a change must pass gives both humans and agents a clear rule to follow. If you already use automation such as GitHub Actions workflow lockfiles to tighten repository hygiene, an accessibility statement fits naturally into the same set of project files.
How to add a statement
There are two simple routes, both described in GitHub's documentation:
- From Community Standards: open the repository, go to Insights, choose Community Standards, find Accessibility and click Add or Propose. Fill in the template and commit, ideally through a new branch and pull request.
- Manually: use Add file, then Create new file, and name it ACCESSIBILITY.md, .github/ACCESSIBILITY.md or docs/ACCESSIBILITY.md.
- Organization-wide: place the file in the organization's .github repository so projects without their own copy inherit it.
For a fuller model, GitHub recommends the Open Source Accessibility Toolkit, while the built-in template offers a shorter starting point.
Conclusion
GitHub has turned ACCESSIBILITY.md into a first-class community health file, showing it as a repository tab, letting organizations set a default and adding an accessibility label to new repositories. It costs maintainers a few minutes to set up, and it gives users a clear, findable path for reporting barriers.
Sources
- GitHub Blog: Accessibility statements now have a home on GitHub
- GitHub Docs: Adding an accessibility page to your repository
See my articles more often when you search Google.
