Consider adding an accessibility disclaimer to the Baseline badge about yari HOT 5 CLOSED

I don't think this is a good idea, for a number of reasons:

First, I reckon it'll fail to achieve what it sets out to do: people likely won't see this disclaimer, currently very few people actually open the Baseline banner: our metrics show between 2-3% of pageviews with a Baseline banner shown also have that Baseline banner toggled open.

Second, a11y support isn't the only non-goal of Baseline, do we add disclaimers for all those others in the banner as well? This will get rather overwhelming rather quickly, and fail on the aim of Baseline to be easily digestible.

Indeed, Baseline doesn't override general web development best practices: you should still test your code, regardless of what the compatibility data suggests. Perhaps some kind of "how to use Baseline" document would be a better place for a disclaimer of this type, along with the other non-goals.

from yari.

Accessibility isn't a non-goal of Baseline, the delineation that was made in web-platform-dx/web-features#519 is that if the browser does the wrong thing we consider that a user-affecting bug like any other, and it might lead to the feature not being considered ready. It's bugs outside of the browser, in the ATs, that we're not tracking.

from yari.

Indeed, Baseline doesn't override general web development best practices: you should still test your code, regardless of what the compatibility data suggests. Perhaps some kind of "how to use Baseline" document would be a better place for a disclaimer of this type, along with the other non-goals.

I would like to echo this sentiment. Perhaps the Baseline glossary page is the right place to cover some of this stuff. That Extra considerations section could use some attention, along the lines of: don't forget to do accessibility, usability, performance, and other testing, or you'll be sorry whether or not there was a blue or green mark.

from yari.

I would like to echo this sentiment. Perhaps the Baseline glossary page is the right place to cover some of this stuff. That Extra considerations section could use some attention, along the lines of: don't forget to do accessibility, usability, performance, and other testing, or you'll be sorry whether or not there was a blue or green mark.

We discussed this internally and support Daniel's proposal to reflect this on the Baseline glossary page. 👍

from yari.

I opened a PR for this in content: mdn/content#33515

from yari.