There's an ongoing kerfuffle about DRM (Digital Rights Management) being implemented in browsers and whether the W3C should publish a standard ('recommendation') that provides access to DRM content.
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.
Back in 2006 I posted about 'subscription accessibility', where sites have to pay to enable accessibility features for users. It came up with a different service so I thought it worth re-considering.
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.
In PPK's much needed research into how browsers handle media queries, he suggests that there isn't a use case for increasing the DPI when zooming in. I think I have one.
A post came up in my feed called the BOMB in the GARDEN by Matthew Butterick. I found it... frustrating. I don't think the solutions would help with the issues he raises.