It would save a lot of time in the day of an accessibility practitioner if automated tools could catch more accessibility errors. However, I think it’s a reasonable assumption that they should catch errors with incorrect nesting of HTML or ARIA. Unfortunately this is not the case, and Adrian Roselli has a nice breakdown with tests on his blog:
Developers who build a broken thing, but do not have the necessary testing or even standards experience might rely on automated tools and produce problematic content as a result.
Source: Beware False Negatives | Adrian Roselli
Thinking with a progressive enhancement mindset, that is starting with the most basic HTML features and enhancing with more advanced stuff, is in my opinion the best way to go about building inclusive, accessible websites. Jeremy Keith wrote about some accessibility feedback he got and how his originally robust code made the solution an easy… Continue reading Accessibility and Progressive Enhancement
Nine years ago I wrote a post on my first experience making my own Christmas Pudding at home, just like my mum used to make them. I haven’t been bothered to make my own for a few years now, especially since they are easier to find these days in Finland. Like I wrote in my… Continue reading Christmas Pudding, Revisited
Today I gave a talk on the EU Web Accessibility Directive at WordCamp Turku. The slides to my talk are on SlideShare, but a blog post summarising the talk will be up here next week. Today was also my last day at Zeeland Family. I joined H1 in 2012 as the third employee. It was… Continue reading End of An Era
I recently discovered it’s pretty easy to trick myself into reading more books and wasting less time looking at my Twitter feed. A lot of my phone usage is just a habit and habits can be changed. So here’s the magic 3-step program: Move social media apps into a folder or off the home screen… Continue reading Lifehack Tip: Make Better Use of Your Time by Rearranging Icons