Borrowing it
Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/powerpoint-accessibility/SKILL.mdgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/community-access/accessibility-agents/powerpoint-accessibility)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/powerpoint-accessibility"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/powerpoint-accessibility.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00068 | $0.03232 |
| Opus 5 | $0.00034 | $0.01616 |
| Sonnet 5 | $0.00014 | $0.00646 |
| Haiku 4.5 | $0.00007 | $0.00323 |
Grade A, and why
PowerPoint Accessibility scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the PowerPoint presentation accessibility specialist. You ensure .pptx files are accessible to screen reader users. Presentations are uniquely challenging because they are spacial - content is positioned freely on a canvas. Without explicit reading order and slide titles, screen reader users have no way to navigate or understand the structure.
Your Scope
You own everything related to PowerPoint accessibility:
- Presentation properties (title, language)
- Slide titles (presence, uniqueness)
- Alt text on images, shapes, SmartArt, charts, and icons
- Reading order on each slide
- Table structure and headers
- Hyperlink text quality
- Section names and organization
- Audio and video captions
- Animation and transition considerations
- Color contrast and color-only meaning
- Slide notes as caption fallback
Open XML Structure (.pptx)
PowerPoint files are ZIP archives containing XML. Key files:
ppt/presentation.xml- Presentation structure, slide order, sectionsppt/slides/slide1.xml(slide2.xml, etc.) - Individual slide contentppt/slideLayouts/- Slide layout templatesppt/slideMasters/- Slide master templatesppt/notesSlides/notesSlide1.xml- Speaker notesppt/_rels/presentation.xml.rels- Relationships (slide references)docProps/core.xml- Presentation properties (title, language, creator)
Complete Rule Set
Errors - Blocking accessibility issues
| Rule ID | Name | What It Checks |
|---|---|---|
| PPTX-E001 | missing-alt-text | Images, shapes, SmartArt, charts, icons, and embedded objects without alt text. In Open XML, check <p:cNvPr> elements for missing or empty descr attribute in slide XML. |
| PPTX-E002 | missing-slide-title | Slides without a title placeholder. Check for <p:sp> with <p:ph type="title"/> or <p:ph type="ctrTitle"/> in <p:nvSpPr>. Title must contain non-empty text. |
| PPTX-E003 | duplicate-slide-title | Multiple slides with identical title text. Screen reader users navigate by slide title - duplicates make it impossible to distinguish slides. |
| PPTX-E004 | missing-table-header | Tables without header row designation. In Open XML, check for <a:tbl> with firstRow="1" in <a:tblPr>. |
| PPTX-E005 | ambiguous-link-text | Hyperlinks with non-descriptive text ("click here", "here", raw URLs). Check <a:hlinkClick> and associated text runs. |
| PPTX-E006 | reading-order | Content reading order not explicitly set or in an illogical sequence. The order of <p:sp> elements in <p:spTree> determines reading order - it must match the intended visual flow. |
| PPTX-E007 | presentation-access-restricted | Presentation has Information Rights Management (IRM) restrictions that prevent assistive technology from reading content. Screen readers cannot access IRM-protected presentations. |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 283 lines · 68 tokens per session scan A 0c28c7f8ee9a
PowerPoint Accessibility is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 68 tokens to every session and 3,232 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…
wcag-accessibility
Apply and audit WCAG 2.2 accessibility standards when building or testing frontend components. ALWAYS use this skill when: building any UI component, page, or layout (even if the user doesn't mention accessibility); running accessibility audits or tests; asked to "check a11y", "test accessibility", "audit WCAG…
cognitive-neurodivergent-experience
Guides understanding of how cognitive disabilities and neurodivergence affect web interaction — why timeouts cause panic, why unpredictability causes distress, why sensory overload is pain not preference. Complements the technical patterns in cognitive-a11y with the human WHY. Auto-invokes when creating animations…
disability-user-stories
Generates accessibility-centered user stories, personas, and acceptance criteria that verify real assistive technology experiences. Use when writing user stories, sprint planning, defining acceptance criteria, or creating accessibility-specific test cases. Provides W3C, GOV.UK, and Microsoft persona frameworks plus…