A PowerPoint Accessibility Review Checklist for Faculty

Use this checklist to review a slide deck before sharing it. It is a practical starting point, rather than a complete conformance evaluation or a prediction of how many issues a deck contains.

Structure and navigation

• Give slides meaningful titles and use supported layouts.
• Inspect the object reading sequence; visual stacking does not establish it.
• Check table-header relationships and simplify complex tables where needed.
• Use descriptive hyperlink text and test keyboard activation.

Meaning and presentation

• Provide accurate alternatives for informative images and diagrams, and use the supported decorative treatment when appropriate.
• Provide longer explanations or data for complex charts.
• Check relevant contrast requirements and avoid color-only meaning.
• Choose readable text for the delivery environment; WCAG does not require one universal 18-point body-font minimum.

Media and motion

Review synchronized video captions against the audio and meaningful sounds. Provide necessary visual descriptions, and assess audio-only alternatives separately. An automatic transcript is not a complete media-accessibility result.

Avoid making essential information depend on an animation or a fleeting timed display. Check applicable motion, pause and flashing requirements for the actual material rather than assuming all transitions are prohibited or harmless.

Before distribution

Use the checker available in the installed PowerPoint release and investigate its findings. Test the shared deck in the intended environment. Exported PDF or HTML needs its own review; a source pass cannot establish what survived conversion.

Keep the original and inspect the actual saved output. Combine relevant automated checks with manual review of meaning, reading order, navigation and content preservation. Test important student tasks with the intended reader and assistive technologies. A clean checker report alone does not establish conformance.

Aelira Core is beta software. Supported workflows can apply eligible partial fixes and record outcomes, but some inputs need manual work or cannot produce a downloadable remediated file. Review the actual saved output, unresolved findings and content preservation before publication. Automated scores describe implemented checks rather than accessibility conformance. Inspect the public source and release documentation and evaluate a representative authorized sample before planning a rollout.

For a large collection, measure preparation, checking, corrections and manual fallback on representative decks. This article supplies no verified throughput or time-saving benchmark.