LibGuides Standards & Best Practices: Accessibility Guidelines

• 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.
  • LibGuides uses h1 for page titles and h2 for box titles. Any headings you add inside a box should start with h3.
• 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.
• Make sure your content is clearly written and easy to read. Get more tips on writing clearly and simply.

• 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. Learn more about providing appropriate alternative text.
• 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. Learn more about creating accessible tables.
• 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.

• Add caption and/or provide transcripts for media. For guidelines and resources to create video caption and transcripts, see Create Accessible Captions and Transcripts (section508.gov)
• 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. Learn more about creating accessible Word documents and creating accessible PDF files.

Source: The above information comes from WebAIM’s Principles of Accessible Design. This 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. The US Government also maintains an accessibility resource guide.