by Andy Clarke
In 2003, Dave Shea coined the phrase 'MOSe' (Mozilla, Opera, Safari enhancement). Several months later 'progressive enhancement' became a phrase that web designers knew, but were unable or unwilling to use on large scale, high-profile or commercial projects.
In 2007, web technologies such as CSS and DOM scripting, plus our understanding of how best to use them have matured enough so that progressive enhancement and a transcendent approach can be a reality.
But what of the future? In this closing session, Andy Clarke shares his vision of how web designers and developers will combine technologies in the future to provide audiences with experiences that are beyond progressive enhancement.
"In modern web development we must support all browsers. Choosing to exclude a segment of users is inappropriate, and unnecessary." Yahoo!'s publicly declared rationale for how to deal with supporting the thousands of different browsers that visit their pages is "Graded Browser Support".
This talk will be a walk through this support and how it ties in with the idea of progressive enhancement, then a look at some of the more common mistakes and misconceptions of progressive enhancement.
Every time non-semantic markup is used, a piece of data dies. Data was born to be shared. Discover how the use of semantic markup and microformats can obsolete common read-heavy APIs and can be paired with identity protocols to provide casual APIs for the loosely coupled generation.
by Andy Budd
In this session Andy will peer into his crystal ball and look at the future of CSS design and development. He'll examine some of the exciting new possibilities that CSS 3 will bring, and speculate when they will arrive. Using the concept of progressive enhancement, Andy will show you how you can take advantage of some these features today, and on which browsers they work.
The future of CSS is already here. It's just not evenly distributed.
by James Edwards
The best bits of Web 2.0 are conceptual not technological social networking, tagging, folksonomy and we don't really need Ajax to implement these ideas. We can build these next generation apps without destroying accessibility or riding roughshod through user expectations.
In this presentation, I won't be trying to tell you not to use Ajax, or decrying it as 'evil' or 'fundamentally inaccessible'. I won't spend a lot of time critisising bad examples unconstructive critisism is all too easy, and bad examples don't mean that a general principle is bad.
But I will be exploring and advocating the option of not using Ajax, on a case-by-case basis, as a solution or workaround to the problems it can create. And I'll be looking at some of the darlings of Web 2.0, to see how much of what they do really needs Ajax to make it work well.
by Jeremy Keith
Join me as I take a trip down memory lane. From the bad ol' days of the browser wars up to today's brave new Web 2.0, I'll be tracing the roots of an idea. That idea is progressive enhancement. Find out why progressive enhancement has only become possible thanks to technological advances. I will be explaining why progressive enhancement is so important to my workflow. I'd also like to take this opportunity to introduce the great line of developers speaking at the Highland Fling.
5th April 2007