This checklist is part of the Universal Design for Modern Course Creators Toolkit, a practical collection of resources designed to help you build learning experiences that are inclusive, effective, and accessible by design. It is intended for course creators, instructional designers, and educators working in digital spaces.
It complements the WAVE Accessibility Scan Guide, which shows you how to identify automated accessibility issues using the WAVE browser extension. While automated scans are useful, they cannot detect every barrier. This checklist focuses on the manual review steps that require human judgment, such as content structure, keyboard navigation, and text alternatives.
If you are looking for additional testing tools and accessibility support platforms, visit the Free Tools for Accessible Online Learning page.
Make sure your text and page layout are easy to read and navigate.
WebAIM Contrast Checker: A quick tool to check if your text and background color combinations meet WCAG contrast standards.
W3C Headings Tutorial: A simple guide to using headings properly so screen readers and users can follow your content structure.
Add descriptions to images and captions to videos so everyone can access them.
WebAIM Alt Text Guide: A detailed explanation of how to write effective and meaningful alt text for images.
Rev.com Caption Guide: A beginner-friendly overview of how to write captions for video content.
Ensure all buttons, links, and forms work for keyboard and screen reader users.
WebAIM Keyboard Navigation Testing: A walkthrough to help you test if your content works without a mouse.
WebAIM Form Accessibility: A guide to making sure all form fields, labels, and errors are accessible.
Check that your website code and mobile design follow accessibility standards.
W3C WCAG Overview: A full explanation of the official Web Content Accessibility Guidelines (WCAG 2.2).
W3C Markup Validator: A free tool to check that your HTML is clean, valid, and well-structured.
Web.dev – ARIA vs. Semantic HTML: Explains when to use ARIA and when it’s better to rely on built-in HTML for accessibility.
© 2025 Kroxie & Co. LLC. All Rights Reserved.