Teaching · Special Education

Can a screen reader user get through the platform alone?

Sign in as a student, turn the screen off and do the real tasks: open an assignment, submit it, take the quiz. The checklist turns what happened into a verdict and a report the vendor can act on.

Start a testWhat you get
$5one-time · every device you sign in on
Buy · $5

Included with Caveat Classroom and Whole-school licenses. Or get it in the Special Education toolkit, $99 for 135 items.

The platform test

One record per platform and setup, dated each time you test. The example is made up.

Loading the form. If nothing appears, turn on JavaScript.

What you get

Teaching · Special Education$5 · included with Classroom and Whole-school licenses

What you finish with
A verdict for the setup tried, the tasks that block a student, and the problems written as vendor report lines tied to WCAG 2.2.
Who it is for
Assistive technology specialists, teachers of students with visual impairments, school technology staff and digital learning coordinators.
Format
Browser checklist. One saved record per platform and setup; printed with its summary or as a blank form; CSV of the problems; export and import a file.
Access
$5 one-time, yours on every device you sign in on; the tool opens once you are signed in with it. Included with Caveat Classroom and Whole-school licenses. Also in the Special Education toolkit ($99) and the Teaching Suite pass ($199), and 1 more bundle. Everything you type stays in this browser; nothing is sent to Caveat.
Where it lives
The Special Education space in Caveat Teaching.
Support
Questions about an order, access or a correction: team@caveatacademic.com.
“button”which one?try every task with the screen dark
Drawn for this page. A screen reader user hears what the code says, not what the screen shows: an unlabeled button is just “button”.

How to use it

  1. Use the screen reader and browser the student actually uses.
  2. Sign in with a student test account, not a staff account.
  3. Turn the screen off, or ask a screen reader user to test with you.
  4. Do each task to the end: submitting means hearing it was received.
  5. Write each problem in one sentence and pick the success criterion it breaks.

Start a test

What the checklist covers

Tasks, not pages

A platform can pass an automated scan and still leave a student unable to submit work. Testing the tasks a student must finish shows what matters for that student.

Why the success criterion

Vendors fix what they can trace to a standard. Naming the WCAG 2.2 success criterion, such as 4.1.2 Name, Role, Value for an unlabeled button, makes a report specific.

What it is not

This is not a full conformance audit or a vendor accessibility conformance report. It records whether one setup works for students, on the date tested.

Sources

  1. W3C Web Accessibility Initiative. Web Content Accessibility Guidelines (WCAG) 2.2, 2023: success criteria 1.1.1, 1.2.2, 1.3.1, 2.1.1, 2.1.2, 2.2.1, 2.4.3, 2.4.6, 2.5.7, 3.3.1, 4.1.2 and 4.1.3.
  2. W3C Web Accessibility Initiative. Easy Checks and Involving Users in Evaluating Web Accessibility.
  3. U.S. Department of Justice. Final rule on the accessibility of web content and mobile apps of state and local governments (ADA Title II), 2024, adopting WCAG 2.1 Level AA.
  4. WebAIM. Screen Reader User Survey results and Testing with Screen Readers guidance.

The example platform and its problems are made up. Support: team@caveatacademic.com.