Improve map sheet UX for VoiceOver users #576
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Oops, didn't mean to merge #575 yet, shouldve marked it as a draft.
Beta feedback on #575, summarized:
When the sheet is fully expanded, the prompt is confusing for Voiceover users, since the map is now inaccessible for Voiceover (see screenshot). Additionally, the map should not be disabled for all voiceover users, since low-vision users are still able to interact with the map visually.
Stuff to do:
[ ] Add a button to recent stops list to "expand" the search radius if no stops were loaded (viaremoved from this PR, see Add a button to recent stops list to "expand" the search radius if no stops were loaded #578perferredLoadDataRegionFudgeFactor
from commit ae73f03)