A presentation often hides its main point in a chart, a color, or a gesture. A listener may hear “the green one is better” without receiving the information needed to understand the comparison. The practical editing job is to identify what the audience must learn and make that meaning available through the spoken explanation and a usable set of materials.
W3C's guidance on describing visual information encourages planning important visual meaning into the content, rather than treating description as a repair after production. Its remote-meetings guidance also addresses prepared materials. Use these as technical planning references; this article does not certify a deck against a particular accessibility standard. W3C WAI: Description of Visual Information W3C: Accessibility of Remote Meetings
Find the sentence each slide is responsible for
Before changing colors or fonts, write a one-sentence takeaway. For a process diagram, the takeaway might be “The reviewer checks the draft before the team publishes it.” For a chart, it might be “The three categories moved in different directions.” If the presenter cannot explain the main point without pointing at the screen, the slide needs a more deliberate script.
Avoid reading every decorative detail aloud. Describe the information necessary for understanding the argument or completing the task. When a complex visual contains supporting data, provide that data in an accessible companion format so the live explanation does not have to recite an entire spreadsheet.
Replace location-only and color-only references
In a fictional staff briefing, a slide compares three request routes with blue, orange, and gray arrows. “Follow the orange path” is difficult to use without sight of the slide. The presenter can instead say “For a document translation request, use the planned-materials route,” while the slide includes the same text label. Color may reinforce the difference, but the label carries the meaning.
Apply the same test to phrases such as “over here,” “this box,” and “the item at the bottom.” Name the object or step. This improves comprehension for people listening by phone, taking notes, or viewing a small screen as well as for people using assistive technology.
Edit for the real viewing conditions
A slide reviewed on a large desktop display may be shown on a projector or a phone. Check whether the title, labels, and main content remain legible. Reduce competing messages rather than shrinking text to fit. Give an intricate diagram its own explanation or divide it into stages that preserve the relationship between the parts.
Keep the companion material synchronized with the presentation. If an important number or instruction changes, update every version that participants may use. A polished accessible handout containing yesterday's instructions still creates a barrier to doing the right thing.
Run a meaning test
Ask a colleague to listen to the presentation without watching the screen. Can they explain the central point and the requested next action? Then ask someone to review the distributed materials without the narration. Can they locate the same point? These are useful editorial tests, not substitutes for specialist evaluation or testing with relevant assistive technology.
Record failures as specific edits: “Name the two categories aloud,” “Add text labels to the legend,” or “Provide the process as an ordered list.” Finish by checking how the file is delivered and what support a participant can request. The outcome should be a presentation with multiple usable ways to reach its meaning, not a claim that one format serves every person equally.
LOCAL READING AID / NO PERSONAL INPUT
Participation Readiness Map
Choose a work product and the stage of participation. Get a practical plan, focused review questions, and a route to the official source. No personal information is requested.
Read the method without JavaScript
Choose a work product and the stage of participation. Get a practical plan, focused review questions, and a route to the official source. No personal information is requested.
- Boston: Language and Communications Access: Define every participation activity, including questions and follow-up. Assign owners for the venue route, materials, communication arrangements, and live troubleshooting. Check current departmental LCA steps before committing funds.
- Massachusetts Office on Disability: Tips for hosting accessible events and meetings: Test a room question reaching a remote participant and a remote contribution reaching the room. Test shared files, communication supports, and the breakout activity with a participant account. Name who can pause the session and invoke the agreed fallback.
- Massachusetts Office on Disability: Creating accessible digital documents: Confirm the approved audience, required action, version, and owner. Review structure, meaningful links, and non-text content in the editable source. Reopen the exported file and test the actual distribution link.
- Boston: Language Access Information and Services: Separate live conversation needs from written-material needs. Provide the authorized coordinator with the format, activity, timing, and approved materials. Track source edits across every affected language version and delivery format.
- W3C WAI: Understanding Media Alternative (Prerecorded): Inventory what the lesson communicates through speech, sound, and visuals. Review captions for instruction-changing errors and identify visual meaning absent from the audio. Check the player, companion files, version, and support route as one package.
- City of Boston Employee Handbook: Policies and Procedures: Identify whether this is an employee workplace process, a City-program question, or an operational defect. Use the appropriate official channel for personal supporting information. Assign a repair owner and choose a test that matches the reported participation failure.
Choices stay in page memory. No submission, tool storage or URL change. Browser-managed form restoration may behave independently. External source links follow their own policies. Source context checked October 7, 2026.
Sources and scope
Public sources checked October 7, 2026. The exercises and fictional cases are independent editorial work. This publication cannot certify accessibility, decide an accommodation, or act for the City.
- W3C: Accessibility of Remote Meetings: Technical guidance for host, platform and content responsibilities, including hybrid participation. Not a legal ruling.
- W3C WAI: Description of Visual Information: Planning meaningful visual information into audio and description.