Posted on October 28, 2015
The conversation came up internally at WebDevStudios, and I knew I had seen Ethan Marcotte, and/or Mat Marquis rant on it a bit before (I mean that in the best way), so I hit them up on twitter:
.@wilto @beep do either of you (or anyone) have a good resource for “why you should care about disabled JS” that I can pass around?
— Justin Sternberg (@Jtsternberg) October 28, 2015
They did not disappoint.
@Jtsternberg @wilto Three come immediately to mind:
— Ethan Marcotte (@beep) October 28, 2015
@Jtsternberg @wilto (Hint: it’s not about “disabling JS.” It’s about “ensuring our work is accessible if the JS doesn’t download/execute.”) — Ethan Marcotte (@beep) October 28, 2015
@beep @Jtsternberg Yeah, exactly—building something that doesn’t have a single point of failure. A CDN goes down, a transfer cuts off.
— Mat MarqDRACULAS (@wilto) October 28, 2015
The conversation spread, and I got a some great input from a few others as well (thanks Sally Jenkinson, Zack Rothauser, Nicolas Hoizey, and Adrian Roselli!):
@Jtsternberg @scottjehl @wilto @beep Jeremy Keith’s talk on Resilience: https://www.youtube.com/watch?v=3aw6U2uVl0I
— Zack Rothauser (@zrothauser) October 28, 2015
— Adrian Roselli (@aardrian) October 29, 2015
Since I got such great responses and resources, I wanted to get it all down here on the blog so I could keep it as a reference. Hopefully it helps you as well.
“ensuring our work is accessible if the JS doesn’t download/execute.” – pretty much sums it up for me. Well done on the post though.
Pingback: Progressive Enhancement—Ain’t Nobody Got Time for that | GlückPress