Bogdan Lazar’s Post

View profile for Bogdan Lazar, graphic

I help product owners ship accessible websites w/o blocking ongoing work.

How a failed user test got me started with accessibility (and three reasons why it failed) I was running a user testing session on a website some years ago, before I had any idea about accessibility and screen readers. This person was blind, using a screen reader, and they had problems filling in a form. I instructed them to select the first option in a fancy drop down widget, but they just couldn't get to it with a keyboard. "But it's right there," I kept saying. "No, I can't get to it," they said. What the what!? I was just a deer in the headlights, completely stunned and utterly surprised by what was happening. That little widget that I was so proud of was making them feel frustrated and exhausted. Total surprise! Why was it a surprise though? 1. I didn't know what I didn't know. I wasn't aware that a lot of people will tab tab tab their way through a website. I had no idea about accessibility, people with disabilities, keyboard navigation - and semantic HTML apparently. 2. I was ignorant. I knew the tester will use a screen reader and still I thought everything will work fine. How different could it be? I did no research. 3. I wasn't prepared. Because I thought everything will go smoothly, I didn't bother to prepare for the what-if. What if something goes wrong and we can't finish the test? No preparation lead to me babbling my way through it all, probably annoying them and running the clock. That whole experience left both of us frustrated. I felt that I wasted their time and they just felt exhausted at the end. It made me realise that the way I was designing and building things on the web was excluding a whole lot of people. And that got me started on the path I am today. How did you get started?

To view or add a comment, sign in

Explore topics