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
Welcome back everyone, and happy new year! I took a break from writing posts during the holidays, as things just got too busy for me. This month’s post was inspired by a conversation with a friend. My friend was looking for guidelines on writing blog posts. She knew I had created guidelines for the blogs we have at the Boston Public Library, but she had trouble finding articles online with this information. The trouble is that most of the information I used, I gathered from sources about writing for the web. So, when she searched for blog guidelines, she didn’t find what I used.
The purpose of this post is to aggregate information on how to write blog posts, as an informal literature review. I will also include my own suggestions in here as well. I’ve broken things down by category, and included these three broad categories: Word Count, Readability, and Accessibility.
Continue reading Blog Post Best Practices: A Literature Review
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
This is a continuation of my Hall of Shame series, where I point out website “crimes” that many libraries are guilty of committing. If you missed my first post in this series, you can see it here: Hall of Shame series.
This time, I’m coming for those libraries (and other institutions) who don’t test their website to see if it works for people who are color blind.
Color blindness affects approximately 8% of all men, and 0.05% of women (National Eye Institute). This means out of the approximately 300 million people in the United States (doing the math myself) they may be as many as 12 million men and about 7.5 million women in the United States with some form of color blindness, which is a total around 19.5 million.
So, with all of these people who are color blind, what can we do to improve their experience on websites?
Continue reading Library Websites’ Hall of Shame: Color Blindness
This is a continuation of my Hall of Shame series. One of the many things I work on as a librarian is websites, more specifically, the usability, accessibility, and navigation of a website. In this series I will show examples of website sins libraries commit, and explain why they’re not good ideas. In all of my examples, the names of the libraries, and any other identifying information, will be blacked out to protect those guilty of these sins.
Before I go into this month’s post, I want to say this disclaimer: The issues I’m pointing out are very relevant, and should be rectified if there is a chance to do so. I don’t claim to know the budgets of these libraries or the reasoning behind their decisions, so I can only go off what I see on their websites.
With that disclaimer out of the way, let’s begin. This post is about libraries that don’t have their own website. Their website is folded into the university or city’s own websites. Below, are three big reasons why that is problematic, with screenshots of library websites to back up the evidence.
Continue reading What Not to Do on Your Library Website, or the Library Websites’ Hall of Shame: Not Having Your Own Website