There are some interesting discussions on customisation going on with the work on WCAG 2.1, the much anticipated (I hope) update to the Web Content Accessibility Guidelines. This is a little inside-baseball, but I've tried to make it understandable for a wider accessibility-audience.
We know that a clear focus indicator is vital for people using a keyboard, so why do some website remove it? A little digging into how the browsers deal with it.
There have been a couple of articles on ARIA tabs recently, I pick up some specific points from both articles, analyse the interactions and suggest a way forward.
I also considered calling this "Why zoom sucks on mobile", as that is the biggest issue with zooming & web development. To understand why I'll walk through the different ways zoom works on desktop and mobile.
I recently started experimenting with flexbox. On this blog. Without enough testing. Or at least, without the kind of testing I would do for a work project. It's a live experiment! Here are the bugs I ran into.
Lessons learned from a project by Hans Hillen and Jennifer Gauvreau, what should have worked that didn't! Lots of JAWs/IE bugs and how they got around them.
Denis Boudreau and Wayne Dick presented on why browser zoom sucks, firstly from the point of view of testing with WCAG, and then from a low-vision user's point of view.
Doug Schepers on data visualisation with Web technologies such as SVG, Canvas, ARIA, and the Web Audio API, so that you can make accessible information graphics.
A presentation on the parallels between responsive design and accessible design By George Zamfir.
Taking my arguments about pixels being relative another step, the CSS pixel sizes that device makers use actually tell us the distance away from your eye that they think you should hold a device. Applying a bit of maths lets us work out what that distance is.