Free tool

Accessible teaching materials checklist

Check handouts, slides, documents and video against WCAG 2.2 and plain-language good practice, then copy or print a checklist report with fixes. Free and private.

Free tool Updated

Tool at a glance

  • Runs entirely in your browser
  • Nothing is sent or saved
  • Copy, print or download the result
  • Free, no sign-up
Start using the tool
In short

A free checklist of 31 accessibility checks for handouts, slides, documents, video and online course pages, based on WCAG 2.2 and plain-language good practice. Choose what you are checking, mark each item, and get a report of what passes and how to fix the rest.

Private by design. This tool runs entirely in your web browser. Nothing you type is sent to Inclusion Studio or anyone else, and nothing is saved: refreshing or closing the page clears it. If you plan to print or share the result, use a first name or initials rather than full personal details.

Most accessibility problems in teaching materials are quick to fix once you know where to look. This checklist covers the common ones for handouts, slides, documents, video and online course pages. Choose what you are checking, mark each item, and get a report you can keep with the file or share with colleagues.

Check your materials

Optional. For example “Level 2 Plumbing, week 4 slides”.

Type of material

Choose one or more. Only the relevant checks are shown.

Structure and navigation

It has a clear, specific title (for files, also set in the document properties).

WCAG 2.4.2 Page Titled

Headings use the built-in heading styles, in a logical order.

WCAG 1.3.1 Info and Relationships; 2.4.6 Headings and Labels

Every slide has a unique title.

WCAG 2.4.6 Headings and Labels

Lists and tables use real list and table formatting, and tables have a header row and are not used for layout.

WCAG 1.3.1 Info and Relationships

The reading order is correct when read by a screen reader.

WCAG 1.3.2 Meaningful Sequence

Link text makes sense on its own, such as “assessment guidance” rather than “click here”.

WCAG 2.4.4 Link Purpose (In Context)

The language of the document is set correctly.

WCAG 3.1.1 Language of Page

Images, colour and text

Images that carry meaning have alternative text, and decorative images are marked as decorative.

WCAG 1.1.1 Non-text Content

Charts and diagrams have their key information in the text or a description too.

WCAG 1.1.1 Non-text Content

Text has enough contrast with its background: at least 4.5 to 1, or 3 to 1 for large text.

WCAG 1.4.3 Contrast (Minimum)

Colour is not the only way information is shown, for example “red items are required”.

WCAG 1.4.1 Use of Color

Instructions do not rely only on shape, size, position or sound, such as “the box on the right”.

WCAG 1.3.3 Sensory Characteristics

Text is real text, not a picture of text (except logos).

WCAG 1.4.5 Images of Text

Fonts are clear and a readable size, text is left aligned rather than justified, and there is space between lines.

Good practice (see also WCAG 1.4.8 Visual Presentation, level AAA)

Plain language

Sentences are short and use everyday words. Technical terms are explained the first time they appear.

Plain language good practice (see also WCAG 3.1.5 Reading Level, level AAA)

The most important information comes first, and tasks or deadlines are easy to find.

Plain language good practice

Slides are not overloaded with text, and anything said but not shown is also available in notes or a handout.

Good practice

Video and audio

Pre-recorded videos with sound have accurate captions, checked and corrected, not just raw automatic captions.

WCAG 1.2.2 Captions (Prerecorded)

Audio-only content, such as podcasts, has a transcript.

WCAG 1.2.1 Audio-only and Video-only (Prerecorded)

Important visual information in videos is described in the narration, an audio description or a text alternative.

WCAG 1.2.3 and 1.2.5 Audio Description

Live online sessions have live captions.

WCAG 1.2.4 Captions (Live)

Nothing flashes more than three times a second, and moving or auto-advancing content can be paused.

WCAG 2.3.1 Three Flashes or Below Threshold; 2.2.2 Pause, Stop, Hide

Audio does not play automatically, or can be stopped straight away.

WCAG 1.4.2 Audio Control

Online pages and interactive content

Everything can be used with a keyboard alone, and you can always see where the keyboard focus is.

WCAG 2.1.1 Keyboard; 2.4.7 Focus Visible

The focused item is not hidden behind sticky headers, banners or pop-ups.

WCAG 2.4.11 Focus Not Obscured (Minimum), new in WCAG 2.2

Buttons and links are big enough, or spaced enough, to tap easily (at least 24 by 24 CSS pixels).

WCAG 2.5.8 Target Size (Minimum), new in WCAG 2.2

Content works when zoomed to 400% or on a narrow screen, without scrolling in two directions.

WCAG 1.4.10 Reflow

Form fields, including fillable PDFs and online quizzes, have clear labels and instructions.

WCAG 3.3.2 Labels or Instructions

Format and sharing

The document was made from an accessible source, such as a styled Word document, and exported as a tagged PDF or shared as an editable file or web page.

Good practice

You have run the built-in accessibility checker and fixed the issues it found.

Good practice

Materials are shared in advance where possible, in a format learners can adapt, such as changing font, size or colours.

Good practice

How do I use the accessible materials checklist?

  1. Open the file you are checking next to this page.
  2. Choose the type of material. The list changes to show only the checks that apply.
  3. Mark each check as done, not yet or not applicable. Each one shows the WCAG 2.2 success criterion it relates to, or says when it is good practice rather than a WCAG requirement.
  4. Create the report. It lists what passes and gives a short fix for everything marked “not yet”. Copy it into your team’s notes, or print it to keep with the course file.

Many checks take seconds: setting the document title, running the built-in accessibility checker, or turning on captions. Start with those, then work through the rest.

Why do accessible materials matter?

Accessible materials help disabled learners, and they usually help everyone else too. A clearly structured handout is easier for a screen reader user to navigate, and also easier for a tired learner skimming it on a bus. Captions help deaf learners and learners watching in a noisy workshop. Plain language helps learners with dyslexia and learners working in an additional language.

It is also about duties. The Equality Act 2010 includes an anticipatory duty: providers should think in advance about what disabled learners might need, rather than only reacting to individual requests. Accessible materials by default reduce the number of individual adjustments you need to make. Public sector bodies covered by the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 also have specific duties for websites, apps and many documents published on them; GOV.UK explains what is covered. See the guide to accessible teaching materials and the glossary entry for the anticipatory duty.

How does WCAG 2.2 apply to documents and slides?

WCAG 2.2 is the current W3C recommendation, published in October 2023. It is written for web content, so not every success criterion maps neatly onto a Word document or slide deck. The W3C publishes separate guidance on applying WCAG to non-web documents and software. In practice, the checks that matter most for documents and slides are structure, alternative text, contrast, colour, link text and reading order, which this checklist covers. For online course pages and learning platforms, the full set of criteria applies, including the new WCAG 2.2 criteria on focus visibility and target size. The WCAG 2.2 for education software guide covers this in more depth.

What are the limits of this checklist?

It covers common, high-impact issues, not every WCAG success criterion, and it relies on your own judgement. It is not a formal audit or conformance claim. Automated checkers miss many problems, and so do checklists. The most reliable test is to ask learners who use assistive technology, and to try the material yourself with a screen reader, keyboard only or high zoom. If a learner needs a specific format, such as Braille or a modified layout, that is an individual adjustment to agree with them; the adjustment ideas finder can help you prepare for that conversation.

How does Inclusion Studio approach accessibility?

Accessibility matters in our own product too, because learners will use Inclusion Studio to see their plans and give their views, not only staff. The product is in development, and our accessibility statement says honestly what has and has not been tested yet. See our accessibility statement and accessibility features.

Frequently asked questions

Do teaching materials have to meet WCAG 2.2?

It depends on the organisation and the content. Public sector bodies covered by the 2018 accessibility regulations must make websites, apps and many documents published on them accessible, measured against WCAG. Separately, the Equality Act 2010 expects providers to anticipate the needs of disabled learners. Check the GOV.UK guidance for what applies to you.

Does passing this checklist make a document fully accessible?

No. It covers the most common issues, but it is not a full WCAG audit. Testing with assistive technology and, best of all, asking learners who use it, will find things a checklist cannot.

Is a PDF accessible?

A PDF can be accessible if it is properly tagged and made from an accessible source, but many are not. An editable document or web page is often easier for learners to adapt with their own settings and tools.

What is new in WCAG 2.2?

WCAG 2.2 added success criteria including focus not obscured, target size, consistent help, redundant entry and accessible authentication. It also removed the parsing criterion. Most checks for documents and slides are unchanged from WCAG 2.1.

Sources and further reading

Official guidance changes. Check the source before relying on any detail, and take professional advice for individual cases.

Want this as a joined-up process?

Inclusion Studio is learner support software in development for England FE colleges and apprenticeship providers. We are looking for pilot partners to shape it with us.