search

FreedomScientific / standards-support

Contains documentation for Vispero software support of Web standards
https://freedomscientific.github.io/standards-support/
GNU General Public License v3.0
105 stars 11 forks source link

Aria-selected is not narrated for the single-select listbox, when selection is NOT moved with focus #440

Open kolaps33 opened 3 years ago

kolaps33 commented 3 years ago

Summary

  1. Go to https://codesandbox.io/s/m5fjl?module=/example.js
  2. Navigate through the selectable list

Expected result

JAWS should announce information about aria-selected state

Actual result

JAWS doesn't announce information about aria-selected

Additional Information

Background about example: When we implemented selectable 'listbox' example we consider Down Arrow: Moves focus to the next option. Optionally, in a single-select listbox, selection may also move with focus. Up Arrow: Moves focus to the previous option. Optionally, in a single-select listbox, selection may also move with focus. from aria https://www.w3.org/TR/wai-aria-practices-1.2/#listbox_kbd_interaction

It means that we don't move selection with focus. But user need to press space to do selection.

Comment

When I tried the same example with Firefox then JAWS was narrating:

Irving Kuhic 7:26:56 AM Program the sensor to the SAS alarm through the haptic SQL card! selected 1 of 3

Does it mean that JAWS is getting maybe accessibility tree from chromium without the information about aria-selected state?

JAWS version and build number

2020.20006.12 ILM

Operating System and version

Win 10 Enterprise 10.0.19041 Build 19041

Browser and version:

Chrome Version 85.0.4183.83 (Official Build) (64-bit)

JAWS-test commented 3 years ago

Does it mean that JAWS is getting maybe accessibility tree from chromium without the information about aria-selected state?

No, Chrome transmits aria-selected correctly. See the Accessibility tab in the developer tools (F12)

JAWS-test commented 3 years ago

See: https://github.com/w3c/aria-practices/issues/1513

frex65 commented 3 years ago

Bug confirmed using JAWS 2020.2008.24 and Chrome 85.0.4183.121. If the JAWS "List item say" is set to "Selected" or "Both", the option with focus is reported as selected, even if a different option is selected.

Wildebrew commented 3 years ago

This is still a problem with Chrome and Edge (latest browser versions with newest version of Jaws 2020))

To reproduce

  1. Visit the APG 1.2 rearrangeable listbox example
  2. Open the "Available Upgrades" listbox in example 2 (it is multi-selectable).

Chrome

Grade: B-

Action: Press spacebar to select or de-select an option in the listbox

Navigating through the listbox options with arrow keys

Edge:

Grade: B-

Exactly like Chrome with one exception. If you navigate to a selected option with the arrow keys and press spacebar, Jaws announces "not selected", I cannot trigger any other state change announcement.

Firefox

Grade: B+

Action: Press spacebar to select or de-select an option

Navigating through the listbox options with arrow keys

While a bit odd at first, this is acceptable.

smhigley commented 2 years ago

The results I'm currently getting are even worse than in the above comment -- JAWS isn't saying either "selected" or "not selected" when navigating through options in a single-select listbox when selection does not follow focus, using this example: https://jsfiddle.net/8w2arykb/show (note: that example doesn't include interactivity and only shows the base semantics, though the issue also does repro in a fully functioning listbox).

This reproduces with JAWS 2022, tested in these browsers: