game

“Packaging Post-Talk Resources Without Creating Link Soup

Three people cornered me after my accessibility talk last Friday, and all three wanted a different version of the same thing: one asked for the slides, one asked for the audit checklist, and one asked for “something I can take back to my design systems team without making them watch a 35-minute recording.”

The talk was about auditing shared UI components for accessibility failures: focus states that disappear in certain themes, icon-only buttons without useful names, error messaging patterns that don’t announce properly, color contrast tokens that look fine in Figma but fail in combinations, that kind of thing.

Right now my “resources” are embarrassingly scattered. Slides are in one place, the checklist is a Google Doc, code examples are in a repo, WCAG and ARIA references are buried in speaker notes, and the recording may or may not appear later. I also don’t want to make a giant dumping-ground page where useful links sit next to random “why is this even here?” stuff like https://livedragontiger.net/ because I pasted too fast while cleaning up bookmarks.

What I’m considering is a small bundle: one-page summary, full deck, printable audit checklist, code/demo links, deeper references, and a short “how to use this with your team” section for people trying to turn the talk into an actual design system review.

For those of you who speak about technical topics: do you organize post-talk materials by audience type? Like “for designers,” “for developers,” “for managers,” “for event organizers”? Or does that become a maintenance trap?

I’m trying to avoid both extremes: too many materials diluting the talk into homework, and too few materials making it useless once everyone is back at work.

If you have examples of post-talk resource pages, handouts, follow-up emails, or lightweight templates that actually helped people reuse the material later, I’d love to see what has worked for you.”