Teachable Accessibility Checklist 2026 | WCAG 2.1 AA & EAA Compliance
Last updated: 2026-04-25
Teachable powers tens of thousands of independent course schools, and most of them are run by solo creators with no developer on staff. That matters for accessibility, because Teachable -- like every closed course platform -- gives you a fixed surface area: a theme, a page builder, a lecture player, a comments thread, a quiz engine, and a checkout. You cannot rewrite the player. You cannot redesign the comments component. You can, however, change the things students actually trip on, and you are the only person legally on the hook when a deaf student cannot follow your lessons or a screen-reader user cannot complete your checkout. Under the European Accessibility Act, which took effect on 28 June 2025, online course schools selling into the EU are explicitly within scope, and under the ADA, U.S. plaintiffs have already filed against course creators on Teachable in California, New York, and Florida. The good news: most of the high-impact remediation on Teachable is content work (captions, transcripts, alt text, plain-language quiz instructions) plus a handful of theme-level CSS and HTML snippet edits in Site > Code Snippets. This checklist walks you through the issues we see in nearly every Teachable audit and the specific fixes that work inside the platform without breaking your theme.
Common Accessibility Issues
Teachable supports SRT/VTT caption uploads on every video lecture, but most creators skip the step. Auto-generated captions from the upload pipeline are not enabled by default and, when enabled in some integrations, are inaccurate enough to violate the spirit of WCAG 1.2.2 (Captions, Prerecorded). Deaf and hard-of-hearing students cannot use lectures without captions, and ESL students who paid full price often refund when no transcript is provided.
Generate captions with a service like Rev (human), Otter.ai, or Descript, then proofread for jargon. In Teachable, edit each lecture, click the video, and upload the .vtt or .srt file under the Captions tab. Turn captions on by default in Site > Theme > Player Settings if available. Also paste a full text transcript into the lecture description so it is searchable and indexable.
Teachable's native quiz engine renders multiple-choice and fill-in-the-blank questions with visible labels but inconsistent programmatic associations. Screen-reader users may hear 'edit text' without context for short-answer fields, and radio-button groups sometimes lack a fieldset/legend pair. This makes graded assessments impossible to complete with assistive technology.
Where you cannot fix the underlying markup, mitigate at the content level: phrase each question so the visible question text and the input are unambiguous when read in sequence. For short-answer questions, prepend the expected answer format to the question itself ('Type the year as four digits, e.g. 2026:'). File a support ticket with Teachable referencing WCAG 3.3.2 and 1.3.1 to push the platform-level fix; document the request to support a reasonable-accommodations defense if a complaint arises.
Teachable's most-used themes (Colossal, Tribeca) pair pale gray body text on white at roughly 3.2:1, well below the 4.5:1 required by WCAG 1.4.3 for normal text. Hero overlays often place white headlines on light photographs without a darkening layer, dropping contrast as low as 1.8:1. Low-vision learners abandon the sales page before reaching the checkout.
Open Site > Theme > Customize and change body text color to a darker neutral (#1f1f1f or darker on white). For hero sections, add a semi-transparent dark overlay or switch to a solid background. Use the WebAIM Contrast Checker on every text/background pair before publishing. Re-check after any theme update because Teachable occasionally resets custom colors.
The Teachable checkout flow displays placeholder text ('Email', 'Card number') inside fields without visible labels. Once a user begins typing, the placeholder disappears and there is no on-screen reminder of what each field expects. Cognitive-disability users and screen-magnification users cannot recover context after a typo, and assistive technology often fails to announce placeholder text reliably.
Checkout markup is platform-controlled; the practical fix is a small CSS+JS snippet pasted into Site > Code Snippets > Head Code that promotes placeholders to persistent labels via floating-label CSS. If you sell into the EU, escalate the issue to Teachable support citing EAA conformance; settlements with Teachable schools have already begun in 2026 and the platform is responsive when liability is at stake.
Posting a comment in a Teachable lecture page reloads the comment list without moving keyboard focus or announcing the new state to screen readers. Keyboard users are dropped back at the top of the page; screen-reader users hear nothing and assume the post failed, often submitting duplicates.
Add a small Code Snippet that listens for the comment-submit XHR completion and either calls element.focus() on the new comment node or updates an aria-live='polite' region with 'Comment posted.' If you cannot inject JavaScript, write a clear lecture-description note explaining that comments may take a moment to appear and to refresh once if the new comment is missing.
Teachable-Specific Tips
- Use Site > Code Snippets (Head and Footer) to inject accessibility patches the visual editor cannot make: skip links, focus styles, ARIA landmarks, and live regions.
- Always upload .vtt or .srt captions on every video lecture and paste the full transcript into the lecture description so it is keyboard-searchable.
- Test the entire student journey -- sales page, checkout, course player, quiz, comments -- with keyboard only and with VoiceOver or NVDA before launching.
- Avoid Teachable's built-in countdown timers and pop-up coupon offers; they create WCAG 2.2.1 (Timing Adjustable) and 2.2.2 (Pause, Stop, Hide) failures and trigger anxiety for cognitively disabled learners.
- Document every accommodation you offer (transcripts on request, alternative quiz formats) in a public accessibility statement linked from your course homepage.
Recommended Tools
axe DevTools
Browser extension to scan Teachable sales pages, course pages, and the checkout for WCAG violations with prioritized fix guidance.
Rev Captions
Human-generated SRT/VTT captions for course lectures; the most defensible option for WCAG 1.2.2 conformance on technical or jargon-heavy content.
WebAIM Contrast Checker
Free contrast ratio calculator to validate every text/background combination on your Teachable theme before launch.
Further Reading
Other CMS Checklists
Get our free accessibility toolkit
We're building a simple accessibility checker for non-developers. Join the waitlist for early access and a free EAA compliance checklist.
No spam. Unsubscribe anytime.