-
Notifications
You must be signed in to change notification settings - Fork 9
Issues: Maps4HTML/experiments
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
User lost sight of the keyboard focus very often
Dragon Naturally Speaking User Testing
Version number: Dragon 15.71 pro corporate French
Inconsistencies experienced with "Show links" command on "Keyboard shortcuts" link
Dragon Naturally Speaking User Testing
Version number: Dragon 15.71 pro corporate French
Inability to copy-paste restaurant information
Dragon Naturally Speaking User Testing
Version number: Dragon 15.71 pro corporate French
Confusion about using arrow keys
Dragon Naturally Speaking User Testing
Version number: Dragon 15.71 pro corporate French
Inability to open the restaurant button once “Show links” command is used
Dragon Naturally Speaking User Testing
Version number: Dragon 15.71 pro corporate French
Lack of search field
Dragon Naturally Speaking User Testing
Version number: Dragon 15.71 pro corporate French
Lack of feedback from arrow keys during map navigation
JAWS User Testing
Version Number: 2024.2312.99
Confusing location of keyboard shortcuts (in map attributions)
JAWS User Testing
Version Number: 2024.2312.99
Discrepancy in number of expandable restaurant information buttons for screen reader users
JAWS User Testing
Version Number: 2024.2312.99
Ambiguous link purpose for "Zoom to here" in restaurant information
JAWS User Testing
Version Number: 2024.2312.99
Would have preferred <details> and <summary> usage for the buttons to expand restaurant information
JAWS User Testing
Version Number: 2024.2312.99
The tables that contain specific information of the restaurants mistakenly display itemprop values as visible text
WCAG 2.4.6
An issue that is a failure under the WCAG “2.4.6 Headings and Labels” criterion
The <div> element containing the scale information has an aria-label but it does not have a role
WCAG 4.1.2
Issues that are failures under the WCAG “4.1.2 Name, Role, Value” criterion
The info button at the bottom right has no accessible name.
WCAG 4.1.2
Issues that are failures under the WCAG “4.1.2 Name, Role, Value” criterion
Map can be panned in both dimensions within its screen using arrow keys, but screen readers do not announce anything while doing so
WCAG 4.1.2
Issues that are failures under the WCAG “4.1.2 Name, Role, Value” criterion
For each example, allow the user to see and copy the markup that creates it
#33
opened Apr 28, 2021 by
prushforth
ProTip!
Exclude everything labeled
bug
with -label:bug.