GitHub teaches screen readers to read issue and PR timelines as lists

GitHub has updated the interface for issue and pull request timelines, making them significantly more accessible for screen reader users and other assistive technology users. The work improves the experience for developers with visual impairments and helps them work with projects on the platform at the same speed and comfort as everyone else.

How the new interface works

Screen readers can now navigate timelines like standard HTML lists. As users move through events on the timeline, the assistive technology announces the list structure, the number of events, the user's current position, and the available navigation commands. This makes working with a long change history far more intuitive.

Previously, screen readers treated timelines as simple unstructured content, with no information about the size of the history or the user's position within it. Users had to "scroll" through content without a clear sense of its structure. The new approach solves this problem by providing full navigation context and letting users jump quickly to relevant events without scanning the entire history.

Loading new events has been improved

When a user clicks the "Load more" or "Load all" button to load additional events, the screen reader now announces the exact number of new events that were loaded. For example, it might announce "11 new items loaded" after the focus moves to the newest event. Previously, new events loaded without any announcement, which could cause confusion about whether loading had actually occurred and how many items had been added.

Scope of the update

The update works on timelines for the following item types:

• Issue — tasks and bugs in projects • Pull request — code merge requests • Commit — commits with change history • Secret scanning alert — alerts about detected secrets • License compliance alert — license compliance alerts

The update is available both on the main github.com site and on GitHub Enterprise Server version 3.23 and above, covering both public and enterprise platform users.

How to test it

Developers can check out the new capabilities by opening any issue or pull request with a long history and navigating through the timeline using one of the popular screen readers:

• VoiceOver — built into macOS and iOS • NVDA — a free screen reader for Windows • JAWS — a commercial screen reader for Windows

The screen reader will announce the timeline as a structured list, indicating the number of items and the position, allowing quick orientation within the history without visually scanning the screen.

Significance for accessibility

The update doesn't change the visual appearance of timelines for most users. However, it significantly improves HTML semantics and compatibility with assistive technologies. Such changes are critical for building truly inclusive applications, where users with disabilities can work just as efficiently as other developers. GitHub also provides a detailed guide on using screen readers when working with issues for all interested users.