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

Use case: User-controlled pan & zoom #39

Open
AmeliaBR opened this issue May 27, 2019 · 2 comments
Open

Use case: User-controlled pan & zoom #39

AmeliaBR opened this issue May 27, 2019 · 2 comments
Labels
discussion: use case a possible use case: should it be included? what should it say? status: editor's draft there's a draft section in the report that corresponds to this discussion

Comments

@AmeliaBR
Copy link
Member

@AmeliaBR AmeliaBR commented May 27, 2019

This issue is for discussion of the use case “Reposition or scale a map to find more context for the displayed locations”, its examples & list of required capabilities.

This is the most basic user-focused use case: the website author has displayed a map of a certain area, but the user wants to pan or zoom.

I am including in the same use case all the accessibility requirements. I think it's important that we don't talk about "panning and zooming with the keyboard" as a separate feature/requirement from "panning and zooming with the mouse (or touch gestures)". One should never be implemented without the other.

@AmeliaBR AmeliaBR added discussion: use case a possible use case: should it be included? what should it say? status: editor's draft there's a draft section in the report that corresponds to this discussion section: map viewer Capabilities & use cases for declarative map viewer widgets labels May 27, 2019
@bkardell
Copy link

@bkardell bkardell commented Jun 2, 2019

FWIW This seems at least somewhat spiritually related to:

@cmhodgson
Copy link

@cmhodgson cmhodgson commented Jun 3, 2019

Spatial navigation and other focus-related issues are certainly relevant to accessible map controls, but we have to be careful about the word "spatial" as its use in spatnav is relative to the HTML page layout, whereas its use in terms of MapML is more likely relative to a geographic location. (I'm sure we are all aware of this but it does need to be clear)

@AmeliaBR AmeliaBR removed the section: map viewer Capabilities & use cases for declarative map viewer widgets label Jul 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion: use case a possible use case: should it be included? what should it say? status: editor's draft there's a draft section in the report that corresponds to this discussion
Projects
None yet
Development

No branches or pull requests

3 participants