When adding an image to a LibGuides page, always make sure to put a meaningful description into the alternative text, or “alt tag” of the image.
The alt tag is a brief description of the image and its purpose on the page. Remember that the users who will be seeing the alt tag will likely not be able to see the image, so be sure to include all relevant information about the image’s appearance here.
For best practices on creating alternative text, please consult the ALT Text Guidelines Google Document (opens in a new window)
LibGuides content types that do not allow alt tags:
Book from the Catalog items: The WAVE tool may show an error for missing alt tags; however, you may leave these alt tags blank and still be in compliance. An alt tag, in this case, would be redundant to a screenreader because it would duplicate the element's title which is next to the image.
Images in Gallery Boxes: Gallery boxes are currently not compliant. The images have non-descriptive alt tags such as "Gallery Image 1" and the controls of the box (that rotate the images) are operable, but not fully accessible with screenreaders. The WAVE tool will not show an error. Springshare is aware of this issue.
Make sure that any videos you wish to include on a guide have closed captions.
Closed captions must accurately relate everything spoken as well as all relevant background noises and sound effects, and users must have the ability to turn them on or off during playback. Many videos on Youtube come with accurate closed captions. Any videos that you create should be uploaded to Ensemble, as these videos will be sent out for captioning automatically within a few days of being uploaded.
Specific remediation cases:
ADA Compliant Video Platforms:
Use only the default font color in your LibGuides.
Users with visual disabilities related to color may have difficulty perceiving a wide range of similar colors if they do not have a certain degree of contrast from the background color. Font color which is kept uniform across a set of pages helps users with low vision, color blindness, and cognitive or perceptual disabilities to better understand the relationships between content and structure on a page. Please use only the default style text in content boxes. To emphasize text, use the bold or italics styling button in the editor.
Please note, if you are using colors that do not appear in the print-only/screenreader version of the LibGuide, do not worry about checking them at this time.
Make content easy to read by making short paragraphs and using bulleted lists to itemize information when possible.
Break up content into small, easy-to-understand chunks for users’ ease of reading/understanding. Paragraphs should average 3 - 5 sentences in length. Most assistive devices allow users to quickly scan through these lists in the same way that they can scan through box headings. Use bulleted or numbered lists whenever possible to display itemized lists of information within content boxes on your guides. You are strongly encouraged to use the “Links: Links & Lists” box to create organized, clear lists of information.
Sections of content should be divided into separate boxes to ensure that content is easy to read.
Content boxes in LibGuides automatically create ADA-compliant Heading structure. If you must create a subsection within your boxes, use the “Heading 3” paragraph style in the editor to maintain the page’s ADA-compliant Heading structure.
Dropdown menu items are inaccessible through the keyboard, either with screenreader controls or traditional keyboard navigation. This issue has been reported to Springshare, but please refrain from using nested menus where possible.
As specified in Temple University's Web Accessibility Policy, tables should be used for display of tabular data only. Do not use tables to format content within your boxes.
In order to be ADA compliant, tables must include proper markup, specifically a summary, a caption, and headings.
To create an ADA compliant data table:
Example of compliant table:
Link to search boxes in the Box Repository Guide. Database search boxes must contain a label tag in order for screen readers to be able to read them. Boxes in the repository will be updated for ADA compliance. If you wish to create a new search box, please do so in the box repository to ensure that it is checked for ADA compliance.
WAVE is the Web Accessibility Evaluator Tool, a free tool designed to help web content creators check their sites for certain basic levels of accessibility.
Please note, WAVE alone is not a comprehensive accessibility solution and should be used in conjunction with human spot-checking (and other tools for validation such as Compliance Sheriff). As outline below, there are critical issues for ADA compliance that WAVE will NOT help you detect.
You MUST follow a WAVE check with a manual human check, to detect issues like these:
The sections above in this LibGuide contain more information on how to prevent or fix these issues. Open a ticket with Chris Doyle in DLI after the first time you use WAVE to verify the ADA health of your guide.