Thank you for this talk! I've learned a lot of useful things, especially dramatic hover-start! I'm also guilty of getting alt-text wrong all the time.
Would it be a good idea for web developer to try out these accessibility tool such as screen-reader to understand what the experience is like? Or is that a bit too extreme and we should just rely on linting tools and automatic test?
Miranda is a technical writer and product lead at VMware as well as founder of Books on Code, which is a platform for programmers who love to learn through technical books.
Location
San Francisco, CA
Education
MA English Literature
Work
Senior Technical Writer at VMware (previously Pivotal)
Absolutely use a screenreader tool! It's always valuable, builds empathy, and gives insight in a way nothing else can.
My original talk included a screenreader tutorial, but I cut it for time. Most operating systems have screenreader software built in. For Mac, it's Voiceover.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for this talk! I've learned a lot of useful things, especially dramatic hover-start! I'm also guilty of getting alt-text wrong all the time.
Would it be a good idea for web developer to try out these accessibility tool such as screen-reader to understand what the experience is like? Or is that a bit too extreme and we should just rely on linting tools and automatic test?
Absolutely use a screenreader tool! It's always valuable, builds empathy, and gives insight in a way nothing else can.
My original talk included a screenreader tutorial, but I cut it for time. Most operating systems have screenreader software built in. For Mac, it's Voiceover.