Accessibility statements now have a home on GitHub

Accessibility work often lives in issue trackers, contribution guidelines, audit reports, team knowledge, and conversations with users. When that information has no predictable home, people who encounter a barrier must search for it, and maintainers lose context as contributors and project ownership change.

An ACCESSIBILITY.md file, now visible on repository overview pages, gives a project one durable place to explain its accessibility goals, contributor expectations, supported environments, known limitations, and process for reporting barriers.

GitHub makes accessibility statements easier to find

GitHub now recognizes the ACCESSIBILITY.md file in the repository’s root,.github/ directory, or docs/ directory. A repository can also inherit a statement from its organization’s.github/ repository. For public repositories, maintainers can add or propose a statement from Insights > Community Standards using a concise starter document.

GitHub’s community health files help people understand how a project works:

Contribution guidelines explain how to propose changes

Codes of conduct establish expectations for participation

Security policies explain how to report vulnerabilities

Recognizing ACCESSIBILITY.md …