Accessibility checkers are all over the map.

And the abandonment of icon fonts continues…

This is an interesting finding in the realm of accessibility: ARIA being harmful to the experience. As I understand it, the WAI’s recommended interaction and tab flow stems from the way people using AT would tab through traditional desktop interfaces (e.g., Windows). I wonder if, as more people use the Web as their primary means of interacting with software, those mappings have become less relevant, either through loss of muscle memory in the case of long-time AT users or a lack of awareness for those who’ve only used AT since the advent of the Web and Web-based interactions (i.e., folks who’ve never had to navigate their way through complex interfaces like Windows’ Device Manager).

I’d take it a step further: You don’t need a CSS framework.

Is all that weight worth it? Probably not. Play Doom instead.

This is an amazing post from Karolina Szczur concerning who we build for. You should read it.

Excellent post on the importance of web page performance:

Performance isn’t a technical niggle that “we should get around to fixing”. It is an opportunity to grow your audience, to grow your business, to convert more sales (or whatever it is eCommerce people do).

Performance is an opportunity, and a risk, the same way that a redesigned template is. Or a new logo. Or a change to the colour of a button CTA.

See also: Tim Kadlec’s 2012 post on 24 Ways.

An excellent in-depth analysis of GitHub’s current Content Security Policy including the issues they encountered and lessons they learned.

Casey Phillips did a nice write-up of the Chattanooga Open Device Lab in today’s paper. It even has the requisite shout-outs to Jeremy Keith and OpenDeviceLab.com

Accessibility is everyone’s job. Find out what you can do to ensure your web creations are as accessible as possible.