Discover · github.blog

Accessibility statements now have a home on GitHub

Git.io github.blog

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.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

In the piece

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Also from Git.io

  1. Maintainers don’t need more AI bug reports. They need fixes. Ashley Wolf github.blog
  2. Building the Agent Host Protocol for sessions that continue across devicesConnor Peet github.blog
  3. GitHub availability report: October 2026Jakub Oleksy github.blog
  4. Build once, run on any agent: A practical guide to agent skillsAndrea Griffiths github.blog
  5. Git security vulnerabilities announcedElijah Newren github.blog
  6. Beyond code generation: A developer’s guide to agentic engineeringNick Liffen github.blog