Best Practices for Subject/Course/General LibGuides at USF

Accessibility Guidelines for Text

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.

  • Use clear fonts:Don't mix different font types. Stick to the default font (Sans Serif).
  • Use bold, color, italics, and ALL CAPITAL LETTERS, etc. sparingly; each has its own function.
  • Don't use underlines for emphasis. Users will think an underline is a hyperlink.
  • Use real text rather than text within graphics.
  • Use headings and lists appropriately. Headings, lists, and other structural elements provide meaning and structure to web pages. They can also facilitate keyboard navigation within the page.
  • Do not rely on color alone to convey meaning or importance. That information may not be available to a person who is colorblind and it will be unavailable to screen reader users.
  • Ensure proper contrast between the font and the background. Optimize font color use for readability and accessibility.

Accessibility Guidelines for Graphics, Table and Links

  • All Images need to have alternate text (ALT tags) included. Alternative text provides a textual alternative to non-text content (such as graphics or images). It is especially helpful for people who are blind and rely on a screen reader to have the content of the website read to them.
  • Tables should have appropriate table headers. Data cells should be associated with their appropriate headers, making it easier for screen reader users to navigate and understand the data table.
  • Make sure linked text makes sense out of context. Screen reader users may choose to read only the links on a web page. Certain phrases like “click here” and “more” must be avoided.

Accessibility Guidelines for Media and Other non-HTML Content

  • Add caption and/or provide transcripts for media. 
  • Ensure accessibility of non-HTML content. If you cannot make it accessible, consider using HTML instead or, at the very least, provide an accessible alternative. 

Standards and Accessibility