Free live webinar · Google Docs & Slides accessibility

Document Accessibility: What a Daily Screen-Reader User Wants You to Fix

Headshot of Quintin, smiling, with short reddish-brown hair, a beard, and a blue-and-white checked shirt

Presented by

Quintin Williams

Blind JAWS & NVDA user
Founder, QA11yLabs

A document can look fine to a sighted reader and still stop a blind reader cold. Quintin Williams, who uses a screen reader every day, shows what breaks in Google Docs and Slides, and which fixes matter most for WCAG 2.1 AA.

Date
Time
5:30 PM ET / 4:30 PM CT / 3:30 PM MT / 2:30 PM PT
Length
60 minutes, including live Q&A
Where
Online. The link is emailed after you register.
Register for free

Who this is for

  • Instructional designers and faculty who build course materials in Google Docs and Slides
  • Disability services and accessibility coordinators
  • Digital learning and LMS teams preparing for ADA Title II and WCAG 2.1 AA

Register for free

Registrants get the recording, even if they can't attend live.

What you'll hear, live in Google Docs and Slides

Quintin runs his screen reader on real course documents, so you hear exactly what he hears: first the version that looks fine, then the fixed one.

  • Google Docs and Slides

    Alt text that actually describes

    Hear what a screen reader says for an image with no alt text, with a file name, and with a useful description. Learn when an image should be marked decorative instead.

    WCAG 2.1 1.1.1 Non-text Content (A)

  • Google Docs

    Headings you can navigate

    See how screen-reader users jump through a document by heading, and why bold text or a skipped level breaks that. Learn the fix with Google Docs' built-in heading styles.

    WCAG 2.1 1.3.1 Info and Relationships (A) · 2.4.6 Headings and Labels (AA)

  • Google Docs

    Links that make sense on their own

    Hear a list of “click here” links the way a screen reader reads them, out of context. Learn to write link text that names where it goes.

    WCAG 2.1 2.4.4 Link Purpose (In Context) (A)

  • Google Slides

    Slides that read in the right order

    A screen reader follows the order objects are layered on a slide, not where they appear. Hear a slide read out of order, and learn to fix it with Arrange › Order or let Inkable reorder it.

    WCAG 2.1 1.3.2 Meaningful Sequence (A)

Then he'll fix the same files with Inkable Docs and take your questions.

Prefer to read first? How to make Google Docs accessible for screen readers

About the speaker

Quintin Williams, Founder, QA11yLabs (opens in a new tab)

Quintin is blind and uses the JAWS and NVDA screen readers every day. He runs QA11yLabs, an accessibility consultancy that does WCAG 2.2 audits, VPATs, and remediation.

Quintin Williams on LinkedIn (opens in a new tab)

Webinar questions

Does the webinar cost anything?
No. The webinar is free to attend.
What if I can't attend live?
Register anyway. Everyone who registers gets the recording by email after the session.
How long is it?
60 minutes. Quintin presents for the first 20 to 30 minutes, and the rest is open for questions.
Which WCAG success criteria does the webinar cover?
The examples map to WCAG 2.1 1.1.1 Non-text Content (Level A), 1.3.1 Info and Relationships (Level A), 2.4.6 Headings and Labels (Level AA), 2.4.4 Link Purpose (In Context) (Level A), 1.3.2 Meaningful Sequence (Level A).
Do I need to use Inkable Docs?
No. The examples are in Google Docs and Slides, and the fixes apply whichever tools you use.

Save your spot

Thursday, December 10, 2026, 5:30 PM ET / 4:30 PM CT / 3:30 PM MT / 2:30 PM PT. Free, with the recording sent to everyone who registers.

Register for the webinar