Screen reader accessibility

[ljordan51]

1. The map is incredibly hard to navigate using Android TalkBack screen reader. Also it doesn't appear that the little wind indicators can be clicked on when in TalkBack mode.
2. The nav bar just reads all the links as if they are one block of text when the drawer is first opened.
3. The graph is not accessible because it uses CanvasJS which coverts all the graph text to pixels before drawing.
4. The ReactJS "Link" elements aren't recognized by the TalkBack screen reader when navigating by links.

[anushadatar]

This is a good start for sure, but if we want to move towards rolling this out we should probably figure out how to build in screen reader accessibility, even if the outcome is simple, as this report at least indicates that there is no way to get information using the screen reader.

[ljordan51]

When you say "this report" what does that refer to? At least when I used the Android TalkBack screen reader on my Tmobile REVVL2+ it worked for a lot of the content on the original ("V0") Android build and web deployment.

[anushadatar]

Oh wow, I totally misread what this issue was saying! That's great to know. I'll try out our new at-a-glance display with my phone. Thanks.