GitHub adds repository-level ACCESSIBILITY.md statements to make project guidance easier to find

GitHub now displays an ACCESSIBILITY.md file on repository overview pages when it is stored in the root, .github/, or docs/ directory, and repositories can inherit one from an organization. Public-repository maintainers can use a starter document in Community Standards, while new repositories also get an accessibility issue label. The statements can document reporting routes, supported environments, known barriers, workarounds, and contributor expectations; naming a WCAG target alone does not prove conformance.

For maintainers, a visible statement can reduce the effort users face when reporting barriers and give contributors concrete accessibility expectations. The trade-off is ongoing upkeep: projects should publish only practices and response commitments they can sustain, and the article does not say GitHub verifies the accuracy or completeness of these statements.