Skip to content
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

Accessability Issues when Pulling Dynamic Map #8972

Open
10 tasks
GabeGabeT opened this issue Oct 29, 2020 · 1 comment
Open
10 tasks

Accessability Issues when Pulling Dynamic Map #8972

GabeGabeT opened this issue Oct 29, 2020 · 1 comment

Comments

@GabeGabeT
Copy link

GabeGabeT commented Oct 29, 2020

We are one of the Application Development teams at Agriculture and Agri-Food Canada. A few months ago we found your GeoGratis API for dynamic maps and we made use of this API in one of our web applications at Agriculture and Agri-Food Canada. As our application will have external users, it needs to comply with the Web Content Accessibility Guidelines (WCAG) before going live. During the testing cycle of our app for WCAG, we noticed that GeoGratis is failing in a few WCAG areas.

Please find attached a document with a list of WCAG issues that we encountered. Would you kindly inform us of your future release plans that can potentially resolve some or all of these issues? We would be glad to provide you with a link to our application or code for further verification.

DynamicMapIssues.xlsx


(Extracted from the attached spreadsheet)

  • SC 4.1.2 - Name, Role ,Value - Zoom to element buttons in the table
  • SC 4.1.2 - Name, Role ,Value - Using aria-label to provide an invisible label where a visible label cannot be used
  • SC 3.3.2 - Labels or Instructions - The checkboxes in the table
  • SC 3.3.2 - Labels or Instructions - The visually hidden <th> for the checkboxes and the zoom buttons
  • SC 3.3.2 - Labels or Instructions - Positioning labels to maximize predictability of relationships
  • SC 2.4.4 - Link Purpose (G91) - Providing link text that describes the purpose of a link
  • SC 2.4.4 - Link Purpose (G59) - Placing the interactive elements in an order that follows sequences and relationships within the content
  • SC 2.1.1 - Keyboard (G202) - Dismiss button for the Help information on the map
  • SC 3.1.2 - Language of Parts (H58) - Using language attributes to identify changes in the human language
  • SC 2.4.3 - Focus Order - Correcting order on the map for tabbibg

@szet0018

@duboisp
Copy link
Member

duboisp commented Nov 23, 2020

Thanks @GabeGabeT

Is those issue are also noticeable from the geomap working example here: https://wet-boew.github.io/wet-boew/demos/geomap/geomap-en.html

We will need to find a resource in order to fix those issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants