It’s been a while since I posted, but this is the first time I’ve had some free time to sit down and think about things I want to say or share.
When I did usability testing for the redesign of the Boston Public Library website last year, we found that seniors had the most difficulty using the new website. At the time, we didn’t have time to explore much into it. We made the edits we needed based on their feedback, but I wanted to revisit this. Seniors tend to be the demographic group with the most difficulty with technology, and changes. However, they’re also a significant part of the population. I want to make sure as we look forward, we aren’t leaving them behind. Now, we finally have the time to work on this project, so here are a few things I’m reading as I think about how I want to approach this.
Continue reading What I’m Working On/Reading: July 2019
This post is about doing usability testing on a website for a public library, without a budget for usability testing, or any extra software beyond a simple survey tool and Google Analytics.
So, to start at the beginning, my team completely overhauled our old library website design, and for good reason(s):
- It looked very outdated, because it was basically a lightly modified version of the website we created in the early 2000s.
a. It was all static HTML pages for the most part.
2. The design wasn’t responsive, making it a headache for patrons on mobile or tablet devices, and for staff members trying to help users on mobile or tablet devices.
3. Certain parts of the website were not accessibility compliant.
Those are the biggest reasons for the switch, but as you can imagine, there were a lot of reasons to do it.
Continue reading How to Do Usability Testing Without a Budget