Gaël Poupard
Gaël Poupard
Learn from [IDPDF's accessibility guidelines](https://idpf.github.io/a11y-guidelines/) to see which tests are doable with CSS Thanks to @JayPanoz for the idea.
Following [WAI-ARIA Authoring Practices](https://www.w3.org/TR/wai-aria-practices/), we can create tons of selectors to test what's testable :) eg: ``` [role="alertdialog"]:not([aria-label]):not([aria-labelledby]) { } ``` but since it would be pretty heavy — and...
Wouldn't it be valuable? This would help us see if any useful content is missing when disabling backgrounds…
Check [longdesc.fr](http://longdesc.fr/) if any a11y.css' test could be improved or added!
* check for focus visibility * check some aria-pattern based on focus
Simply check: - [ ] properties and values support in [Can I Use?](https://caniuse.com) - [ ] current version support with real devices or something like [BrowserStack](https://browserstack.com) - [ ] then...
[Chartability](https://chartability.fizz.studio/) is a kind of WCAG 2.1 extension dedicated to data visualization. From the site: > Chartability is a methodology for ensuring that data visualizations, systems, and interfaces are accessible....
Because you know, test is better than think.
There're tons of things to explain and link in `charts.scss` main file, a shame it's not documented yet!
axe-linter doesn't do that much; the oldish axe-webdriver is way too heavy to run in CI for each push… So what now? Maybe pa11y-ci, like in Bootstrap?