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.
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.
Interesting post from Google on their update for reCAPTCHA, where they are replacing the current CAPTCHA method.
This was my first CSUN conference and it was a very enjoyable, if very tiring event. Having posted quite a few sets of notes from the sessions, I though an overview of the resources and experience would be helpful.
Amy Chen, Olga Sokolova and Beth Bemis talk about how they incorporate accessibility into the agile process at Workday.
Billy Gregory and Karl Groves talk about demystifying and simplifying mobile testing with live demonstrations and straightforward techniques.
Shadi Abou-Zahra and Eric Velleman spoke about the "Website accessibility conformance evaluation methodology" (WCAG-EM), i.e. how you test an entire website for accessibility.