1862999 - codepen.io - "aria-posinset" and "aria-setsize" not implemented correctly, VoiceOver unable to identify the options correctly

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect, P3)

Description

[Calin Tanase]

Note: The screen reader (VoiceOver) is unable to identify correctly the lines/options, more info on the github report

From github: https://github.com/webcompat/web-bugs/issues/129225.

<!-- @browser: Firefox 119.0 -->
<!-- @ua_header: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/119.0 -->
<!-- @reported_with: unknown -->

URL: https://codepen.io/michaelmherrera/pen/gOqwXjx

Browser / Version: Firefox 119.0
Operating System: Mac OS X 10.15
Tested Another Browser: Yes Chrome

Problem type: Something else
Description: Firefox ignores aria-posinset and aria-setsize
Steps to Reproduce:
I used a codepen because I couldn't find a use of aria-posinset in the wild.

What I noticed is that aria-posinset and aria-setsize do not appear in the accessibility tree for Firefox. In the codepen example, I simulate a 10-item list where only items 5-8 are currently in the dom. In Chrome, where aria-posinset and aria-setsize are properly implemented, the screen reader (VoiceOver) correctly identifies the first list item as "5 of 10" and the next as "6 of 10". On the other hand, in Firefox, the aria attributes are ignored, and the first item is identified as "1 or 4" and the second as "2 of 4".

Thus, if someone using a screen reader is interacting with a list that implements infinite scroll by loading and unloading list items in the DOM, they will be mislead about their position in their list.

View the screenshot

<img alt="Screenshot" src="https://webcompat.com/uploads/2023/11/ad211f12-77d7-4586-8c7b-90b6be673f98.jpg">

Browser Configuration

<ul>
<li>None</li>
</ul>

From webcompat.com with ❤️

Change performed by the Move to Bugzilla add-on.

Comment 1

[Eitan Isaacson [:eeejay]]

Thanks! This looks like a real issue. In the gecko accessibility layer it works as expected, but no in VO.

Comment 2

[michaelherrera595]

(In reply to Eitan Isaacson [:eeejay] from comment #1)

Thanks! This looks like a real issue. In the gecko accessibility layer it works as expected, but no in VO.

Thanks for the update! Given that the issue appears to be with VoiceOver and not Gecko, what do you expect to be the path forward? Essentially,

1. Would resolving this bug require modifications to Gecko?
2. Would resolving this bug require modifications to VoiceOver?

Thanks so much!

PS: I'm a Salesforce dev and encountered this issue while QAing the a11y of one of our features.

Comment 3

[Eitan Isaacson [:eeejay]]

The fix is in our mac platform compatibility layer. I hope to have this fixed this cycle, so you could expect to see this in release 121.

Comment 4

[Eitan Isaacson [:eeejay]]

Attachment: Bug 1862999 - Introduce support for AXARIAPosInSet and AXARIASetSize. r?morgan!

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/54f6a0fa6c5f
Introduce support for AXARIAPosInSet and AXARIASetSize. r=morgan

Comment 6

[Cristina Horotan [:chorotan]]

https://hg.mozilla.org/mozilla-central/rev/54f6a0fa6c5f