The fine folks at 18F just posted a beautiful write-up of the talk on progressive enhancement that I delivered as part of the 18F Design Speaker Series. I thoroughly enjoyed talking to the folks that came. They presented some interesting challenges and asked pressing questions—exactly the kind of engagement I love.
Dispatches From the Internets
I see this one all the time: something that looks like a button, but only a portion of it is tappable.
Last week Peter-Paul Koch (PPK) posted a lengthy treatise on why browsers should stop “pushing the web forward”. I thoroughly enjoyed the read and agree with him on a number of points. I also agreed with the well-articulated responses from Jake Archibald (of Google) and Bruce Lawson (of Opera). I guess I’m saying I see both sides. Like Chris Coyier, I live in a world filled with varying shades of grey rather than stark black & white.
Insurance company Unum has just released the “UX Toolkits” (a.k.a. patten libraries) they use for both Unum and Colonial Life. They are pretty bare-bones right now, but I am hopeful they will flesh them out over time.
I love it when companies share stuff like this.
The U.S. Department of Justice (DOJ) has published Statements of Interest in two cases brought by the National Association of the Deaf (NAD) against Harvard (PDF) and MIT (PDF), respectively. The NAD is suing the two universities for violations of Title III of the Americans with Disabilities Act (ADA) and Section 504 of the Rehabilitation Act because the video and audio materials they are making available as part of their online learning offerings are not captioned.
I had the great pleasure of delivering the closing keynote for the final Responsive Day Out. Here’s what I had to say.
One of the greatest challenges of progressive enhancement lies not with the coding, but with the planning. It can be incredibly challenging to articulate how a single interface might adapt to a wide variety of situations. Interface Experience Maps (Ix Maps) can help.
It’s like a snake eating its own tail:
Wonder what’s going on? Well, Facebook’s mobile site (
m.facebook.com/ClydesOnMain) is tracking the URL (using the
refsrc GET parameter) I came from (
www.facebook.com/ClydesOnMain#!/ClydesOnMain)—a single page “web app”, hence the hash-bang:
#!—that was tracking the original referral page (
I hope they got all that.