Adam Reineke
Adam Reineke
FYI, I hit this issue on IdeaExchange and this was the solution we adopted.
There are probably way more accessibility violations than just that. (Creating new panels, etc.)
This is probably a good first issue. Do `npm run demo` and then run aXe on the page. It should repro this issue.
The demo page has two violations and three issues regarding best practices. We should probably make the whole page accessible but will be a little extra work.
@peterjgrainger Yeah, go for it!
 27 08 2018 19:41:17.017:WARN [launcher]: Chrome have not captured in 60000 ms, killing. 27 08 2018 19:41:17.237:INFO [launcher]: Trying to start Chrome again (1/2). 27 08 2018 19:42:17.238:WARN [launcher]:...