Apple Feedback: posinset assertion in test 12 "Open a menu" (Action Menu Button Example Using aria-activedescendant, V22.03.17)

[cookiecrook]

Description of Behavior

From the test expectations:

MUST Name of the focused item, 'Action 1', is conveyed Failed
MUST Position of the focused item in the menu (1) is conveyed Failed

I agree that the first is a bug...

However, I don't understand the second failure...

"Position of the focused item in the menu (1) is conveyed"

Are you expecting the numeral 1 to be spoken even though it does not occur in the visible UI? If so, what behavioral "MUST" requirement is this test referencing?

Note that this same invalid expectation appears in several tests on this page... All seem to be invalid expectations. I recommend removing them. Thanks.

Test Setup

• Test File: test-12-open-menu-interaction-voiceover_macos.collected.html
• Report Page: Link
• AT: VoiceOver for macOS (Version 13.5)
• Browser: Safari (Version 16.6.0)

[mcking65]

@cookiecrook wrote:

From the test expectations:

MUST Name of the focused item, 'Action 1', is conveyed Failed
MUST Position of the focused item in the menu (1) is conveyed Failed

I agree that the first is a bug...

However, I don't understand the second failure...

"Position of the focused item in the menu (1) is conveyed"

Are you expecting the numeral 1 to be spoken even though it does not occur in the visible UI? If so, what behavioral "MUST" requirement is this test referencing?

That assertion is related to conveying the value of aria-posinset. In the new version of this test plan that it is being written now, it will be changed from a "MUST" to a "SHOULD".

[cookiecrook]

@mcking65 wrote:

That assertion is related to conveying the value of aria-posinset. In the new version of this test plan that it is being written now, it will be changed from a "MUST" to a "SHOULD".

I would disagree with this change too. ariaPosInSet is relevant to convey to the screen reader programmatically, in situations where the order differs from the DOM or the set in the DOM is incomplete... It's not a requirement (MUST or SHOULD) that the SR convey that numeric value to the user unless either 1) the numeric value is rendered on-screen, or 2) the SR defaults would normally convey this value in a similar non-web context... The only requirement is that the navigation remains in authored order.