Quick Accessibility Checks

When creating content for the website or D2L (and other tools), be sure to follow these basics:

• Use headings (H2, H3, H4, H5) to separate sections and structure content, and follow the proper heading order.

• Use legible fonts and font sizes.

• Use bullets for lists.

• Use plain, simple language. Avoid using too much jargon or acronyms. 

• Create links properly, and use descriptive link text. For example, “comprehensive 2024 sales report” vs. “learn more.” 

• If including a video, check that it has captions.

• If including images, add alt text. Images should not contain large amounts of text.

• If using a table, make sure it is properly structured.

• If uploading files (PDF, Word, PowerPoint, etc.), make sure they have been through an accessibility check first.

• Use good color contrast. Use the WebAIM Color Contrast Checker to verify your colors are accessible (i.e., if you have text with a colored background).

• Make sure color isn’t the only way you are conveying information.

• Use simple layouts that are easy to navigate and understand.

Cascade-Specific Checks

• Run the page through the built-in accessibility checker (in the Submit to Workflow window).
• Use the Siteimprove integration tool for a deeper dive into accessibility issues and areas of improvement, and to check the reading level.

Some accessibility items are already set up in the CMS, and you don’t have to worry about checking these (unless you are making changes in the code view that would override defaults).

• Color contrast
• Page language
  • (If you are including a section of text in another language, that will need to have the language set on that section. Reach out to web-team@iup.edu for assistance.)
• Appropriate, readable font
• Accessible navigation
• H1 and description
• Form fields
• Reading order