A PowerPoint slide has a structure whether or not the author uses it. Built-in slide layouts place titles, body text, and content in defined placeholders, and those placeholders are what assistive technology reads. Microsoft's guidance is to use the built-in slide designs, which carry inclusive reading order and color choices with them.
For the principles behind accessible documents generally, including structure, alternative text, and reading order, see Accessible Documents. This page covers what is specific to slides.
Text typed into a manually drawn text box sits outside the layout. It appears on the slide, but it is not part of the slide's defined structure, and it is where most presentation accessibility problems begin. Rebuilding a deck onto proper layouts is usually faster than repairing a deck built out of floating boxes.
A slide title is how a reader knows where they are. Screen reader users move between slides by title, so a deck in which several slides are called Overview, or in which title placeholders were deleted for design reasons, offers no way to navigate.
Microsoft's guidance is to give every slide a unique title. Where a visible title would spoil the design, PowerPoint supports positioning the title off the slide so that it remains available to assistive technology without appearing in the presentation. That is the correct solution, and it is far better than deleting the title placeholder.
Titles should also be informative. A meaningful title describes what the slide says rather than what section it belongs to, so that a list of slide titles reads as an outline of the argument.
Slides have no natural reading order. Objects are read in the order they exist in the file, which is usually the order in which they were added, not the order in which a sighted viewer takes them in. A slide with a diagram, three callouts, and a footnote can be read in almost any sequence.
PowerPoint provides a Reading Order pane for setting the sequence in which objects are presented to assistive technology. Checking it on any slide more complicated than a title and a bulleted list is worth the few seconds it takes, and it is the single most valuable check in a deck.
Objects that are purely decorative should be marked so that they are skipped, rather than left in the sequence to be announced between two pieces of content.
PowerPoint supports alternative text on pictures, SmartArt graphics, shapes, groups, charts, embedded objects, ink, and video. As in any document, the description should carry what the object contributes rather than describe its appearance, and decorative objects should be marked as decorative.
Charts and diagrams are the hard case on slides, because they usually carry the point of the slide. A short description cannot convey a full data series, so the finding the chart illustrates should be stated in the slide text or the speaker notes, where it is available to everyone.
Where a table is genuinely needed, the Header Row control in the Table Design tab identifies the column headers, and split cells, merged cells, and nested tables should be avoided. Microsoft's broader guidance is to avoid tables on slides where the same information can be presented another way.
Slides are read in conditions the author cannot control: a projector in a bright room, a laptop screen at an angle, a phone on a train, a printed handout in grayscale. Contrast that is adequate on a designer's monitor frequently is not adequate anywhere else.
Text over photographs is the most common failure, followed by pale corporate palettes applied to body text. Placing text on a solid panel, darkening the image behind it, or moving the text off the image are all reliable fixes.
Color must not be the only way a distinction is made. Chart series identified only by hue, status indicators that are only a colored shape, and instructions that refer to the green box all fail for part of the audience. Labels, patterns, and direct annotation solve it without giving up the color.
Animation that builds a slide one item at a time can help an audience follow a complex point, and it can also break a deck for anyone reading it independently, because content that has not yet appeared may not be available. Decks intended to be read as well as presented should work when everything is visible at once.
Motion itself is an accessibility consideration. Rapid transitions, spinning entrances, parallax effects, and looping animated backgrounds can cause discomfort, nausea, or migraine for people with vestibular conditions. Restraint is the simplest accommodation, and static transitions are rarely missed.
Automatically advancing slides remove the reader's control over pace, which disadvantages anyone reading with magnification, listening to a screen reader, or simply reading more slowly. Manual advance should be the default outside a kiosk setting.
Video embedded in a slide needs captions, and audio needs a transcript, for the same reasons those apply anywhere. PowerPoint supports closed captions, subtitles, and alternative audio tracks for media placed on slides, either embedded or as a separate caption file depending on the edition in use.
Where the video carries information visually that is not described in its own soundtrack, that information needs to reach people who cannot see it, either through description or through the surrounding slide text. Captioning and audio description in depth are beyond the scope of this page.
Autoplaying media creates a specific problem for screen reader users, whose speech output competes with the audio. Media that starts on click, rather than on slide entry, avoids it.
Speaker notes are a genuine accessibility asset and are usually treated as scratch space. Notes that record what the presenter actually said about a slide give a reader the content that the slide only gestured at, and they are available to assistive technology.
Handouts and exported PDF files inherit the structure of the deck they came from. A deck built on proper layouts with real titles, alternative text, and a checked reading order exports to a usable PDF; a deck built from floating text boxes does not. For what happens after that export, see PDF Accessibility.
Sharing slides before a session, rather than afterward, lets people who read slowly, magnify heavily, or use braille follow along in real time rather than reconstructing the session later.
PowerPoint includes an Accessibility Checker, reached through Review and Check Accessibility, which also runs while a deck is being built. It flags missing alternative text, reading order problems, insufficient color contrast, missing slide titles, and table problems, and it removes a whole class of faults quickly.
As with any checker, it reports what a machine can detect. It cannot tell whether a description conveys what the image is there to show, whether the reading order it reports is the order the slide means, or whether a chart's point survives without the chart. A deck that passes the checker can still be unusable, and a deck that fails it is definitely worth fixing.
Much of presentation accessibility happens in the room rather than in the file. Describing what is on screen as part of the delivery, rather than saying as you can see here, gives everyone the content. Reading out the text of a dense slide, or better, not building dense slides, has the same effect.
Recorded and streamed sessions need captions, and automatic captions need review before the recording is published, particularly where names, acronyms, and technical terms are involved. Where a session includes audience questions, repeating each question before answering it is the single most useful habit a presenter can adopt.
For the principles that apply to documents in every format, see Accessible Documents. For decks exported to PDF and for the handouts that come from them, see PDF Accessibility. For authoring in a word processor, see Word Document Accessibility. For what the guidelines are and how conformance levels work, see WCAG Overview. For a general orientation to the subject, see Digital Accessibility, and for further reading across topics, see Resources.
Where a public entity's presentation work is done to meet the Department of Justice's Title II rule for web and mobile accessibility, the required technical standard is WCAG 2.1 Level A and Level AA. WCAG 2.2, the current W3C Recommendation listed in the sources below, is not itself the Title II legal requirement.
Request accessibility services
World Wide Web Consortium: Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation, for the success criteria behind these practices, including those covering contrast, motion, and captions.
World Wide Web Consortium: Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT), W3C Group Note, informative guidance on reading those criteria for documents and software.
Microsoft: Make your PowerPoint presentations accessible to people with disabilities, for the names and behavior of the PowerPoint features described here.
U.S. General Services Administration, federal Section 508 program: guidance on creating and testing accessible presentations.
Last standards review: September 22, 2026. On that date the PowerPoint feature names and guidance described here, including unique slide titles, positioning a title off the slide, the Reading Order pane, alternative text support, the Header Row control, caption and subtitle support, and the Accessibility Checker, were verified against current Microsoft documentation, and the standards statements were verified against current World Wide Web Consortium sources.
This page provides general educational information about presentation accessibility. It is prepared by The Accessibility Clinic Inc. as educational information only. It is not legal advice, and it does not guarantee that any specific website, application, document, or product meets a particular standard or legal requirement. Organizations should evaluate their own obligations in light of their specific circumstances and consult qualified counsel when needed. Standards and regulations change; the last standards review date above indicates when the statements on this page were most recently verified against primary sources.