Comments (5)
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.
Related Issues (20)
- Excessive Header Size HOT 2
- Opening a specific section in a new tab or window, or from the address bar, doesn't scroll to that section HOT 8
- Add guide to CSS sidebar
- Add and fix Japanese translations in the `{{AvailableInWorkers}}` macro
- Search bar sometimes breaks when refocusing a tab with MDN
- Searching for `tilde` returns nothing HOT 1
- Add Korean translation of deprecated notice header
- Browser Compatibility Table uses wrong Firefox logo HOT 3
- Sidebar page icons do not display in zh-cn locale HOT 1
- Error not loading the original image when the locale translation markdown page does not exist
- Feature Request: Explain "Yes" in compatibility tables HOT 1
- Page URLs ending with .json don't show up HOT 3
- Search field is barely visible in mobile Safari
- Broken link to browser compatability section in API landing pages HOT 2
- [Suggestion] 'Locale' values would be better to be managed as a type. HOT 1
- Baseline component included on writing style guide pages HOT 1
- Non-Scrolling Sidebars Trigger Migraines HOT 3
- GlossarySidebar: Child terms are not available in the sidebar HOT 2
- Yari build possibly broken HOT 4
- web-features baseline status is not sync'd with BCD HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from yari.