Create a course-level accessibility audit: checks, exceptions, and remediations.
- User
Create a course-level accessibility audit: checks, exceptions, and remediations.
Assistant
The user wants a "course-level accessibility audit" document. This means they need a framework for checking the accessibility of an online course (likely in an LMS like Canvas, Blackboard, Moodle, D2L, etc.). The document needs three specific sections:
- Checks: What to look for? (Criteria based on WCAG 2.1 AA and best practices).
- Exceptions: What is allowed to be inaccessible? (Unavoidable constraints, specific accommodations).
- Remediations: How to fix the issues found.
Target Audience: Instructional Designers, LMS Administrators, Faculty, or Accessibility Specialists. Tone: Professional, structured, actionable, and clear.
Scope:
- Content: Text, Images, Multimedia, Documents (PDFs/Word/PowerPoint), Navigation, LMS tools.
Drafting the Structure:
- Introduction: Brief overview of the standard (WCAG 2.1 AA) and the scope.
- Section 1: Checks (The Audit Checklist): Group these logically (e.g., General, Visuals, Media, Documents, Interactivity).
- Section 2: Exceptions (What constitutes a valid exception): Define what "exceptions" mean in this context (often temporary or specific to the subject matter).
- Section 3: Remediations (The Fix Plan): How to prioritize and fix issues.
- Reporting Template: A simple way to present findings.
Fleshing out "Checks":
- General: Keyboard nav, color contrast, focus indicators.
- Text: Headings, logical reading order, links (descriptive), fonts.
- Images: Alt text (decorative vs. informative), complex images (charts).
- Media: Captions, transcripts, audio descriptions.
- Documents: PDF accessibility (tags), headings in Word/PPT.
- Tables: Headers, scope, no merged cells (if possible).
- Interactivity/Quizzes: Time limits, accessible question types.
Fleshing out "Exceptions":
- When is an exception okay?
- Legacy content (if a plan exists).
- Third-party vendor tools (sometimes out of the creator's control, though an Equally Effective Alternative Access Plan (EEAAP) is needed).
- Specific fundamental alterations (e.g., a music theory course where hearing is the assessment).
- Password-protected publisher content.
Fleshing out "Remediations":
- Immediate fixes vs. long-term.
- Alt text writing.
- Remediating PDFs ( Acrobat Pro).
- Captioning (YouTube/Rev/3PlayMedia).
- Color contrast tools.
Refining the Output: The user asked for "Checks, Exceptions, and Remediations." I should structure the response clearly around these three headers, perhaps organized by content type.
Self-Correction during drafting: Initially, I might just list WCAG codes. But a course-level audit needs to be practical. Instead of saying "1.1.1 Non-text Content," I should say "Check: Do all images have alt text?" and "Remediation: Add descriptive text."
Crucial addition: A "Risk Level" or "Priority" system is helpful for audits. (High/Critical vs. Low).
Final Plan:
- Overview: Define the standard (WCAG 2.1 AA).
- Module 1: Content & Visuals (Checks & Remediations).
- Module 2: Multimedia (Checks & Remediations).
- Module 3: Documents & Files (Checks & Remediations).
- Module 4: Navigation & Interaction (Checks & Remediations).
- The "Exceptions" Policy: Defining valid vs. invalid exceptions and Equally Effective Alternative Access Plans (EEAAP).
- Summary Table/Template.
Let's write the content. I will make sure to distinguish between Checks (what you test), Remediations (how you fix it), and Exceptions (when you don't have to fix it).
Refining "Exceptions": In an audit, "Exceptions" usually refers to items that fail but are flagged for specific handling (like a third-party tool waiting for a vendor patch), not just "we didn't feel like fixing it." It implies a workaround strategy.
Let's build the response. This is a comprehensive framework for performing a course-level accessibility audit. It is designed for Instructional Designers, LMS Administrators, and Faculty reviewing online or hybrid courses.
This audit is based on WCAG 2.1 Level AA standards (the legal standard for ADA compliance in most educational contexts).
Course-Level Accessibility Audit Framework
Part 1: The Core Checks (The "What")
These are the specific elements you must verify. They are categorized by the type of content usually found in a Learning Management System (LMS).
A. Global Navigation & Structure
Check ID Component What to Check For WCAG Principle G-01 Consistent Navigation Is the course menu consistent across all modules/pages? Is the "Home" link always in the same place? Consistent Navigation G-02 Heading Structure Do pages use true Heading styles (H1, H2, H3) rather than just bold text? Does the hierarchy make sense? Info and Relationships G-03 Reading Order If you tab through the page or use a screen reader, does the content appear in a logical order? Meaningful Sequence G-04 Color Contrast Does all text meet the 4.5:1 ratio against the background? (Use a contrast checker tool). Contrast Minimum G-05 Use of Color Is color used as the only way to convey information? (e.g., "Click the green button" or red text indicating an error). Use of Color B. Images & Visuals
Check ID Component What to Check For WCAG Principle I-01 Informative Images Do all images have descriptive alttext that conveys the content/purpose?Non-text Content I-02 Decorative Images Are decorative images (spacers, borders) marked as decorative (null alt text)? Non-text Content I-03 Complex Images Do charts, graphs, or infographics have a detailed description in the nearby text or a long description tag? Non-text Content I-04 Text in Images Are there images of text? (These should be avoided; actual text should be used). Images of Text C. Multimedia (Audio/Video)
Check ID Component What to Check For WCAG Principle M-01 Captions Do all videos have synchronized, accurate closed captions (CC)? (Auto-generated captions must be edited for accuracy). Captions (Prerecorded) M-02 Transcripts Do audio-only files (podcasts) have a text transcript? Audio-only Alternative M-03 Audio Description For videos where visual action is crucial to understanding, is there an audio description track or a descriptive transcript? Audio Description D. Documents (PDF, Word, PPT)
Check ID Component What to Check For WCAG Principle D-01 Tagged PDFs Is the PDF "Tagged"? (Check Properties or reading order). Untagged PDFs are usually just images of text. Accessibility Support D-02 Bookmarks/TOC Do long documents use Bookmarks (PDF) or Heading Styles (Word/PPT) for navigation? Navigation D-03 Data Tables In tables, are headers identified? Do they avoid merged cells which confuse screen readers? Data Tables D-04 Reading Order In PowerPoint, is the reading order panel checked to ensure elements are read logically, not in the order they were created? Meaningful Sequence E. Interactivity & Assessments
Check ID Component What to Check For WCAG Principle X-01 Keyboard Access Can you navigate all quizzes, interactive elements, and tabs using only the keyboard (Tab, Enter, Space, Arrows)? Keyboard Accessible X-02 Focus Indicator Is there a visible outline (focus ring) around the item currently selected via keyboard? Focus Visible X-03 Time Limits If a quiz has a time limit, can students request an extension or pause? (Or is it strictly enforced without exception?) Timing Adjustable X-04 Link Text Do hyperlinks describe the destination? (Avoid: "Click Here", "Read More". Use: "Review the Syllabus"). Link Purpose
Part 2: Exceptions (When rules don't apply)
There are specific scenarios where strict accessibility compliance is technically impossible or pedagogically distinct. These must be documented.
1. The "Fundamental Alteration" Exception
- Scenario: A music theory course testing students on identifying specific instrument sounds.
- Why it fails: You cannot provide an audio alternative for an audio test.
- Audit Action: Mark as an exception. Ensure the instructions are accessible, but the test material itself cannot be.
2. Third-Party Vendor Inaccessibility (The "VPAT" Gap)
- Scenario: A publisher-supplied homework tool (e.g., Pearson, McGraw Hill) contains inaccessible drag-and-drop questions.
- Why it fails: The instructor or institution cannot edit the code of the vendor's tool.
- Audit Action: Flag the specific content. Document that an Equally Effective Alternative Access Plan (EEAAP) is required (e.g., the Disability Services office must provide a human proctor for that student).
3. Legacy/Archival Content
- Scenario: A PDF scan of a historical handwritten letter from 1850 used in a history class.
- Why it fails: OCR (Optical Character Recognition) cannot read handwriting accurately.
- Audit Action: Mark for remediation via transcription. The original image stays for authenticity, but an accessible text transcript must be provided alongside it.
Part 3: Remediation Strategies (The "Fix")
Once the audit identifies a failure, use these standard remediation protocols.
Priority 1: High Impact / Quick Wins
- Fixing Links: Change "Click Here" to descriptive text. (Done in the HTML editor).
- Color Contrast: Change grey text to black (#000000) on white (#FFFFFF), or change a yellow background to a darker blue.
- Alt Text: Right-click images in the LMS editor to add descriptive text.
- Heading Structure: Highlight text in the editor and change "Paragraph" to "Heading 2" or "Heading 3".
Priority 2: Document Remediation
- Word/PowerPoint: Run the built-in Accessibility Checker (Review > Check Accessibility). Fix missing headings and alt text.
- PDFs (Scanned): Do not use the OCR in Adobe Reader (it doesn't save). Use Adobe Acrobat Pro to "Scan and OCR" > "Recognize Text" > "Settings: ClearScan". Then, verify the reading order using the Accessibility tags panel.
- Complex PDFs: If a PDF is a complex form or brochure, remediate by conversion. Convert it to an HTML page in the LMS instead of posting a PDF.
Priority 3: Media Remediation
- Auto-Captions: If using YouTube/Kaltura/Panopto, go to the captions editor.
- Click "Edit" on auto-captions.
- Do not just accept them. Auto-captions usually lack punctuation and capitalize random words.
- Read while listening to the audio to fix grammar and speaker identification.
Priority 4: Complex Interactivity
- Keyboard Traps: If a student gets "stuck" inside an interactive module (cannot Tab out), this is a coding error.
- Fix: If you cannot code a fix (e.g., you are just the instructor), you must remove that tool or provide a non-interactive alternative (e.g., a downloadable Word doc version of the activity).
Audit Report Template (Example)
Course: BIO 101 - Section 005 Auditor: J. Smith Date: 2023-10-27
Item ID Location/URL Issue Found Remediation Plan Status I-01 Module 2 / Cell Diagram Image has no Alt Text. Add Alt Text describing the nucleus and mitochondria. Fix Required M-01 Module 4 / Lecture Vid Auto-generated captions are inaccurate (95% error rate). Upload corrected SRT file or edit in Kaltura. Fix Required G-04 Syllabus Page Red text on grey background used for "Late Policy". Contrast ratio 3:1. Change text to Dark Blue. Fixed D-03 Module 6 / Lab Data PDF is a scanned image, not searchable. Run OCR in Acrobat Pro. Fix Required X-01 Module 8 / Chem Lab Sim Vendor tool (ChemLab) is inaccessible via keyboard. EXCEPTION: Vendor content. Add note to syllabus for EEAAP contact. Logged/Exception
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.