Posts tagged “progressive enhancement” 

A few smart folks have already put together their thoughts on responsive tables and, while I think the proposed methods are pretty good, I think there might be room for improvement.

These last two days have been a bit of a whirlwind, but I have had a great time meeting and talking to the attendees (and other speakers) here at the HOW Interactive conference in San Francisco. Read on for the slides from my talk.

In case you hadn’t heard, Tim Kadlec fantastic book Implementing Responsive Design came out today from New Riders. It’s a fantastic and necessary read for any practicing web professional out there and I was honored Tim asked me to write the foreword.

Aaron’s been all over the place lately. He was recently interviewed for a segment on HTML5 that ran on BBC television in the UK. He also sat down for a chat with Jared Spool to talk about responsive design, adaptive user interfaces, mobile and more.

A few weeks back, I flew to Sweden to deliver a talk on progressive enhancement for mobile devices at Funkas Tillgänglighetsdagar. I thought I’d share my slide deck from the talk in case you’re interested.

Most sites have exhaustive Privacy Policies detailing what information they collect and what they may do with it, which is why I find it bizarre that many of these same sites have chosen to hand over their users’ browsing habits to third parties such as Twitter, Facebook, and Google without considering the implications.

A few years back, I wrote a little article celebrating the fact that you could actually apply image-replacement techniques to images themselves. Little did I know, six years later, it would become a useful technique for tackling high resolution displays.

What might progressive enhancement suggest in the world of culture and politics? It’s a subject I have been mulling over in my head for years and I thank Ben Hoh for finally coaxing it out of me.

When I opened my inbox this morning, I nearly fell over: Browser makers are considering supporting the WebKit vendor prefix (-webkit-*) because the web development community can’t be bothered to use the equivalent experimental properties for other browsers.