Accessibility options for end-users with impairments
Jacques Reulet
Use standards like WCAG 2.0 or VPAT to enable greater usability for users with disabilities and allow Canny to be used under ADA guidelines.
H
Helpful Galliform
I agree with Ian. Canny handles quite well with a screen reader, but has some small issues that create heavy friction for blind or visually impaired users.
The sign-up modal is not announced, but can be found at the bottom of the HTML hierarchy. Once we get to it though, some of the buttons have a non descriptive label (such as "F" for Facebook or "G" for Github).
This is one of many theoretically very simple-to-correct issues but can unfortunately exclude a significant chunk of the population (1-2%) from using your wonderful product.
Allowing users with impairments to more easily use your product might also create a positive feedback loop, where you will get more and more feedback concerning accessibility and be able to improve not only your product but all products that use Canny as their feedback tool !
S
Safe Deer
Voting for this. As of now I can't use Canny in my products because it does not pass our accessibility checks. For example, when I use macOS Voice Over to try to leave feedback, the "Sign in to Canny" modal pops up but is never announced to the user. And I'm unable to navigate to the modal via Voice Over. This seems like a total dead end for a vision-impaired user.
Jacques Reulet
Merged in a post:
Make the product WCAG 2.0 conformant at the AA level
C
Casual Horse