Listed below are common issues to address accessibility in course content. Selecting the drop down will provide an overview of the topic. The link at the bottom of each overview will go to a page that details additional information about the issue, how it aligns to WCAG, recommended actions to address it, and resources specific to the topic.
The Course Accessibility Checklist can be utilized as a guide when working through materials.
All issues do not need to be resolved at once!
Review the 5 Steps to Get Started or watch the Quick Start Guide to Digital Accessibility.
Start with high usage courses and materials.
Remove course files that are no longer in use such as duplicates or outdated files.
Utilize accessibility checkers to assist with remediating existing content:
In Microsoft Word/PowerPoint → Review → Check Accessibility.
In Google Docs/Slides → install and use the Grackle Add-on → Launch Grackle.
In D2L → upload content and review the YuJa Panorama accessibility report.
Review the categories on this page for additional information regarding accessibility issues and solutions.
Contact Instructional Technology & Accessibility Coordinators for additional assistance.
What it is: Readability refers to how easily text can be read and understood by the intended audience, including clear language and formatting.
Why it matters: Good readability ensures all students can access and comprehend course content effectively.
How to fix: Use simple language, easy-to-read fonts, clear headings, and sufficient spacing to make content easier to scan and understand.
Example: Replace stylized, serif fonts with less stylized San-serif fonts.
What it is: Descriptive links use clear, meaningful text that explains the destination or purpose of the link rather than vague phrases like "click here."
Why it matters: This helps users understand the link’s context without reading surrounding content, improving navigation and accessibility.
How to fix: Replace non-descriptive link text with specific descriptions that convey the link’s destination title or function.
Example: Instead of writing "Click Here" write "Elgin Community College Accessibility Page"
What it is: Color contrast ratio measures the difference in brightness between text (or important visuals) and its background to ensure readability.
Why it matters: Sufficient contrast helps users with low vision or color blindness distinguish content easily, improving overall accessibility.
How to fix: Use color combinations that meet WCAG guidelines—typically a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.
Example: Instead of light gray text on a white background, use dark gray or black text to increase contrast and readability.
What it is: Document structure organizes content using headings, lists, and proper markup to create a clear, logical flow.
Why it matters: Proper structure helps screen readers navigate and interpret content correctly.
How to fix: Use built-in heading styles (H1, H2, etc.), add lists for grouped items, and avoid using visual formatting alone to indicate sections.
Example: Instead of using bold text to simulate a heading, apply the actual heading style like Heading 2 for section titles.
What it is: Accessible videos include accurate captions, transcripts, and well narrated descriptions of visual elements to convey all essential information.
Why it matters: Captions and transcripts support users who are deaf or hard of hearing, non-native speakers, or anyone accessing content without sound.
How to fix: Provide synchronized captions, a transcript of spoken content, and audio descriptions if visual elements convey important information not spoken.
Example: A lecture video should include captions for dialogue and key sounds, plus a downloadable transcript summarizing the spoken content.
What it is: Images in digital content should include meaningful alternative text (alt text) that describes their purpose or content.
Why it matters: Alt text allows screen reader users and those with visual impairments to understand the information or context conveyed by the image.
How to fix: Add concise, descriptive alt text for informative images, and mark decorative images as decorative so they are skipped by assistive technologies.
Example: For an image of a bar chart showing enrollment growth, use alt text like "Bar chart showing a 20% increase in enrollment from 2020 to 2025."
What it is: Accessible tables use a simple structure with designated header rows and clear labels to organize data.
Why it matters: Properly marked-up tables allow screen readers to convey the relationship between headers and data cells, making the information understandable.
How to fix: Use the table tools to set header rows, avoid merged or split cells, and include a descriptive caption if needed.
Example: A gradebook table should have a header row labeled "Student Name, Assignment 1, Assignment 2, Final Grade" so screen readers announce each column with its label.
What it is: Accessible PDFs are tagged documents with proper reading order, headings, alt text, and searchable text.
Why it matters: Untagged or scanned PDFs are often unreadable by screen readers, creating barriers for students who rely on assistive technology.
How to fix: Ensure that PDFs are uploaded to D2L as tagged and structured PDFs. Utilize YuJa Panorama to review and adjust PDFs as needed.
Example: Instead of uploading a scanned image of a syllabus, use a properly tagged PDF where students can highlight, search, and navigate using headings.