• Usability as covering a wide range of concerns
  • ADA compliance and making a site that is accessible for differently able individuals is a given. We will make a site like that, but that process is a more technical one which we will handle during development, it is not what the group will focus on.
  • Our usability focus is more on user experience and ease of use. Logic and minimal need for search.

  • emphasize clarity and being easily understood, minimize clutter
  • use words that users are familiar with over library specific terms or terms that have unique connotations in a library.
  • define or explain professional or specialized terms wherever they must be used (use hovers to define databases and other terms)
  • use simple, clear action words (find vs research)
  • what does your navigation and its phrasing express to the audience/users

Sites to Review
  • Oregon State
    • hours
    • central search
    • constant nav with common language titles
    • ask a librarian
  • SUNY Buffalo
    • choice of navigation terms
    • dropdowns
    • importance of listing ask a librarian as separate from help and as a top level
  • University of Arizona
    • central search
    • dropdowns
    • choice of terms in navigation
  • Indiana University - Bloomington
    • overhelming (do not put to many things on a page)
    • repeated common tasks across groups (put common tasks on a landing page for ease of use)
  • Iowa State
    • alphabetical as problematic (can use more than one scheme to index or link to resources)
    • how the three programs: knowledge base, instruction/learning, and cultural/discourse could influence the site.

Guidance Transition

  1. Define what elements go on the home page
  2. Select IA type (audience/task/hierarchy/hybrid)
  3. Determine top level navigation
  4. Determine Criteria

1 through 4 will be turned into a written document which will guide the development of the site and how we classify and use content in the future.