Usage feedback from visually impaired IT specialist
- Dominant language
- TypeScript
- Stars
- 25
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Test each of these issues
- [x] 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?
See original at: https://github.com/kellyhutchins/a11y-map/issues/9
Contributor guide
Assessment
This issue has not been assessed yet.