New Course: Accessibility: Testing and Screen Reader Use
Introducing my new course on Plurasight, Accessibility: Testing and Screen Reader Use!
Personal site to archive digital accessibility-related learnings, mostly focused on technical implementations.
Introducing my new course on Plurasight, Accessibility: Testing and Screen Reader Use!
I am extremely proud to announce that my second course, Introduction to Developing Custom Components with ARIA, has just published!
My first course on Plurasight, updated to include WCAG version 2.1 was just published.
A few months ago, I wrote about solving an issue with VoiceOver and list–style–type: none;. The response that I got was surprising, for a few different reasons.
With that bit of additional CSS, we are able to return the list semantics for VoiceOver users without needing to touch the markup.
UPDATE June 2018 – I would like to assume that, based on this post/ conversation, Google has updated the checkbox...
UPDATE: A more recent version of this article was posted on CSS-Tricks: How to Disable Links. The topic of disabling...
Back in July, the fine folks at ForwardJS allowed me to give an "Intro to Web Accessibility" workshop. The workshop...
There has been a lot of talk in the last couple of weeks about whether JavaScript is needed or not...
After being approached almost a year ago, and with about 4 months of video production and editing, I am extremely...
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius — and a lot of courage to move in the opposite direction.
Being two former co-founders of well-known browsers and releasing brand new ones that cater specifically to user needs are not the only things in common. Unfortunately, these browser are also not
I have to be honest and say that I totally don't get the trend around Code of Conduct declarations for...
I've had the great fortune of being able to stand on the shoulders of giants, whom have allowed me to reach such great heights.
Nobody ever explained to me why/ how this actually made a form accessible, but understanding why makes this even more important to get right. The answer lies in how screen readers handle interaction via keyboard.