Hot take: We don’t need anymore inaccessible apps / products.
If you’re not gonna design with accessibility and inclusivity in mind, then why design at all?
— Emaly Abdou (@ItsEmaly) June 18, 2020
Category: Twitter
Posts from the microblogging service Tweitter.
The Almanac is consistently a treasure trove of facts featuring the very best thinkers and doers of the web. Maybe @csswizardry wants to tackle performance? Put some Yorkshire in it. https://t.co/iJJerD5jAY
The Almanac is consistently a treasure trove of facts featuring the very best thinkers and doers of the web.
Maybe @csswizardry wants to tackle performance? Put some Yorkshire in it. https://t.co/iJJerD5jAY
— Chris Taylor (@mrwiblog) June 18, 2020
RT @SaraSoueidan: I’m old-fashioned. I like my CSS seperated from my HTML; my HTML seperated from my JS; my JS separated from my CSS. I like my JS layer only added when I need it, usually progressively. CSS added progressively on top of semantic markup. I don’t fight the C in CSS, I embrace it.
I'm old-fashioned.
I like my CSS seperated from my HTML; my HTML seperated from my JS; my JS separated from my CSS. I like my JS layer only added when I need it, usually progressively. CSS added progressively on top of semantic markup. I don't fight the C in CSS, I embrace it.
— Sara Soueidan (@SaraSoueidan) June 17, 2020
Top of my list: probably guitarix. Then patchage, but that would require full JACK.
Top of my list: probably guitarix. Then patchage, but that would require full JACK.
— Chris Taylor (@mrwiblog) June 16, 2020
Seen this? @WebDevLaw https://t.co/hIshpIv0r5
Seen this? @WebDevLaw https://t.co/hIshpIv0r5
— Chris Taylor (@mrwiblog) June 16, 2020