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

Text instructions for keyboard shortcuts and the query reticule #267

Closed
prushforth opened this issue Jan 28, 2021 · 4 comments · Fixed by #683
Closed

Text instructions for keyboard shortcuts and the query reticule #267

prushforth opened this issue Jan 28, 2021 · 4 comments · Fixed by #683
Labels
accessibility i18n Internationalization and localization

Comments

@prushforth
Copy link
Member

No description provided.

@Malvoz
Copy link
Member

Malvoz commented Feb 2, 2021

By "text instructions" do you mean instructions for how to operate it (keyboard shortcuts)?

@prushforth
Copy link
Member Author

Yes, maybe it needs them just as the a11y map and Google Maps do when the focus area is visible?

@Malvoz Malvoz added the i18n Internationalization and localization label Aug 5, 2021
@Malvoz Malvoz changed the title Should the query reticule have text instructions for accessibility reasons Text instructions for keyboard shortcuts and the query reticule Nov 24, 2021
@Malvoz
Copy link
Member

Malvoz commented Nov 24, 2021

I've renamed this issue to include text instructions for keyboard shortcuts in general as well.

Since last year when we reported accessibility issues in Google Maps at the time of the W3C/OGC Maps for the Web workshop they've made a ton of improvements (related blog post), including a new "keyboard shortcuts" button placed next to the attribution links:

which opens up a dialog with text instructions:

A dialog like this could hold instructions for keyboard shortcuts such as pan, zoom, context menu, and the query reticule.

@prushforth
Copy link
Member Author

It's great, your advocacy has had an impact on Google Maps too, by the looks of it. It would be greater if they all came over here and helped us improve our proposal. Not that you can do anything about that, mind you. I guess I'm happy to try to implement accessibility improvements to the polyfill as we can, including this one.

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

Successfully merging a pull request may close this issue.

2 participants