Skip to main content
Link
Menu
Expand
(external link)
Document
Search
Copy
Copied
# Making an Accessible Poster Presenting your work Accessibly with Posters cse482a: Fall 2026; Jennifer Mankoff (Last Edited: 2026-11-23).
Live View: /slides/poster.html
Important Reminder: check zoom & captioning
---
Outline
Making an Accessible Poster
(Slide 3)
--- class: center, middle, inverse # Making an Accessible Poster Due **the morning of Monday, Dec 7** (we print that day). Session: **Wed, Dec 9**. --- ## What you already have Most of your poster content exists from earlier milestones: - **Users** and a quote: Milestone 1 - **Lofi prototype** and what you learned: Milestone 2 - **Study findings**: Milestone 3 - **Final application**: screenshots and technical details after Milestone 4 Demo Day (Dec 2) Start now. Build the poster from these. Add the final app last. --- ## What goes on the poster 1. Title, group members, mentor, class 2. Users: who, what you learned about their access needs, at least one quote 3. Lofi prototype: pictures, what you learned 4. Final application: screenshots, technical details 5. Justice-centered design: intersectionality, possible harms 6. What you learned, and "Ask me about..." prompts Minimize text. --- ## Size and format - **32 x 40** inches. Start from a [CSE template](https://internal.cs.washington.edu/lab/printing/poster-printer/) - Suggested text sizes: title 158 pt, section headings 56 pt, body 36 pt, captions and footnotes 24 pt - Sans serif fonts, plain backgrounds, generous white space - Check contrast for **printed** colors, not just on screen - Use high-resolution images or vector graphics --- ## Accessible poster checklist - Follow [DO-IT's guide to accessible posters](https://doit.uw.edu/knowledge-base/how-can-i-create-a-conference-poster-that-is-accessible-to-people-with-disabilities) - **A QR code next to each image** that links to its alt text - Alt text on every image in the **source file** - Real headings and lists in the source, not just big text - Include a QR code or short URL for an accessible, downloadable version You are graded on the Accessible Communication competency, using the same guidelines as your documents. --- ## What we will look at - The quality of your setup - How you introduce your project - How finished your prototype is, technically and as a design - How finished your poster is, as a design --- ## What to hand in (Mon morning, Dec 7) - Poster **source file** (PowerPoint or Google Slides), for the accessibility check - A **PDF** for printing - Share it with your mentor We print on Monday. We can't fix problems after it is printed, so check your poster *before* you hand it in: the final app is due Wed, Dec 2, so you have the weekend. --- ## Presenting accessibly - Describe the images you point to - Keep a notepad to pass notes back and forth - Be patient, and don't assume someone is uninterested - Don't expect people to read while you are talking: *present* it - Bring your demo on a laptop next to the poster - More on presenting and visuals: [Accessible Presenting and Document Accessibility](presenting.html) --- class: center, middle, inverse # Your pitch --- ## Communication is telling a story - A short prepared speech: the **why** and the **how** - Maximum 30 seconds - Before you say something, ask: *what is this adding to the story?* --- ## Using your poster and prototype - **Show**, don't just tell: anecdotes, examples, quotes - Think about who you are presenting to, and what their purpose is - Present accessibly --- ## In your team (about 15 minutes) 1. Write down the main need or problem you found in your user research 2. In 1-2 sentences, how does your prototype address it? (If you pivoted, what need does it address now?) 3. Write a pitch: **30 seconds or less**. Start with the need (numbers help: "More than 80% of CS students feel...") 4. **Red pen it**: cut anything unnecessary, including jargon --- ## Try it on another team Show off your pitch and collect feedback. Add the notes and the pitch to your `LOG.md`.