Best Practices
Some Basic Best Practices
(Note: This is not legal advice. Review the WebAIM's WCAG checklist for more guidance.)
Headings
Creating headings in web content breaks your content into sections so that it is easily readable by site users.
- Simply bolding text is not creating accessible headings - using a structure of headings allows screen readers to scan the page and quickly review the page content just as a sighted person would.
- Do not use subheadings on text that you simply want to “stand out” on the page – this is when you would use bold.
- Tip: If you read through the subheadings, does the document flow logically?
Underlines
Underlined text should be reserved for hyperlinks.
Website Links
A screen reader will read the link text to a user. Using the full URL, particularly long URLs, lead to the screen reader reading a long string of letters and numbers. Be sure to use link text that identifies where the link is taking a user.
Create meaningful links: Do not use the words “click here”, “read more”, etc. as your only linked text.
Tip: If you read the link out of context (without reading the surrounding paragraph), does it make send where the link is sending the user?
Try to include as little words as possible in the link text, but enough so that the link makes sense when read separately from the surrounding text.
When linking to a PDF, include “PDF” at the end of the link.
Images
Label with alt text that accurately describes what the image shows.
- If an image is purely decorative, mark the image as decorative so that screen readers will skip reading them (=””).
Bullet & Numbered Lists
Use bullet points and numbered lists; typing the number 1, 2, 3 is not read the same by a screen reader as is a formatted list.
Tables
Tables should have labeled columns and row headers.
Videos
Caption videos or provide written transcripts.
Color
- Do not rely solely on color to communicate information.
- Ensure that a proper color contrast ratio is maintained so that text is readable.