The craft of building websites is incredibly complex with many fast-changing parts. The goal of the web design community is to lessen the complexity, and reduce the potential for error at each stage of the creation process.
Progressive enhancement is such an idea in web design that aims to reduce errors and provide a consistent user experience across the board. The concept has its own Wikipedia page which explains it as a method of fully-accessible content, rendering enhanced features only when supported by the browser.
It’s easy to understand progressive enhancement, but not as easy to apply it directly to your design work. I’d like to cover some best practices for progressive enhancement in real-world projects to help designers think more sustainably about their workflow.
1. Understanding Progressive Enhancement
The theory of progressive enhancement recommends to start with a simple website that works in all browsers, making it accessible for every visitor. Then add features whenever possible.
This is the opposite of graceful degradation which includes all features by default, then degrades when something doesn’t work.
Progressive enhancement is better for the overall user experience, because at its core it loads only necessary elements. Every web browser can support text (and usually images). Without any CSS this information will look bland and tasteless, but it’ll be accessible.
This List Apart article argues that progressive enhancement is content-first with styles and dynamic components added later. Content in semantic HTML should be delivered before anything else.
Here’s a general rundown of the main features of progressive enhancement, that you should take into account:
- Semantic markup for all content
- Users’ browser preferences needs to be respected
- Content and basic functionality should be available to all users
Technological restraints in front-end development are primarily determined by browser compatibility. Progressive enhancement gets you back to the basics thinking about how the bare-bone simplest webpage might look like. From there, you can plan for more advanced features, like CSS3 properties.
But what about browsers that don’t support modern CSS3? This is where sites like Can I Use come into play. You should decide which features are worth implementing, and make judgements based on the target audience of your website.
2. Subsistence In Stylesheets
Most browsers today support all the basic properties you need. But advanced CSS3 is still a problem for legacy users, and progressive enhancement offers a solution.
Instead of looking for fallback methods to maintain these new features, concern yourself first with proper layout structures.
Take for example this JSFiddle that uses floats with two sidebars (
.fixed), and a fluid content area (
.fluid). If you delete all CSS, and rerun the code you’ll notice everything stacks up nicely with the first column, then second, and finally the last.
Some developers would prefer to have the content column (
.fluid) appear first in the HTML. This is where progressive enhancement comes into play, and alternate CSS solutions become viable.
The two primary goals of your HTML are as follows:
- Fully semantic and valid code
- A consistent experience for everyone
The most straightforward way to achieve these goals is to start from nothing and work up, as most progressive enhancement advocates would recommend it.
If your code looks good with CSS both disabled and enabled, then it offers a reasonable solution for everyone.
It’s also worth considering at what point you drop support for something. Microsoft has already dropped major support for IE6 , so users running that browser may not be worth your time.
But there’s still one big question: if a browser doesn’t support my modern CSS, what should I do?
You simply write code that works without it, and consider the modern CSS as a progressive enhancement. This is the beauty of the progressive enhancement methodology.
You don’t need fallbacks, because you’re basically assuming that nothing is supported by default.
Progressive enhancement methods are about making the site usable even in cases when something isn’t supported—but if it is supported, all the better.
You need to consider how content actually flows without CSS. For example, when I disable CSS on Transmit’s website, the content still flows organically down the page.
Yes, it’s ugly, and yes, it feels like we’ve lost twenty years of progress… but it works.
This will require lots of online research to find valid solutions. Aaron Gustafson wrote a great blog post with solutions to various problems, like replacing Ajax with a meta refresh for content inside an iframe.
Here’s another example. Let’s say you have a link that loads content dynamically. The
Instead, it would be wise to set the
Operate under the assumption that everything has been disabled, and scale up from there. This might include problems with embedded widgets that are out of your control, the
<noscript> tag is a viable solution here.
Every feature requires individual testing with an individual solution.
- Progressive Enhancement: It’s About the Content
Where Progressive Enhancement Falls Short
Although progressive enhancement is a brilliant idea for almost every type of modern website, it simply may not be applicable to projects that aim to push the limits of web technology.
For example, this methodology is not a good solution for web applications that function solely on Ajax calls. Is that a good choice for accessibility? No, of course not. But if that were the case most of Codrops’ tutorials wouldn’t even exist. You have to remember the target audience.
A business website probably doesn’t have the audience that cares about flashy new CSS3 perspective properties, but web developers can be the perfect audience for such advanced features.
Progressive enhancement only falls short for web applications that simply don’t care about going back in time. I realize these web applications are few and far between, but developers love progress, and in some cases it can be sensible to forge ahead with new tech leaving the stragglers behind.
I am a proponent of progressive enhancement (or even graceful degradation, your choice) for general web projects. But I also realize it’s not the perfect solution for everything. In fact, there is no perfect solution. It all boils down to audience needs and project goals.
If you’re constantly building web projects, you should consider applying progressive enhancement to your workflow. It’s much easier than it seems at first glance, and it all starts with the fundamentals. Most topics surrounding progressive enhancement just require practice and testing. Try out the suggestions from this article, and see what works best for your workflow.
If you want to learn more about progressive enhancement, check out these related posts: