Quansight-Labs / czi-bokeh-mgmt

MIT License
2 stars 0 forks source link

Accessibility audit - Bokeh #5

Open trallard opened 4 months ago

trallard commented 4 months ago

📌 Summary

We will run a comprehensive accessibility audit of the libraries' systems, interfaces, and data visualizations against Web Content Accessibility Guidelines (WCAG), Authoring Tool Accessibility Guidelines (ATAG), and Chartability. By integrating these three sets of guidelines, we will adopt a systematic and robust approach to accessibility assessment for visual contrast, keyboard navigation, tool flexibility, authoring support, use of typefaces, cognitive barriers and overall usability.

The findings will create a concrete roadmap for further accessibility improvements within bokeh.

### 🔖 Tasks to complete
- [ ] https://github.com/Quansight-Labs/czi-bokeh-mgmt/issues/8
- [ ] https://github.com/Quansight-Labs/czi-bokeh-mgmt/issues/11
- [ ] Synthesise results and create a public roadmap for accessibility enhancements
- [ ] Solicit community feedback and input
frankelavsky commented 3 months ago

I'd love to kick this work off soon - so before I do:

trallard commented 3 months ago

Thanks for the ping @frankelavsky - I ended up being off sick last week.

Regarding previous accessibility work on Bokeh I don't believe there is any prior concerted effort but @pavithraes might be best at pointing you towards any docs. There are some issues and PRs that have some fixes or discussions about accessibility, but I think nothing major has been done until now.

For the scoping @mattpap is our in-house expert for BokehJS so I'd like to hear from him first regarding scoping/priorities on this end.

Note that we do include theming in the grant but I'd like to consider theming (colours and such) separately and focus on BokehJS components for the audit.

frankelavsky commented 3 months ago

Oh no! Well, I hope you're feeling better now!

So I guess my big question/questions for @mattpap is really just what scope and process we'd like to use. We can start with one representative thing (like an example app, dashboard, etc with a lot in it) and see how much we want to scale beyond that, we can start with a representative set of smaller things (individual widgets, plots, etc) that we know we want to tackle for sure, or another approach.

trallard commented 3 months ago

Noting I have not forgotten about this. So will share my thoughts/ideas on Monday so we have a start point (for discussion or else).

Have a lovely weekend.