Thinkific Accessibility Checklist 2026 | WCAG 2.1 AA & EAA Compliance
Last updated: 2026-04-25
Thinkific is the second-most common platform we see in course-creator audits after Teachable, and the accessibility profile is similar but not identical: Thinkific gives you a more flexible Site Builder, a Liquid-templated theme layer (TCommerce themes), and slightly better default focus styles, but the same closed lesson player and a community module that has its own keyboard-trap problems. The legal exposure is the same as any other course platform. Under the European Accessibility Act, in force since 28 June 2025, course schools selling to EU consumers must conform to EN 301 549 / WCAG 2.1 AA on every consumer-facing surface, and under U.S. ADA Title III the demand-letter trend that started with retail in 2018 has now firmly reached the digital-education market. The good news is that Thinkific exposes more theme-level customization than Teachable -- you can edit Liquid snippets, override CSS, and inject custom code globally -- so you have more leverage to fix issues without waiting on the platform. This checklist focuses on the issues we find in nearly every Thinkific audit and the specific places in the admin where you fix them, so you can work through it in an afternoon without engaging a developer.
Common Accessibility Issues
Thinkific supports caption uploads on every video lesson and integrates with Wistia and Vimeo, but creators commonly skip captioning or rely on auto-generated captions that have not been proofread. Without accurate captions, deaf and hard-of-hearing students cannot follow the lesson, and the course is non-conforming with WCAG 1.2.2.
Order professional captions from Rev or 3PlayMedia, or generate a draft with Otter/Descript and proofread word-for-word. In Thinkific, edit each video lesson, scroll to the captions section, and upload the .vtt or .srt file. For Wistia or Vimeo embeds, attach captions in the source platform and verify the player loads them by default. Add a downloadable transcript link in the lesson description.
Thinkific's Site Builder lets you drop section components in any order, and each section ships with its own heading. As a result, most Thinkific homepages have several H1s and skip from H1 to H3 with no H2, which breaks the document outline that screen-reader users navigate with.
Audit the page outline with the WAVE extension or HeadingsMap. Set exactly one H1 per page (typically the hero) and demote subsequent section headings to H2 or H3 to keep a logical hierarchy. For sections without a Heading Level option in the Site Builder UI, override the heading tag in the section's Liquid template by editing the theme code at Theme Library > Edit Code.
Thinkific quizzes render radio buttons and text inputs with custom styling that removes the browser default focus ring. Keyboard-only learners cannot tell which option is selected as they tab through, especially on multi-question pages where the only visual cue is a subtle color change.
Add a global CSS override in Settings > Site > Code & Analytics > Site Footer Code (wrapped in a style tag). Restore visible focus on quiz inputs with a rule like input:focus, .question__option:focus { outline: 3px solid #0057B7; outline-offset: 2px; } and verify it on every quiz template. Tab through a sample quiz and confirm the focus indicator is visible against every background color in your theme.
Thinkific's order form shows inline errors when a student submits with missing or invalid fields, but the error text appears without role='alert' and without programmatic association to the offending field. Screen-reader users hear nothing and assume the form submitted; sighted keyboard users have to scroll back up to find the red text.
Inject a small JavaScript snippet via Settings > Site > Code & Analytics > Site Footer Code that watches for the error elements and assigns role='alert' plus aria-describedby links between fields and their error nodes. As a content-level mitigation, document the order-form requirements (which fields are required, what coupon code format you expect) in the page above the form so users can avoid errors in the first place.
The Thinkific Communities post composer opens in a modal that does not return focus to the triggering element when closed and, in some themes, traps focus inside the rich-text editor with no keyboard exit. Keyboard-only and screen-reader users get stuck and have to refresh the page.
Until Thinkific patches the modal at the platform level, add a small focus-management script via Site Footer Code that listens for the modal's open and close events and moves focus appropriately (focus the close button on open; focus the trigger on close). Also publish a community guideline that the post composer can be exited with Escape, and provide an alternative posting flow (an email-to-post inbox) for users who cannot use the modal.
Thinkific-Specific Tips
- Use Settings > Site > Code & Analytics for global CSS and JavaScript injections; use Theme Library > Edit Code for Liquid template overrides on a per-section basis.
- Caption every video lesson and provide a downloadable transcript; treat this as non-negotiable for any course sold into the EU under the EAA.
- Avoid the carousel hero section in default themes (it auto-rotates and fails WCAG 2.2.2); replace with a static hero or one with explicit pause controls.
- Test course playback, quizzes, the order form, and the community composer with keyboard only and with NVDA or VoiceOver every time you change themes or update the platform.
- Publish an accessibility statement at /accessibility-statement that lists known limitations, contact information, and your remediation roadmap; this is required for EAA conformance and helps in defending against ADA demand letters.
Recommended Tools
WAVE Browser Extension
Free in-page accessibility evaluator that flags missing alt text, contrast failures, heading-order errors, and ARIA misuse on Thinkific pages.
3PlayMedia
Professional captioning and transcript service with Wistia and Vimeo integrations, useful for the most common Thinkific video stacks.
HeadingsMap
Browser extension that visualizes the heading hierarchy on a Thinkific page so you can spot skipped levels and duplicate H1s.
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.