Posts tagged “accessibility” 

Last week I shared a link about progressive enhancement for mobile on Forrst and it elicited quite a reaction from one reader which, in turn, prompted a lengthy response from me. I thought it was a conversation worth archiving here.

After a whirlwid trip to 4 countries, I am back to a rock-solid internet connection and got a moment to take a breath and post my slides from the first stop on the trip: Beyond Tellerrand in Düsseldorf, Germany.

In the past few months, I’ve spent an inordinate amount of time discussing the differences between the “adaptive” and “responsive” web design philosophies. Don’t get me wrong, I love having these discussions, but I felt the need to set the record straight: these two philosophies are not at odds.

I just finished Day 1 of Future of Web Design here in NYC and wanted to post my slides before I crashed for the night. Enjoy!

This past week, Kelly and I were in Brooklyn for the ExpressionEngine CodeIgniter conference. We had a great time, met some awesome people, and I got to talk about my favorite topic: progressive enhancement.

You may not have noticed, but we just turned this blog on it’s head, design-wise. Those of you browsing on something other than a desktop browser should now be enjoying a much better reading experience. Here’s what’s changed and how we did it.

I've been cautioning folks against over-reliance on JavaScript for the better part of a decade. Apparently Gawker didn't get the memo.

Tell me if this sounds familiar: “HTML5 and CSS3 do not have enough browser support to start using them today.” Or, how about this one: “We still have to support IE6, so using advanced CSS techniques would be a wasted effort.”

By default (or at least in the default configuration provided under the LG TinyMCE extension for ExpressionEngine), TinyMCE will remove the alt attribute if it is empty. Obviously, for accessibility and validation reasons, this is highly undesirable and needs correcting.