Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A11Y: Improve navigation on topic lists for screen readers #13153

Merged
merged 1 commit into from May 26, 2021

Conversation

SamSaffron
Copy link
Member

Previously we had no role set for various topic links, nor did we have any
headers.

This teaches screen readers that topic links in topic lists are to be treated
as H2. We opted for this less radical change cause a change of the element
type would probably result in many broken themes.

Confirmed on NVDA you can very quickly breeze through topic lists now. Minor
edge case is pinned topics which can be a bit annoying due to multiple links.

Previously we had no role set for various topic links, nor did we have any
headers.

This teaches screen readers that topic links in topic lists are to be treated
as H2. We opted for this less radical change cause a change of the element
type would probably result in many broken themes.

Confirmed on NVDA you can very quickly breeze through topic lists now. Minor
edge case is pinned topics which can be a bit annoying due to multiple links.
@discoursebot
Copy link

This pull request has been mentioned on Discourse Meta. There might be relevant details there:

https://meta.discourse.org/t/discourse-with-a-screen-reader/178105/47

@awesomerobot awesomerobot changed the title UX: Improve navigation on topic lists for screen readers A11Y: Improve navigation on topic lists for screen readers May 26, 2021
@SamSaffron SamSaffron merged commit 759abb3 into master May 26, 2021
@SamSaffron SamSaffron deleted the add-role-heading-to-topic-list branch May 26, 2021 02:53
nlalonde pushed a commit that referenced this pull request Jun 4, 2021
Previously we had no role set for various topic links, nor did we have any
headers.

This teaches screen readers that topic links in topic lists are to be treated
as H2. We opted for this less radical change cause a change of the element
type would probably result in many broken themes.

Confirmed on NVDA you can very quickly breeze through topic lists now. Minor
edge case is pinned topics which can be a bit annoying due to multiple links.
@oblakeerickson oblakeerickson mentioned this pull request Jun 13, 2022
@xfalcox xfalcox mentioned this pull request Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants