I didn't know Wave was such a useful tool for finding accessibility issues for sites running locally, I'll definitely be using that more in the future!
I have found lots of bugs just by trying to do the same basic tasks with only a keyboard, which was helpful and surprising since they seem obvious the second I find them. Thankfully like many a11y issues, the fixes weren't that tough and were mostly adjustments to the DOM and semantic HTML elements. ...Except for modal focus issues, those still haunt my dreams.
Great piece, and I think some in-depth looks at testing for keyboard and screen reader usage would be some great follow-ups. I'd especially be interested in the Screen Reader one, since despite testing with it many times I get the feeling there's many ways to use it I'm overlooking.
I'm a self-taught Front End & JS Dev and professional learner with accessibility expertise. I'm passionate about breaking down concepts into relatable concepts, making it more approachable.
Yeah, I actually might want to partner with a screen reader user for that to make sure I know how they actually navigate it. I don't want to make so many assumptions as someone who is able bodied.
Yeah, I've often done the same when it comes to screen reader testing. I'm still unfamiliar with it in many ways, so there's likely different approaches or tricks to using it I don't know of but should likely take into account.
I think Smashing Magazine had an article with footage of a regular screen reader user, but I've never gotten around to watching it unfortunately. Here's the link: smashingmagazine.com/2019/02/acces...
I'm a self-taught Front End & JS Dev and professional learner with accessibility expertise. I'm passionate about breaking down concepts into relatable concepts, making it more approachable.
I didn't know Wave was such a useful tool for finding accessibility issues for sites running locally, I'll definitely be using that more in the future!
I have found lots of bugs just by trying to do the same basic tasks with only a keyboard, which was helpful and surprising since they seem obvious the second I find them. Thankfully like many a11y issues, the fixes weren't that tough and were mostly adjustments to the DOM and semantic HTML elements. ...Except for modal focus issues, those still haunt my dreams.
Great piece, and I think some in-depth looks at testing for keyboard and screen reader usage would be some great follow-ups. I'd especially be interested in the Screen Reader one, since despite testing with it many times I get the feeling there's many ways to use it I'm overlooking.
Thank you, Max! That's a great idea!
Yeah, I actually might want to partner with a screen reader user for that to make sure I know how they actually navigate it. I don't want to make so many assumptions as someone who is able bodied.
Yeah, I've often done the same when it comes to screen reader testing. I'm still unfamiliar with it in many ways, so there's likely different approaches or tricks to using it I don't know of but should likely take into account.
I think Smashing Magazine had an article with footage of a regular screen reader user, but I've never gotten around to watching it unfortunately. Here's the link: smashingmagazine.com/2019/02/acces...
Oh, this is a good thing for me to read! Thank you!