cc licensed flickr photo shared by ntr23

so at least two of us in the collective have recently gone live with new library websites (probably more, ’tis the time of year). as i was dealing with the fallout from this (and yes, i know, there will always be fallout – some of da peeples will never be happy, not never) i started wondering about the whole process of redesigning library websites.

what are we trying to accomplish with these redesigns? the answer is usually “to make things easier to find for our users”. but this is where it gets all kinds of sticky. libraries have _so_many_ different user groups. in my own library we have:

• undergraduates
• graduate students
• researchers
• professors
• librarians (both chez nous and at other institutions)
• continuing education students
• students who speak neither English nor French
• citizens of the city & province
• and, oh ya, ANYONE WHO FINDS US THROUGH THE GOOGLEMACHINE!

what does this mean for library site design?
how many groups do we need to consult prior to making a big change?
do we then weight the opinions of certain groups more than others?
when doing the redesign, should we do it in-house, or outsource it to a company that can make it sleeker than your average web services librarian has time for?
should we be designing for the 800×600 IE6 group of folks out there, or should we use the redesign of the library site to teach them that the minimum standards have changed, and they should join us, the friendly library, in this new (upgraded) online world?
where’s the line between accessibility and ease of use? is there one? is it possible to have a site that meets accessibility standards, is mobile-ready, and isn’t nine kinds of fug?

so, who wants to take a stab at answering some of these questions?