Issue: While VoiceOver can navigate to reply headings using quick navigation keys, the heading text does not clearly identify the purpose or content of each reply.
Specific Behavior:
● Headings announce profile names but lack context about reply content
● Users can find replies but cannot efficiently identify which reply contains relevant information
Why High: Makes discussion reading very difficult and confusing as users must visit each reply to determine relevance.
These issues were first reported in Screen Reader Accessibility issues .
Can you explain the expected behaviour here?
The user would be able to know which post is being replied too.
But how? What do you expect to hear? I’m not familiar at all with screenreaders, hence I’m asking.
When I turn on voiceover in safari, and Im on the reply button element, it says something like:
“Reply to post #2, by [username]”
For example, sighted folks would know which of the reply buttons to activate because of visual grouping. We need a way for a blind users (using a screen reader) to know for certain which reply button is associated with which post. Right now, people have to listen to them all.
Correction of this issue may be key: Issue 1: Broken Heading Navigation / DOM Manipulation
@adress is this using an element list style of navigation similar to what was mentioned in the other issue? in this case, the landmarks are difficult to distinguish from each other… here’s an example from VoiceOver
I think we should be able to provide labels for these
Yes, the is an issue with screen readers. Links, buttons, elements with the same repeated name are not useful. Thanks.
