Where the statement can live
GitHub now recognizes an ACCESSIBILITY.md file placed in the repository root, the .github/ directory, or the docs/ directory, and surfaces it on the repository overview page. A repository can also inherit a statement from its organization's .github/ repository. For public repositories, maintainers can add or propose one from Insights > Community Standards, which offers a concise starter document.
The new file sits alongside the other community health files that describe how a project operates: contribution guidelines, codes of conduct, and security policies. Accessibility information gets a dedicated place next to that guidance rather than being scattered across issue trackers, audit reports, and team knowledge. New repositories also ship with an accessibility issue label by default, so the reporting path described in the statement has a matching place to track the resulting work.
What real statements document

GitHub CLI's accessibility statement records settings, known barriers, and workarounds. It explains why table output can be hard to follow with a screen reader and gives a command that prints pull request numbers and titles one per line instead. Contributors who change prompts or output are asked to show the results with relevant accessibility settings enabled — a specific workaround for users, clear expectations for contributors.
The GitHub Annotation Toolkit's statement documents a limitation of its Figma library: annotations convey relationships through canvas position, connecting lines, and matching numbers, and access to individual canvas objects does not necessarily communicate those relationships. The recommended alternative is a structured text description identifying each annotated element, its intended semantics and behavior, and any relevant ordering. The file also explains how to report barriers and states plainly that the library has not undergone keyboard-only or screen-reader testing, so readers see both practical guidance and the limits of what has been verified.

Sections worth covering
No fixed format exists; a small library, a CLI tool, a documentation site, and a large web application differ in users, risks, and maintenance capacity. Start with information the project can keep current.
- Priorities and goals: why accessibility matters and which user experiences get attention.
- Contributor expectations: the checks, evidence, or review practices expected for changes, with instructions for both human contributors and coding agents.
- Reporting barriers: a direct, accessible path that does not require disability disclosure, screenshots, or recordings.
- Response process: how maintainers acknowledge, triage, track, and communicate about issues; if severity levels exist, let maintainers assign or confirm them during triage.
- Supported environments: platforms, browsers, input methods, and assistive technologies supported or tested.
- Known limitations: barriers described in terms of the affected experience, available workarounds, and links to tracked remediation.
- Ownership: the team, role, or maintainer responsible for keeping the statement and practices current.
- Feedback: how users and contributors can suggest changes to the statement or the practices.
A project may name a Web Content Accessibility Guidelines version and level as a target. A target is not verified conformance; a conformance claim requires an evaluation and should identify the evaluated scope, date, method, and evaluator.
Writing for the moment something breaks
The most useful statements serve people who arrive after a barrier has already been hit. Plain language, descriptive links, and a clear reporting route matter more than legal or standards-heavy wording. Good reporting guidance invites context — the affected task or page, observed behavior, browser, operating system, and assistive technology — while keeping screenshots and recordings optional. The statement should also promise only what maintainers can consistently deliver: acknowledgement, status updates, workarounds, expected timelines, and a chance for the reporter to verify a fix.
Adopt, then improve
The Open Source Accessibility Toolkit offers a detailed public example, while GitHub's Community Standards workflow provides a shorter starter whose prompts projects can replace. The goal is not a perfect policy before publication: start accurate, name the gaps, and update as practices mature.



