This document outlines 25 common problems found on library websites and provides suggestions for how to fix them. The problems are organized into four categories: missing but not forgotten, everybody else got the memo, search headaches, and major league problems. Suggested fixes range from simple changes that can be made by library staff to more complex issues that may require hiring a professional web developer. The overall goal is to make library websites more user-friendly, accessible, and responsive to patron needs.

1. 25 PROBLEMS
ON LIBRARY WEBSITES
(AND HOW TO FIX THEM)
#libsite25
Laura Solomon @laurasolomon laura@designforthelittleguy.com

2. http://oplin.ohio.gov

3. Humor, you haz it?

4. ANECDOTES

6. Laura’s Incredibly Subjective
Complexity Scale*
EASY
No big deal
MEH
Might need some
HTML/CSS knowledge
OY
Get a pro
*NOT PROPORTIONAL

7. Agenda
•Missing but not forgotten
•Everybody else got the memo
•Search headaches
•A major league you don’t want to be in
#libsite25

8. MISSINGBUT NOT FORGOTTEN
#libsite25
Laura Solomon @laurasolomon laura@designforthelittleguy.com

9. #25
Board of Trustees?

10. http://codes.ohio.gov/orc/3375.33v1

11. Add board member names to your library’s website.
Contact info and/or photos are nice but optional.

12. #24
No phone and/or address on homepage

13. Add the address and main phone number to the homepage,
either in the header or footer.
You may need some basic HTML/CSS to shift things around to
these elements.

14. #23
No hours or hours link on homepage

15. Add the hours, either in full or as a conspicuous link.
You may need some basic HTML/CSS to shift things around to
this element.

16. #22
No custom favicon

18. Create a custom favicon.
You may need some basic HTML/CSS to add the metatag for
element. You may need basic graphic design skills to create the
image.

19. #21
No breadcrumb trails

21. If you’re not using a content management system with this
feature built in, you’re going to need a professional.
To create breadcrumb trails dynamically, you’ll need someone to
write some serious code.

22. EVERYBODY ELSE
GOT THE MEMO
#libsite25
Laura Solomon @laurasolomon laura@designforthelittleguy.com

23. #20
Using images as text

24. Replace images of text with actual text.
You may need some basic HTML/CSS to insert, position and
the text.

25. #19
Logos that don’t link to home

26. Make your library’s logo a link to the homepage.
You may need some basic HTML to add a link to your library’s
logo.

27. WARNING
THE FOLLOWING MAY BE DISTURBING
FOR SOME AUDIENCES.
VIEWER DISCRETION IS ADVISED.

28. Logos, logos everywhere
#18

29. Do you really need ALL of those logos? Evaluate carefully.
You may need some basic HTML to remove these and/or add
some descriptive annotations.

30. Clip art
#17

31. Stop using clip art.
Even stock photography is a step up. But evaluate whether or
an added graphic really adds value, or just is a cutsey-add-on.

32. Problematic navigation
#16

33. Change the wording to intuitive terms.
People are task-driven on the web. See the webinar handout for
more info on better terms to use.

34. #15
Rotating banners (carousels)

35. Look, I know you won’t get rid of it, no matter what the data
says.
At least make sure that the images have alternative text
and that the carousel doesn’t auto-rotate.

36. #14
Fonts under 16 px

37. Make all text at least 16 pixels.
You may need some basic CSS to change font sizes.

38. #13
Huge flyer images

39. Just stop doing this!
You’re slowing your library’s site down, making it more
inaccessible to handicapped users and costing people more
money on mobile.

40. Staff-only links
#12

41. Get rid of the staff login link.
Buy a simple domain for your library’s intranet, have staff
bookmark it, whatever it takes. Get it off the site.

42. Unnecessary widgets
#11

43. Remove widgets that don’t provide real value to your patrons.
You may need some basic HTML to remove these kinds of items.

44. SEARCH
HEADACHES
#libsite25
Laura Solomon @laurasolomon laura@designforthelittleguy.com

45. #10
No search at all

46. #9
No search options

48. #8
More than one search

49. #7
Placeholder text

50. #6
Search in the wrong place

51. Chances are good that your library’s search feature has more
than one of these issues.
Most of these will likely require more major HTML/CSS
modifications and/or back-end scripting.

52. #5
Redundant links

53. #4
Poor contrast

54. Change the color of text and links and check with a contrast
tool.
You may need some basic CSS to change colors of text/link
elements.

55. MAJOR LEAGUE
PROBLEMS
#libsite25
Laura Solomon @laurasolomon laura@designforthelittleguy.com

56. #3
Poor speed

58. There are so many different things that can cause a slow site.
Server configuration, scripts and script placement, images and
many more. Get a pro.

59. #2
Poor accessibility

60. Interpreting and correcting accessibility issues can be a major
undertaking.
Remember, Section 508 compliance is the bare minimum
Get a pro.

61. #1
Not responsive

63. This may likely require completely rebuilding your website…but
it will be worth it!
Consider using a CMS that has responsiveness built in, or
a professional.

64. We know…

65. QUESTIONS?
http://designforthelittleguy.com/libsite25.pdf
Laura Solomon @laurasolomon laura@designforthelittleguy.com