slide-accessibilitylisted

# Slide Accessibility ## When to use Use this skill when a deck goes to a public body, a bank, a healthcare or education client, anyone procuring under an accessibility standard, or any audience that includes a screen-reader user. Also use it before a deck is published to a website, because a published `.pptx` or its PDF inherits every defect. Do not use it as a general design pass; contrast and reading order are correctness problems, not taste problems, and `brand-compliance-auditor` covers the rest. ## What it does It runs the deck against the checkable accessibility requirements, fixes them in the file rather than in a separate document, and produces a defect list with what was changed. The output is a remediated deck plus an audit trail a procurement team can accept. ## Method **1. Know which standard you are held to.** In the United States, Section 508 incorporates WCAG 2.0 Level AA; in Europe, EN 301 549 references WCAG 2.1 Level AA and underpins public-sector procurement. Most contracts name WCAG AA. Ask which, and write the answer at the top of the audit. **2. Give every slide a unique title.** It is the primary navigation handle: a screen reader announces it, and Outline view and slide-jump tools use it. Every slide needs one and no two should be identical — three slides called "Agenda" defeat the point. Where the design carries no visible title, hide the placeholder rather than deleting it: with the Accessibility Checker open, the **Accessibility** tab's *Sli