FAQ: GitHub accessibility tips / navigating with NVDA

[seanbudd]

GitHub isn't the easiest website to learn how to use with a screenreader, and many particular aspects are not intuitive.
This thread intends to serve as place for tips, discussions and questions on how to use GitHub with NVDA.

This post will be kept up to date as an FAQ on using GitHub with NVDA.

Finding/responding to pull request review comments

It can be challenging to view all pull request comments, as GitHub hides them by default on long discussions.
To ensure you respond to all review feedback, do the following:

1. Use browse-mode search for "hidden" and press the button labelled "show hidden comments" (or similar).
2. Do this repeatedly until NVDA can't find any more such buttons.
3. Then search for "resolve" to find the button to resolve each conversation.
4. Then use shift+h to navigate backward by heading to the start of the thread, read it, and decide what action to take.

[jacob-kruger-work]

Just tried out the new issue-input forms, and all seems good from my perspective - one advantage is that just tabbing from the issue title field drops you onto the links relating to content-guidelines, etc. as well before landing on the main content-input fields, since people need to still consider content-input-guidelines before they just post issues.

And, if relevant, was using brave/chromium browser here.

[Mister-Kayne]

I just tested the new issue template for NVDA on GitHub and had a great experience! I recall my first bug report where I didn't fill out the template correctly, but the community's guidance helped me get it right the second time. The new template is easy to navigate, with a clear structure and fields that are simple to fill out. Kudos to the team for making the process more user-friendly!