Why you should ask users to test your website on their own devices
Testing a website means ensuring that it’s usable and accessible for your users. If parts of your library’s website don’t work—for example, if the layout of the search results is confusing, or clicking the chat button doesn’t do anything—then your users’ trust in your library will decrease, and they may be incentivized to look elsewhere to find help or get access to materials.
With just three devices [mobile, tablet, and desktop], you’re already seeing a range of how the website looks and behaves. Now imagine how many kinds of devices your patrons are using. The many different sizes of screens, the many models of mobile devices, the different browsers, and even the different speeds of various networks. What is the experience of using the library’s website like in these different scenarios? How would you know?
I write monthly posts for LibTech Insights, a blog about technology in academic libraries from Choice, an ACRL/ALA publisher.