Open lidel opened 6 years ago
We want to include automated a11y testing from the start of the web-ui rebuild project. https://github.com/pa11y/pa11y looks worth testing out.
Another engine for automated Web UI testing: https://github.com/dequelabs/axe-core#axe-core
react storybook with the a11y info could be good combo https://github.com/storybooks/storybook/tree/master/addons/a11y
Linking to (closed) issue https://github.com/ipfs-shipyard/ipfs-webui/issues/756 for an existing discussion around keyboard navigation and thoughts for next steps.
Also linking to (closed) issue https://github.com/ipfs-shipyard/ipfs-webui/issues/1350 for a user-provided specific suggestion for keyboard nav in breadcrumbs.
Excellent reference on color palette process here: https://stripe.com/blog/accessible-color-systems
ipfs-webui getting a11y treatment and automated checks in https://github.com/ipfs-shipyard/ipfs-webui/pull/1512 :rocket:
https://github.com/ipfs-shipyard/ipfs-webui/issues/1631#issuecomment-699103157 references contrast issues in Files screen checkbox and browse box button/backkground.
Edit: April 2020
Placeholder issue for reviewing and acting on accessibility overall for Desktop, Companion, and WebUI. Suggest that we dig into this mid-2020 once we've got an additional round of issues for the apps overall knocked out. Please see specific issues that have been closed in favor of this meta-issue:
Original issue specs
This is a placeholder issue for coming up with a strategy to tackle accessibility in our apps and documentation
Tasks
References / Reading Material