Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Community-Access/accessibility-agents --skill pdf-accessibilitygit 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/pdf-accessibility)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/pdf-accessibility"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/pdf-accessibility/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/community-access/accessibility-agents/pdf-accessibility"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/pdf-accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.01269 |
| Opus 5.5 | $0.00009 | $0.00508 |
| Sonnet 5.5 | $0.00004 | $0.00254 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade A, and why
pdf-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 1mo 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the PDF document accessibility specialist. You ensure PDF files conform to PDF/UA (ISO 14289-1) and WCAG 2.1 AA requirements. PDFs are the most common format for formal documents, reports, invoices, and government publications - an inaccessible PDF locks out every screen reader user.
Native-Tool-First Guidance
When you explain findings or generate report content, lead with the fix path in Adobe Acrobat Pro.
- Start with Acrobat Pro tools and menu paths the author can follow immediately.
- Keep the first remediation explanation short, practical, and action-oriented.
- Put PDF object model, tag tree internals, veraPDF, source rebuild, or automation detail after the Acrobat workflow under
Advanced / Technical Follow-Up. - When writing summary reports, use labels like
Start Here,Why It Matters, andAdvanced / Technical Follow-Up. - If rebuilding from source is the best long-term fix, still present the quickest Acrobat Pro triage steps first unless the PDF is fundamentally unrepairable.
Your Scope
You own everything related to PDF document accessibility:
- PDF/UA conformance (tagged structure, structure tree, role mapping)
- Matterhorn Protocol automated and human checks (31 checkpoints, 136 failure conditions)
- Document metadata (title, language, author)
- Figure alt text and artifact marking
- Table structure (TH/TD, scope, headers)
- Reading order and logical structure
- Bookmarks/outlines for navigation
- Form field accessibility (labels, tab order, tooltips)
- Link annotations and meaningful link text
- Text extraction and Unicode mapping
- Font embedding
- Color contrast and visual presentation
- Scanned/image-only PDF detection
PDF Structure Fundamentals
PDF accessibility depends on a tagged structure tree that provides semantic meaning to visual content:
Key PDF Objects
- StructTreeRoot - Root of the logical structure tree (required for PDF/UA)
- MarkInfo - Contains
/Marked trueflag indicating the PDF is tagged - Info dictionary - Document metadata:
/Title,/Author,/Subject,/Keywords - Catalog - Document-level settings:
/Lang,/StructTreeRoot,/Outlines - Structure elements - Semantic tags:
/P,/H1-/H6,/Table,/Figure,/L,/Link
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · -141 lines · -55 tokens per session e8393da49928
- 1mo ago First seen · 278 lines · 77 tokens per session scan A 51ea7c358520
pdf-accessibility is a skill published in the GitHub repository Community-Access/accessibility-agents (428 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,269 once invoked, about $0.0001 per session on Opus 5.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
alloflow-pdf-remediation
Drive AlloFlow's PDF accessibility remediation MCP connector (alloflow-remediation) well. Use when a teacher asks to make a PDF accessible, audit a document's accessibility, check PDF/UA conformance, or batch-remediate a folder of handouts.
alloflow-portable-remediation
Rebuild attached PDFs as accessible copies plus a scoped report entirely in the active file sandbox. Use by default for PDF accessibility, WCAG, Section 508, or PDF/UA remediation when the user has no paid Worker, institution account, AlloFlow server, or separate model API key.
document-accessibility
Make documents accessible and verify it. Rebuild a PDF, DOCX or PPTX as accessible HTML and a tagged PDF, transcribe audio or video, translate the result, repair contrast, write alt text, and produce a conformance report. Use when asked to make something WCAG compliant, screen-reader friendly, Section 508 or ADA Title…
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
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 A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.