u/a11y-ui

I turned Notebook LM into a pocket guide for accessibility rules when I’m knee-deep in design and don’t want to hunt through documentation. Sharing because it’s saved me time and might help if you also get pulled into technical a11y questions.

Why it works:

  • Fast answers: the model pulls the clause for you and cites the source so you can verify or dive deeper.
  • Saves brain space: I don’t have to memorize tiny, nitty-gritty rules (touch targets, text style overrides, zoom reflows, etc).
  • Keeps momentum: small accessibility checks don’t derail my workflow.

Quick context:

  • I’m the de‑facto accessibility person at my org. Designers and devs come to me with technical questions.
  • That pulls me away from design. Notebook LM gets me to an answer faster so I can get back to work.
  • I shared the Notebook with coworkers. They still come to me with questions, but the tool helped me evangelize accessibility and saves me time.
  • Important caveat: This isn’t a shortcut around learning accessibility. You still need to know what to ask and verify the answers.

Some sources I rely on:

  • W3C - especially “How to Meet WCAG (Quick Reference)” (great single-page source for NotebookLM’s source limits)
  • DesignSystem.digital.gov
  • Penn State Accessibility
  • WebAIM

Anyone else using NotebookLM? Would love to hear about how you're using it and what sources you're using.

u/a11y-ui — 12 days ago