For questions about the LibGuides system or account issues, please email: email@example.com.
For technical issues and immediate help, contact Springshare support directly by email firstname.lastname@example.org or click on the Report a problem link at the bottom of every LibGuides page and fill out the support form.
Making your LibGuides content accessible benefits everyone: people with or without disabilities. The following list provides suggestions for accessibility practices that will make your content more user-friendly.
Source: This list comes from WebAIM’s Principles of Accessible Design. This list does not present all accessibility issues, but by addressing these basic principles, you will ensure greater accessibility of your libguides content to everyone. You can learn more about accessibility at webaim.org.
It is recommended that you type directly into the rich text editor; then use the functions in the text editor to add style and formatting. Creating the text elsewhere and attempting to copy / paste it into the text editor will bring in a lot of unnecessary HTML code and formatting, which will also introduce inaccessible content.
<h3>in HTML) and follow by Heading 4 in the rich text editor.
<em>tags in HTML) to indicate emphasis. Use these tags sparingly.
<i>tags as they denote style rather than importance.
Credit: The content under Implications in LibGuides is a derivative of the Boston College LibGuides: LibGuides Standards: Accessibility page.
Use headings as indicators for sections and sub-sections in your guide. This not only provides hierarchical organization and formatting, but also makes it easy for screen readers to scan and jump to different content areas.
<h1>tag in HTML) in your guide as this should only be used once for the entire page.
<h3>tag in HTML) and then Heading 4 in rich text editor.
All Images need to have Alternative text (ALT tag) included. To add a ALT tag to your image in the rich text editor, you will
Color Contrast Checker