An in-depth examination of aria-label and aria-labelledby.

A few simple, practical examples of how to make your interfaces more accessible, by Eric Eggert.

Great minds think alike… I wrote at length about native semantics vs. fully-customized divs and the number of dependencies that come with the latter in the second edition of Adaptive Web Design.

A list of things browsers must implement to ensure poorly-coded sites work. That this is needed deeply saddens me.

The picture element, faster taps, desktop gestures, and more are coming in the next iteration of Apple’s browser.

Yep, they’re at it again…

Dan Mall’s excellent overview of decoupling content and display using structured data to make your sites more flexible.

Microsoft is end-of-life-ing IE8–10, but that doesn’t mean we should stop supporting them. Some people can’t upgrade for reasons way beyond their control.

Alex Lande doesn’t believe optimizing for a no-JavaScript scenario makes sense, but he does believe in building a robust web experience pays huge dividends.

Progressive enhancement is a tool that will help you build faster, tougher sites. It is an investment in the strength and quality of your application. It will make your users happy because the app will still work, if imperfectly. It might just save you when disaster strikes, and if you’re interested in building the best websites possible, you should give it some thought.

Eloquently put.

Accessibility is just good customer service. If you run an commerce shop, you should be following this article’s advice. Heck, if you run any kind of site, you should do it.