Links
Baseline and accessibility
Currently, the Baseline support information does not include whether the feature is supported accessibly:
If you need to understand whether browsers support accessibility features as your own base level set of requirements, for legal or other compliance reasons, then Web Platform Baseline does not represent a baseline.
(From: Baseline Does Not Really Cover Baseline Support — Adrian Roselli)
I support Adrian's call for this to change. We should't assume features to be supported, if there are known accessibility issues in specific browsers or assistive technologies. I previously noted I feel Interop should include accessibility (and there is a separate Interop project for accessibility now, nice). I hope Baseline can meaningfully implement updates to make accessibility support more clear. A disclaimer, as Adrian suggested seems a good first step.
What would that it mean to deem a feature supported accessibly? WCAG's accessibility supported definition is a good start, but the W3C or Accessibility Guidelines Working Group (that makes WCAG) don't say exactly which browsers or assistive technologies a feature needs to work. For users of assistive technologies, ‘it works’ depends both their choice of assistive technology and the browser they use it with. But even if there's no clear cut answer to ‘which browsers or AT’, even the information that there are known bugs and where would tremendously help web developers decide whether to use a feature or not.