When the user tabs into the table row set as "SelectionMode.none" with narrator, it announces the row as "(Row item) Not Selected". Since the row is not selectable, it should not say "Not selected".
https://codepen.io/Rafi_Mohammed/pen/zYYJLZW
In the codepen example above, narrator says: "Item 0, 0. Not selected."
In the codepen example above, narrator should say: "Item 0, 0."
@clmori I'm able to repro this but I think this is behaving as intended - it's simply reading out "Not selected" because that is the state of the element Narrator has focus on. I'm not aware of any way to get Narrator to say "Unselectable" or to override it's behavior and make it say "Not selected" when that is exactly what accurately describes the state of the element that currently has keyboard focus. If you do know of either things, I'd like to hear them and see what we can do to make it more clear but as of now, I think this is the best Narrator can do.
@smhigley thoughts on the intended behavior?
I agree with @aneeshack4, I don't see anything in the markup that indicates selectability, so this seems like an issue on Edge or Narrator (or hold off at least until Edge officially releases on Chromium).
Mapping things like selection patterns and edit patterns on the grid role are still getting ironed out (NVDA thinks all grid cells are editable unless the grid is explicitly marked readonly
, for example), so it doesn't entirely surprise me that Narrator/Edge would have a similar issue.
Thanks for looking into this!
Cool I'm going to close this issue then since it's external.
Most helpful comment
I agree with @aneeshack4, I don't see anything in the markup that indicates selectability, so this seems like an issue on Edge or Narrator (or hold off at least until Edge officially releases on Chromium).
Mapping things like selection patterns and edit patterns on the grid role are still getting ironed out (NVDA thinks all grid cells are editable unless the grid is explicitly marked
readonly
, for example), so it doesn't entirely surprise me that Narrator/Edge would have a similar issue.Thanks for looking into this!