I look forward to the day when we no longer have to add the term “accessible” to phrases like “UI Patterns” and “experiences” and “components” because being accessible is implied by default as it becomes the standard and only way to build for the Web.
— Sara Soueidan (@SaraSoueidan) March 27, 2019
Category: Twitter
Posts from the microblogging service Tweitter.
RT @brucel: Validate your HTML. We didn’t when we published an article yesterday. It looked fine in all the browsers. But a mis-nested
Validate your HTML. We didn't when we published an article yesterday. It looked fine in all the browsers. But a mis-nested <span><del></span></del> caused this on iPhone's Reeder app (HT @pepelsbey_ ). Not every renderer of HTML is as forgiving as browsers. pic.twitter.com/K8ix2O6SM4
— Bruce Lawson (@brucel) March 27, 2019
RT @WebDevLaw: Props to all the software projects which declined every opportunity they were offered to participate in and influence the process, and will now cry victim over results. https://t.co/H2Jx45RNgT
Props to all the software projects which declined every opportunity they were offered to participate in and influence the process, and will now cry victim over results.https://t.co/H2Jx45RNgT
— Heather Burns (@WebDevLaw) March 26, 2019
RT @adactioLinks: Simple & Boring | CSS-Tricks https://t.co/ECOlaTRXV0
Simple & Boring | CSS-Tricks https://t.co/ECOlaTRXV0
— Adactio Links (@adactioLinks) March 25, 2019
Not long to go before I can add to this collection @hey_stac https://t.co/5CkWP9cgM5
Not long to go before I can add to this collection @hey_stac pic.twitter.com/5CkWP9cgM5
— Chris Taylor (@mrwiblog) March 24, 2019