We create more accessible solutions through better research, content, design, and development.

We still see teams approach accessibility that leave out the first three, and think about accessibility as ONLY a develeper thing. But it's everyone. Together. Or it doesn't work.

— Derek Featherstone (@feather) January 11, 2019

Seriously, folks. There are 78 days left of our industry's domestic regulatory framework. The time for you to buy one day of my time to talk about it is within the 78. Not from 79.

— Heather Burns (@WebDevLaw) January 10, 2019

Idk I'll never stop rooting for retaining the simplicity of HTML/CSS. We're breeding new devs everyday who jump straight to learning JS & don't understand the basics. Favouring over-engineering and bloating the web with ephemeral 'frameworks' because of shiny new toy syndrome.

— Onyeka Aghanenu (@OnyekaAg) January 9, 2019

The more I build accessible UI elements the more I witness how friggin powerful semantic HTML is.

Sure, I already knew how important it is but seriously accessibility is one of those things that make it SHINE!

Writing proper HTML+CSS certainly is a very powerful job of its own.

— Sara Soueidan (@SaraSoueidan) January 8, 2019

A thought keeps floating through my head on this vague discussion that "CSS is too complex" [for JavaScript developers]. If CSS threw exceptions and broke entirely, JS devs might not think it were so hard to grok.

Though, silent erroring is key to resilience.

/fistbumps HTML

— @rem (@rem) January 8, 2019