-
Notifications
You must be signed in to change notification settings - Fork 12
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
The website should be accessible #21
Comments
The hide/show buttons may or may not be accessible. If we have to make all the buttons distinct then they certainly are not. |
@ToddTurnbull Do you happen to know if there's an easy way to make the roads less prominent in the open street base map? I was talking to a colour blind colleague the other day, and apparently it's difficult to tell what's a boundary and what's a road. Maybe shading would help? You can run things through this to see: https://www.toptal.com/designers/colorfilter/ |
It is possible to fiddle with opacity and stroke width parameters on the geoJSON. You can make the underlying map less prominent, but if you go too far then we lose the advantage of the underlying map. You can compare the maps at https://waterlooregionvotes.org vs https://pnijjar.github.io/WRvotes to see what I am talking about. The thicker the lines the dumber they look when zoomed out, but maybe the better they look zoomed in. I also made the opacity of the polygons 0.5, which washes out the underlying map quite a bit. |
As far as I know the clickable map is not terribly accessible to the blind. We should figure out how to make things convenient for most voters and accessible to those who have disabilities.
The text was updated successfully, but these errors were encountered: