Simulating color vision deficiencies in the Blink Renderer (available in Flemish and English)

Switch audio to English or Flemish by clicking on the settings wheel and selecting your preferred audio track. Switch on/off English or Flemish subtitles by clicking on the CC icon.
Chrome DevTools can simulate color vision deficiencies in the Blink Renderer, to help you designers & developers understand the accessibility of their color schemes. This presentation explains why we worked on this, how to achieve the same effect using web technology (HTML, CSS, and SVG), and how we actually implemented this in the Blink Renderer (C++)
Read more about our International Mother Language Day celebration series → goo.gle/mother...
Subscribe to Chrome Developers → goo.gle/Chrome...
Presenter: Mathias Bynens / mathias​
#MotherLanguageDay #ChromeDevelopers

[@ChromeDevs]

This video is part of our International Mother Language Day celebration series! Switch audio to English or Flemish by clicking on the settings wheel and selecting your preferred audio track. Read more on the series here → goo.gle/mother-language-day-2021

[@mondial3206]

TRÈS bien. Bienvenue

[@jurgentreep]

Nooit gedacht dat ik een Vlaamse video van Google Chrome Developers zou zien. Goed gedaan!

[@paulfontaine7819]

Wat een topkwaliteit in het Nederlands. Structuur, snelheid, doel, duidelijkheid. Top. Proficiat en dank je.

[@oli4wk]

This is definitely translated from English to Flemish

[@WilcoVerhoef]

Jup haha

[@uzunibrahim]

*That's one small step for KZbin, one giant leap for those who want to produce content in their native language.*

[@bigmistqke]

Mooi werk en fijn beetje inzicht te krijgen in het proces

[@2minuteschool929]

This dont need much sophistication..but a good step👍👍

[@Ostap1974]

Can you share is blink-internal viewport dependant on CSP?

[@mondial3206]

En Direct now

[@dachd]

I think this should not be part of a web browser. It's getting ridiculous what a Web browser is and will be. it should be a standalone plugin.

[@Countryen]

But isn't it just in the 'devtools'? Isn't that like using a plugin, users don't use it or what is your concern?

[@dachd]

@@Countryen You could argue that devtools are part of the web experience. If Firefox dies this huge devtool will be the only one developers will use. You are right, the code is probably modular. I'm just ranting, I am frontend dev myself and grew a huge distaste for the web. All they (browser dev companies) care now is more features. It doesn't matter if they look cool or are Awesome. If they add thousands of line of code to a already millions of line of code the browser becomes unforkable rewritteable mess. Webrowsing will become rotten and slow. Hopes for better days.

[@bigmistqke]

@@dachd lol

[@bigmistqke]

@@dachd there might be something to be said for maybe having a dev-browser with dev-tools and a stripped down version for clients, but I think it makes more sense to have it all part of the same package to prevent discrepancies between the versions. Dev tools are a big part of the web dev experience and it's one of the things I personally like most about working in the web: it's super easy to inspect and play around w the form on the fly.

[@dachd]

@@bigmistqke Agreed, however I would like to see the devtools be a portal platform for dev extensions.