Making Your Academy Accessible: A Guide for Admins and Content Authors

Thought Industries builds the learner interface to be accessible and is working toward WCAG 2.2 AA (see Accessibility at Thought Industries for current status). Full accessibility also depends on how you set up your academy and build your content. This guide covers the steps you can take so your design, content, and interactive elements work for every learner, including those who use assistive technologies.


Design your academy for visual accessibility

Accessible design starts with your academy's foundation: colors, layout, and typography.

Who this helps: learners with low vision, color blindness, or other visual disabilities, who rely on good contrast and cues that don't depend on color alone.

Use high-contrast colors

WCAG 2.2 AA requires a contrast ratio of at least 4.5:1 for normal text, and 3:1 for large text and interface components such as buttons and form fields. Check the colors you set in Site > Branding and any custom colors in Site Builder with a tool like the WebAIM Contrast Checker. (WCAG 1.4.3 Contrast (Minimum), 1.4.11 Non-text Contrast)

Don't use color as the only cue

For example, don't mark wrong answers in red alone. Pair color with a label, an icon, or text. (WCAG 1.4.1 Use of Color)

Don't rely on sensory characteristics

Instructions like "click the green button" or "see the box on the right" don't work for learners who can't see color or layout. Name the item instead, such as "select Submit." (WCAG 1.3.3 Sensory Characteristics)

Check custom code

If you add CSS or scripts through Site Builder > Custom Code, test that they don't lower contrast, hide focus indicators, or break keyboard navigation.

Tip

Preview your color palette in grayscale to see whether anything depends on color. Light gray text on a white background is a common contrast failure.

Add accessible media and images

Every learner should be able to understand your media, whatever their vision or hearing.

Who this helps: learners who are blind, have low vision, are deaf, or are hard of hearing. They depend on alt text, captions, and transcripts.

Images Video Audio and live events

Alt text is a short written description that screen readers read aloud in place of the image. Add meaningful alt text to every image. (WCAG 1.1.1 Non-text Content)

  • Keep it concise, typically under 125 characters.
  • Don't repeat text that's already next to the image.
  • Don't start with "Image of…". Screen readers already announce that it's an image.

Avoid images of text. Screen readers can't read text in images, and learners can't resize it. Use real text wherever you can. (WCAG 1.4.5 Images of Text)

 

To mark an image as decorative:

  1. Select the image in the editor and open its settings.
  2. Leave the Title field blank.
  3. Click Save.

A blank title gives the image empty alt text (alt=""), which tells screen readers to skip it.

Note

For images uploaded before July 2025, enter a title and save, then edit the image again, remove the title, and save once more.

Tip

Write alt text as if you were describing the image to someone over the phone.

Structure written content

Consistent structure makes content easier for all learners to navigate, and it's essential for learners who use assistive technology.

Who this helps: learners using screen readers, who rely on headings and lists to scan a page and move around it.

Use heading levels in order

Go from Heading 1 to Heading 2 to Heading 3 without skipping levels, and don't choose a level for its size. Apply headings with the editor's format options rather than by making text bold or larger. (WCAG 1.3.1 Info and Relationships, 2.4.6 Headings and Labels)

Use real lists

Use the editor's bulleted and numbered list buttons rather than typing dashes or numbers. Don't put horizontal lines or other non-list content inside a list. (WCAG 1.3.1)

Mark language changes

If part of a page is in a different language, mark that passage with its language (for example, lang="es") in the HTML view so screen readers pronounce it correctly. (WCAG 3.1.2 Language of Parts)

Tip

Listen to your page with a screen reader to hear how the content flows. Free options include NVDA on Windows and VoiceOver on Mac.

Build accessible interactions in the editor

The editor makes content creation easy, but accessibility still depends on how you use it.

Who this helps: learners who use screen readers or keyboards. They need clear labels, meaningful link text, and well-structured markup.

Write descriptive link text

Avoid "click here" and "learn more." Say what the link does or where it goes. When you link to a file, include its type and size, for example "Download the course workbook (PDF, 1.2 MB)." (WCAG 2.4.4 Link Purpose (In Context))

Add labels and table captions

In the editor's HTML view, add an aria-label attribute to links, buttons, or other interactive elements that need more context for screen reader users. Add a <caption> element inside a <table> to describe what the table shows.

Give learners enough time

If you set a time limit on a test, make sure it's long enough for learners who use assistive technology, and offer extra time as an accommodation where you can. (WCAG 2.2.1 Timing Adjustable)

Tip

When you duplicate blocks or pages, check that the headings, labels, and link text still make sense in their new place.

Third-party content and downloadable files

SCORM and xAPI packages

These packages are built in outside authoring tools, so their accessibility depends on how they were created. Check the accessibility options in your authoring tool, and test packages with a keyboard and a screen reader before you publish them.

PDFs and other downloads

Downloadable documents need tagged headings, alt text, and a logical reading order. Most document tools have a built-in accessibility checker. Run it before you upload.

Embedded content

Videos, forms, and widgets embedded from other services follow those services' accessibility standards. Choose providers that support captions and keyboard access.

Who's responsible for what

Thought Industries covers the learner interface itself. The WCAG success criteria below depend on your content and setup, so this is where your choices make the difference.

WCAG success criterion What you're responsible for
1.1.1 Non-text Content Alt text for the images you upload
1.2.1–1.2.5 Time-based Media Captions, transcripts, and audio descriptions for your audio, video, and live events
1.3.1 Info and Relationships Correct headings, lists, and tables in your content
1.3.3 Sensory Characteristics Instructions that don't rely on color, shape, or position alone
1.4.1 Use of Color, 1.4.3 Contrast The colors you choose in Branding, Site Builder, and your content
1.4.5 Images of Text Using real text instead of images of text
2.2.1 Timing Adjustable Reasonable time limits on tests
2.4.4 Link Purpose Descriptive link text in your content
3.1.2 Language of Parts Marking passages in another language

Resources and support

WCAG 2.2 Quick Reference (W3C)

Was this article helpful?
0 out of 0 found this helpful

More resources

  • Academy

    Go from beginner to expert with hands-on training

  • Community

    Ask questions, swap ideas, and learn from people like you

  • Developer Docs

    Reference guides and code samples for developers