Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How would screen reader users use spatial navigation? #223

Closed
Malvoz opened this issue Feb 1, 2021 · 3 comments
Closed

How would screen reader users use spatial navigation? #223

Malvoz opened this issue Feb 1, 2021 · 3 comments

Comments

@Malvoz
Copy link
Contributor

Malvoz commented Feb 1, 2021

In browse mode (which I believe is default in all/most screen readers, at least in NVDA) the arrow keys are used to read text in a certain direction. I don't know if the typical screen reader user knows how and when to switch between the different modes but it's currently not possible to navigate the demo pages using the arrow keys in browse mode.

Of course, a screen reader user may not even need to navigate documents this way...

@jihyerish
Copy link
Collaborator

You can switch the keys instead of arrow keys using window.navigate() API for spatial navigation.
The corresponding demo is :
https://wicg.github.io/spatial-navigation/demo/#navigate

@Malvoz
Copy link
Contributor Author

Malvoz commented Feb 1, 2021

Okay, to try to make a long story short, the Maps for HTML Community Group's goal is more or less: declarative maps for the web, and I think we're envisioning panning to be controlled using arrow keys. The current situation in popular web map tools is that none of them are pannable without switching from browse mode, which I think is problematic (how do users know to switch mode?). But I suppose because arrow keys (with potential modifier keys) for standard per-element panning (and spatial navigation) would be UA-defined there'd be no need for switching keys using window.navigate() to enable these types of navigation (without switching from browse mode) as screen readers would have predefined and configurable modifiers. Although it'd be nice if the default didn't require modifier keys as I think arrow keys alone is more intuitive, but reading w3c/csswg-drafts#5683 I learned that specs can't put such requirements on browser interfaces.

Thanks @jihyerish.

@Malvoz Malvoz closed this as completed Feb 1, 2021
@jihyerish
Copy link
Collaborator

jihyerish commented Feb 2, 2021

@Malvoz yes, I aware of Maps for HTML Community Group and tried to combine the concept of it with Spatial navigation.
But I came up with the conclusion that the final goals of them are quite different. (The main use cases of the spec are different).
Thank you for your interest and input! It was interesting for me to look at the progress on Maps for HTML thanks to you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants