The worst time to ask for feedback is the time immediately after you’ve annoyed someone!
Have you ever had that experience? You’ve been kept waiting on hold in a queue that went on for what feels like hours, or you’ve had the worst customer service ever, and then you get a request to give feedback about how satisfied you were with the service? Sometimes people are so annoyed, that they do in fact give feedback – and it’s rarely positive.
I had a similar experience yesterday evening. I’m not going to name and shame the site here. I do sometimes use social media or my personal blog to highlight problems and try and get them fixed, but this blog is more about good practice. I will however explained what happened, because I think it’s important.
The site is one that I’ve used before. It’s not the most accessible, but I can get most things done without too many work-arounds. Recently they decided to make some changes and update the page I wanted to use.
I wasn’t aware of any improvements. Maybe it does look nicer. As a blind user, I can’t comment on that. What I did notice however, was that only two of the buttons that I might want to use had graphic labels. As luck would have it, the one that I wanted to click had not been labelled correctly. So I had a 50% chance between unlabelled0 and unlabelled1.
Would you click unlabelled buttons if you didn’t know what they would do?
I didn’t want to take my chances, so I asked someone to take a look and tell me which one I needed. I can remember for next time if I need to use that page again, but I shouldn’t have to. Sighted visitors to the page know what the buttons do.
Apart from the obvious frustration, there are two issues here:
Someone on the team clearly knows how to label buttons correctly, because the other two had graphic labels that my screenreader could read. In the same way that site owners want consistent branding and use of colour across their site, consistent web design and coding is important too, especially on the same page.
If none of the buttons had been labelled correctly, I might assume that the person designing it didn’t know how to. But that’s clearly not the case here.
2. Updates shouldn’t be a step backwards for accessibility
Previously, the buttons on this page did have correct graphics labels, and these somehow got lost or overlooked when the page was updated. This actually makes the experience worse for me now.
It’s easily done if you have more than one person working on a site, or if someone inherits a site that was designed by someone else, but it’s really important not to lose the accessibility features and basic good practice that were already built into the site.
Don’t be fooled into thinking that just because you can’t see a problem as someone didn’t bother to label a page control properly that nobody will notice.
In terms of the site in question, it’s not the first time that I’ve flagged an accessibility issue, it’s been fixed, and then the changes were lost in the next update.
This is a strong argument for why accessible and inclusive design should be on the agenda as a matter of course, not an afterthought whereby people have to fix all the things that get broken with an update.
Then they wanted my feedback!
Directly under the unlabelled buttons was a request for user feedback about the new design. I was happy to oblige and I hope that my feedback will be acted upon. I’d still have preferred it if I hadn’t had to spend time tracking down someone who could help me with something that previously hadn’t been an issue.
I’m fortunate. I do have someone who helps me with visual tasks in my businesses, but it’s an unfair and unrealistic assumption that blind people always have someone close by that can help them out. I don’t have help full-time, and if I want to use your site in the middle of the night when nobody is around, I should have that freedom just as any other visitor does!
People are creatures of habit and generally we’re not fans of change. This is even more so if you break someone’s user experience with your next update, so it’s worth making sure that anything you’re planning to do won’t have a negative impact on the accessibility of your site.
Get in touch
If you’d like to contact me or sign up for the monthly EwK Services newsletter, which will also contain links to new blog posts, please use this contact form: