kellyhutchins / a11y-map Goto Github PK

Limit map navigation to the area where results are located. As a temporary 'fix' I added a listener for the 'h' key that moves the map back to the initial loading location when pressed.

Steps to reproduce:

• go to /a11y-map/index.html
• navigate area to pop-up
• open pop-up
• press 'esc'

Expected Behavior:

• should close the pop-up

Supporting Info:

• Google Chrome Version 68.0.3440.106
• OS X High Sierra
• localhost..././a11y-map/index.html

Test each of these issues

• Number needs to be pressed at least twice before the info about that number is displayed
• As numbers appear the screen reader starts reading. If there are a large number the screen reader reads the list at least twice each tie assigning a different number to the landmarks. Only the number assigned after the last reading is correct and leads to the correct description.
• It seems as though you can go to the next and previous points after you select one, but I am not clear on what keystrokes you need to press to do this. After a point is described I do not hear references to next, previous and menu
• In order to move on the map the arrow keys are pressed repeatedly which interrupts the screen reader quite often, causing the user to possibly miss important announcements. Mainly whether there is a point on the map that may have more information. It would be useful if the computer can emit a tone to indicate that points of interest popped up on the map?

Steps to reproduce:

• go to /a11y-map/index.html
• navigate with keyboard to area without pop-ups

Expected result:

• press [INSERT KEY HERE] to move window to nearest data point
• movements should be read into the live region to give user context on where they are being moved
• finished with end result read into live region

Context:
In current format, a user with a visual impairment may be unable to navigate to an initial datapoint

Expected Behavior:
Legend should be active and displayed on map open.

Context:
For users with visual impairments, a legend provides a meaningful way to navigate data outside of using the map. Also when legend information is ordered or sorted by the data it is portraying (ex. regions ordered by population density), it provides clearer context to the significance of the data and the relationship between data points.

Steps to reproduce:

• go to /a11y-map/index.html
• navigate with keyboard to area with pop-ups
• enter a pop-up

Expected result:

• press [INSERT KEY HERE] to transfer to next data point (potentially ordered by legend?)
• current pop-up is closed and map moves to new point
• New pop-up is opened and read into live region
• Add feature to read current map position on close of pop-ups

Context:
In current format, a user with a visual impairment may be unable to navigate between data points in a orderly format, or unable to visit all data points without context of where they are.

Steps to reproduce:

• go to /a11y-map/index.html
• navigate with keyboard to area over pop-ups
  • I went 7 arrows west, then 5 arrows south from the starting position to sit over a region of three pop-ups
• turn on VoiceOver for OS X (cmd-f5)
• try to rapidly travel east with keyboard (right arrow)

Expected result:

• Travels east

Context:
Initial assumption is that the ARIA Live Region is taking priority over the JS to move the map east and west. This doesn't happen with north and south though.

Supporting Info:

• Google Chrome Version 68.0.3440.106
• OS X High Sierra
• localhost..././a11y-map/index.html

Work on aria live settings so both nav info and feature info is spoken.

We need to check if the demo app and its pattern work on mobile devices. I will report any findings here.