NickFitz opened this issue
Jun 14, 2019
· 2 comments
Labels
discussion: capabilitya specific capability or feature: should it be included? what details? should it be a requirement?section: client-side APICapabilities & use cases for client-side APIsstatus: placeholderthere's a matching section heading / some text in the report, but it's far from complete
I think changing the bearing of a map is an important capability, but it's also a potentially frustrating experience even for able bodied individuals, to keep the map oriented the way they like it. Sometimes I feel it would be better to disallow this feature, in the interest of accessibility. This is especially true of some globes I have used, but also applies to maps.
This capability is currently listed in the API side — can author scripts add features that change the map bearing? So the user-friendliness of it would be up to the website author.
However, it might be worth adding a similar capability to the widget side: does the default widget have features that allow the user to rotate and reset / lock the bearing?
discussion: capabilitya specific capability or feature: should it be included? what details? should it be a requirement?section: client-side APICapabilities & use cases for client-side APIsstatus: placeholderthere's a matching section heading / some text in the report, but it's far from complete
3 participants
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.
This issue is for discussion of the required API capability “Change the bearing of a map”.
The text was updated successfully, but these errors were encountered: