The auto-play policy detection specification (incubated in the @wicg_) allows Web developers to determine whether their media will be played automatically, which in turns enable browsers to take more restrictive media play policies github.com/wicg/autoplay/
I strongly feel web pages should not be allowed to autoplay audio when they are opened. Opening such webpages in a new tab and then navigating to mute the audio is such an annoying experience.
@GoogleChromeDev@firefox@w3cdevs
ICYMI, we published the @w3ctag#ethicalweb principles last week, a finding that will help to inform our continuing work on reviewing new technologies and refining the architecture of the web. I will be speaking about them later in the week in Bucharest at @DevTalksRo.
Harassment, disinformation, filter bubbles, algorithmic bias in feeds and ranking...
The web we all create has massive ethical implications. As spec authors, we have a responsibility to consider them.
Our new finding:
@W3CTAG Ethical Web Principles
w3.org/2001/tag/doc/ethical-…
🎇 I made a small tool for everyone: CSS Grid Generator. You can designate rows, columns, gaps, and units, and then drag to create child divs to make dynamic layouts with ease!
Open source on GitHub and deployed on @Netlifycssgrid-generator.netlify.co…
The module improves #accessibility, too. #Developers can find out if #a11y features, such as high-contrast mode, are in force and cooperate by adjusting the style
The new model uses media queries to check if the user has defined colors. The "color-scheme" property makes an element use them. You can even choose to allow only light or dark color schemes: w3.org/TR/2019/WD-css-color-…
The idea isn't new. Over 20 years ago, Netscape ONE tried to visually blend #Web apps into their environment by making the desktop itself a #webapp. The original #CSS level 2 had "system colors" (now deprecated). Later, the CSS Color module proposed "flavor"