<ul class="tabrow">
//AN_Xml:    <li>Lorem</li>
//AN_Xml:    <li>Ipsum</li>
//AN_Xml:    <li class="selected">Sit amet</li>
//AN_Xml:    <li>Consectetur adipisicing</li>
//AN_Xml:</ul>

.tabrow {
//AN_Xml:    text-align: center;
//AN_Xml:    list-style: none;
//AN_Xml:    margin: 0;
//AN_Xml:    padding: 0;
//AN_Xml:    line-height: 24px;
//AN_Xml:}
//AN_Xml:.tabrow li {
//AN_Xml:    margin: 0 10px;
//AN_Xml:    padding: 0 10px;
//AN_Xml:    border: 1px solid #AAA;
//AN_Xml:    background: #ECECEC;
//AN_Xml:    display: inline-block;
//AN_Xml:}

.tabrow li.selected {
//AN_Xml:    background: #FFF;
//AN_Xml:    color: #000;
//AN_Xml:}

.tabrow {
//AN_Xml:    position: relative;
//AN_Xml:}
//AN_Xml:.tabrow:after {
//AN_Xml:    position: absolute;
//AN_Xml:    content: "";
//AN_Xml:    width: 100%;
//AN_Xml:    bottom: 0;
//AN_Xml:    left: 0;
//AN_Xml:    border-bottom: 1px solid #AAA;
//AN_Xml:    z-index: 1;
//AN_Xml:}

.tabrow:before {
//AN_Xml:    z-index: 1;
//AN_Xml:}
//AN_Xml:.tabrow li {
//AN_Xml:    position: relative;
//AN_Xml:    z-index: 0;
//AN_Xml:}
//AN_Xml:.tabrow li.selected {
//AN_Xml:    z-index: 2;
//AN_Xml:    border-bottom-color: #FFF;
//AN_Xml:}

.tabrow li:before,
//AN_Xml:.tabrow li:after {
//AN_Xml:    position: absolute;
//AN_Xml:    bottom: -1px;
//AN_Xml:    width: 6px;
//AN_Xml:    height: 6px;
//AN_Xml:    content: " ";
//AN_Xml:}
//AN_Xml:.tabrow li:before {
//AN_Xml:    left: -6px;
//AN_Xml:}
//AN_Xml:.tabrow li:after {
//AN_Xml:    right: -6px;
//AN_Xml:}
//AN_Xml:.tabrow li:after, .tabrow li:before {
//AN_Xml:    border: 1px solid #AAA;
//AN_Xml:}

.tabrow li {
//AN_Xml:    border-top-left-radius: 6px;
//AN_Xml:    border-top-right-radius: 6px;
//AN_Xml:}
//AN_Xml:.tabrow li:before {
//AN_Xml:    border-bottom-right-radius: 6px;
//AN_Xml:    border-width: 0 1px 1px 0;
//AN_Xml:}
//AN_Xml:.tabrow li:after {
//AN_Xml:    border-bottom-left-radius: 6px;
//AN_Xml:    border-width: 0 0 1px 1px;
//AN_Xml:}

.tabrow li:before {
//AN_Xml:    box-shadow: 2px 2px 0 red;
//AN_Xml:}
//AN_Xml:.tabrow li:after {
//AN_Xml:    box-shadow: -2px 2px 0 red;
//AN_Xml:}

.tabrow li:before {
//AN_Xml:    box-shadow: 2px 2px 0 #ECECEC;
//AN_Xml:}
//AN_Xml:.tabrow li:after {
//AN_Xml:    box-shadow: -2px 2px 0 #ECECEC;
//AN_Xml:}
//AN_Xml:.tabrow li.selected:before {
//AN_Xml:    box-shadow: 2px 2px 0 #FFF;
//AN_Xml:}
//AN_Xml:.tabrow li.selected:after {
//AN_Xml:    box-shadow: -2px 2px 0 #FFF;
//AN_Xml:}

.tabrow li {
//AN_Xml:    background:      -o-linear-gradient(top, #ECECEC 50%, #D1D1D1 100%);
//AN_Xml:    background:     -ms-linear-gradient(top, #ECECEC 50%, #D1D1D1 100%);
//AN_Xml:    background:    -moz-linear-gradient(top, #ECECEC 50%, #D1D1D1 100%);
//AN_Xml:    background: -webkit-linear-gradient(top, #ECECEC 50%, #D1D1D1 100%);
//AN_Xml:    background: linear-gradient(top, #ECECEC 50%, #D1D1D1 100%);
//AN_Xml:    box-shadow: 0 3px 3px rgba(0, 0, 0, 0.4), inset 0 1px 0 #FFF;
//AN_Xml:    text-shadow: 0 1px #FFF;
//AN_Xml:    margin: 0 -5px;
//AN_Xml:    padding: 0 20px;
//AN_Xml:}

Do I care about validity?

Validity as in "Does it validate?" according to the W3C Markup Validation Service. Validation is a tool to help you find problems and write better markup. But just because something doesn't validate doesn't make it bad or wrong. If invalid code works wonderfully in all browsers, you nor anyone else should care.

If you do care about validity (perhaps a client irrationally requires it from you and is holding your paycheck randsom) then there are a few techniques that you can't use. The picturefill technique, for instance, uses the <picture> element to work its magic. This may ultimately be standarized, but it isn't yet, so it's technically invalid syntax. It's also required that <img> elements have a src attribute, so techniques that remove that to get around the double-image-request problem are invalid.

I'd recommend these techniques if validity is a requirement for you: Adaptive Images, HiSRC, or Responsive Enhance. All of which use simple, valid <img> syntax that include a src.

Do I care about art direction?

Some responsive images techniques serve different resolution versions of the exact same image. While that makes things easier (i.e. less work) it may not acceptable. Here's a visual example:

//AN_Xml: //AN_Xml:

These images are hand-crafted by a designer, cropped to retain meaning and impact. If you took the image on the right and just scaled it down, the people in the image would be very small and the feel of the image my be lost.

If this idea of art direction is important to your project, you'll need a technique that will allow you to specify exactly which src to serve under which circumstances. This is picture perfect (GET IT?) for picturefill which allows you to be very specific about sources and what circumstances get what.

<picture alt="description">
//AN_Xml:  <source src="small.jpg">
//AN_Xml:  <source src="medium.jpg" media="(min-width: 400px)">
//AN_Xml:  <source src="large.jpg" media="(min-width: 800px)">
//AN_Xml:</picture>

JavaScript takes it from there.

Do I care about JavaScript?

Most of these responsive image techniques utilize JavaScript to work their magic. Some only a tiny bit to set a cookie, but JavaScript none the less. Some of them have you put an <img> in a <noscript> tag so that there is a fallback image in the case that the user has JavaScript turned off. If you don't like that, and you need to make absolutely sure that your images work without JavaScript, Sencha.IO is your best bet. This service works by identifying your device through it's User Agent string and serving an appropriately sized image. So you link to the largest (reasonable) version you have of it and Sencha will squeeze it down and server smaller versions if need be (it doesn't scale up, for obvious reasons).

What about JavaScript *library* dependency?

HiSRC and rwdImages are both jQuery dependent. If your project is using a different library, these probably aren't for you. But hey, you could port it and open source that! If you aren't using a library, well, you probably should be but let's not get into that.

Do I care about Server Side Components?

Some of these techniques aren't solely JavaScript dependent. Adaptive Images works it's magic primarily through .htaccess and PHP. Well, .htaccess presupposes an Apache server. And, while of course we all know and love PHP (ahem), many websites run on technologies like Ruby or Python.

Responsive Images (the original Filament Group technique) also uses .htaccess. So if you're using something like Nginx as web server, this is either out or you'll have to port over the .htaccess component to Nginx's similar-but-different syntax.

Do I care about bandwidth testing?

Testing the browser window width and making decisions on what image to serve based on that is pretty cool and fundamental to the concept of responsive images. But it's really only half of what the decision of what image should be served should be based on. The other half is available bandwidth. If the user has a very fast internet connection speed, serving large images is OK. If the user has a very slow internet connection speed, they should get smaller images (regardless of screens size). Unfortunately native bandwidth media queries don't exist.

Two of the current techniques do bandwidth testing as part of their decision making: Foresight.js and HiSRC (both are based on the technique in Foresight.js). It works by downloading a test file and measuring how long it took (configurable). The test itself is a slight performance hit, but theoretically the savings gained by serving images based on knowing the current bandwidth is a net (GET IT?) gain.

Do I care about relying on third parties?

Sencha.IO is a completely third-party way of handling responsive images. As far as I know, it works great and hasn't been inflicted with any major downtime, but of course you always run that risk.

You might be thinking: Wow, the Sencha.IO technique is really cool but I worry about the third-party dependency. I wish I could run that on my own server. If you want to go down that road, there is the public WURFL database and this Server Side Responsive Images technique which puts that to work locally.

There are also third-party services like Device Atlas Cloud which does device detection for you. It's also a third-party dependency for your app. No doubt their goal and focus is staying up and fast at all times, but you have to be very careful about who and what you rely on for your business.

Is there a specific CMS with specific CMS powers involved?

Say your project is in WordPress. WordPress has a media uploader built in. When you upload an image with it, it can create multiple versions (scaling down) of that image for you. That's pretty cool and powerful and you could/should take advantage of that. Keir Whitaker talks about using that ability in his article Automatic Responsive Images in WordPress.

This isn't just a WordPress thing though. I'm sure the concepts at work here could be done (or made to be done) in any Content Management System.

Can I wait for the future?

The release of the "new iPad" (the third one, for longevity) is what sparked a lot of these techniques and conversations. Its high pixel density is great for vectors and big photos, but actually not great for things like small icons that need to be scaled up to be the correct size and can be blurry. But serving higher resolution icons means larger file sizes and slower websites. Hence, the need to only serve them in situations/environments that need them.

The world of web standards is aware of this problem. There is a whole group dedicated to talking about it. In time, they may solve it and then we can start using whatever way they come up with (assuming its awesome and better than what we have now).

It may be flipping out the src of images through CSS content like Nicolas Gallagher suggested. It might be the <picture> element. It might be a srclist attribute in HTML or src property in CSS. It might be a prefix.

More resources

//AN_Xml:
• Jason Grigsby has an epic three-part series on responsive images starting here.
//AN_Xml:
• Christopher Schmitt's slides on a whole talk about responsive images.
//AN_Xml:
• Mat Marquis on Responsive Images: How they Almost Worked and What We Need
//AN_Xml:

Which responsive images solution should you use? is a post from CSS-Tricks

What's the most common result of clicking something on a website? Moving to a new URL, like you would clicking a link (an <a href="/example/"></a>) element).

The <button> element, by itself, can't do that. There have …

When To Use The Button Element is a post from CSS-Tricks

<button>
//AN_Xml:  Do Something
//AN_Xml:</button>

<form action="/" method="post">
//AN_Xml:  <input type="submit" value="Submit">
//AN_Xml:</form>

<form action="/" method="post">
//AN_Xml:  <button>Submit</button>
//AN_Xml:</form>

<form action="/" method="post">
//AN_Xml:  <button type="reset">Reset</button>
//AN_Xml:</form>

<button>
//AN_Xml:  <img src="tiny_birthday_cake.png" alt="">
//AN_Xml:  Submit
//AN_Xml:</button>

<a href="#0">
//AN_Xml:  I'm kinda sick of doing this for buttons.
//AN_Xml:</a>

<button>
//AN_Xml:  Outside of a <form>, I'm just as useless.
//AN_Xml:</button>

// 1. Create the button
//AN_Xml:var button = document.createElement("button");
//AN_Xml:button.innerHTML = "Do Something";
//AN_Xml:
//AN_Xml:// 2. Append somewhere
//AN_Xml:var body = document.getElementsByTagName("body")[0];
//AN_Xml:body.appendChild(button);
//AN_Xml:
//AN_Xml:// 3. Add event handler
//AN_Xml:button.addEventListener ("click", function() {
//AN_Xml:  alert("did something");
//AN_Xml:});

<a href="#meaningful" class="button" role="button">
//AN_Xml:  I'm good
//AN_Xml:</a>