Accessible LibGuides

At this time, no template has been selected as the "default" template for LibGuides at Tisch; however, that should change to improve usability and accessibility.

Studies generally indicate that side navigation is by far more useable than top-tabbed navigation. They also show that a one- or two-column layout is better for comprehension and retention than a three-column layout.

I believe a one-column or two-column layout with the guide creator profile box underneath the navigation menu is the best option, where the second column contains only supplemental information.

References: Exploratory Usability Testing of User Interface Options in LibGuides 2, Student-Centered Design: Creating LibGuides Students Can Actually Use, Creating Audience and Environment-Friendly Research Guides: Findings from a User Study

Underneath the title of your guide, it will say [Click to enter a description]. Your guide's title and other metadata should be robust enough for your guide not to need a description. It's redundant. It creates additional text where you want less. Leave this blank.

A guide's description is not visible unless a user hovers over the information icon next to its title on the Springshare guide list. While it doesn't technically break any accessibility standards by existing, users who can't operate a mouse without a tremor or who don't navigate with a mouse may not be able to access your guide's description.

Once you have your template selected, configure the navigation in the Settings Menu (gear icon):

If you plan to use subpages, use the checkbox for "Show all subpages in side navigation." This will help people who can see understand the relationship between the information on the page, as everything will be nested ahead of time in the menu.

Also, if you are using subpages, consider breaking up your guide into smaller guides, because you likely have a confusing megaguide situation on your hands.

References: WCAG Success Criterion 1.3.1 (Level A): Info and Relationships, WCAG 2.2, SC 1.3.2 (Level A): Meaningful Sequence

Each guide and its pages should have friendly URLs, as they allow users to understand more about a link before they click on it. Additionally, they allow users to better remember your guide's address, increasing the odds that they will return and use it again.

Capitalize the first letter of each word in your friendly URL, so it's easier for both humans and machines to parse.

• Good: https://researchguides.library.tufts.edu/humancentereddesign 
• Better: https://researchguides.library.tufts.edu/HumanCenteredDesign

More information at SpringShare's Assign a friendly URL to a guide & its pages documentation.