Accessible Document Creator
FerroxLabs/wayland
Create accessible PDF, Word, PowerPoint, and email documents with proper structure, reading order, alternative text, and compliance with PDF/UA, WCAG, and Section 508 standards.
Scan and fix PDFs: PDF/UA, Matterhorn checks, tags and reading order.
Install PDF Accessibility
$ npx skills add Community-Access/accessibility-agents --skill pdf-accessibility -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents pdf-accessibility --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pdf-accessibility .claude/skills/pdf-accessibility && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pdf-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/pdf-accessibility into .claude/skills/pdf-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pdf-accessibility", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Community-Access/accessibility-agents/tree/main/skills/pdf-accessibilityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Community-Access/accessibility-agents --skill pdf-accessibility -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents pdf-accessibility --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pdf-accessibility .agents/skills/pdf-accessibility && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pdf-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/pdf-accessibility into .agents/skills/pdf-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pdf-accessibility", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill pdf-accessibility -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents pdf-accessibility --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pdf-accessibility .cursor/skills/pdf-accessibility && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pdf-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/pdf-accessibility into .cursor/skills/pdf-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pdf-accessibility", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Community-Access/accessibility-agents.git --path skills/pdf-accessibility--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Community-Access/accessibility-agents --skill pdf-accessibility -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents pdf-accessibility --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pdf-accessibility .gemini/skills/pdf-accessibility && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pdf-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/pdf-accessibility into .gemini/skills/pdf-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pdf-accessibility", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Community-Access/accessibility-agents pdf-accessibilityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Community-Access/accessibility-agents --skill pdf-accessibility -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pdf-accessibility .github/skills/pdf-accessibility && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pdf-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/pdf-accessibility into .github/skills/pdf-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pdf-accessibility", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill pdf-accessibility -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Community-Access/accessibility-agents pdf-accessibility --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pdf-accessibility .opencode/skills/pdf-accessibility && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pdf-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/pdf-accessibility into .opencode/skills/pdf-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pdf-accessibility", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pdf-accessibility- GitHub stars
- 422
- Token cost
- ~1.4k tokens
- SKILL.md length
- 623 words
- Files
- 6 (incl. references)
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Scan and fix PDFs: PDF/UA, Matterhorn checks, tags and reading order.
- Works in 7 steps: Always scan before advising - never… → Report rule IDs with every finding for… → Distinguish automated findings from… → …
- Tasks that involve PDF
- SKILL.md covers Native-Tool-First Guidance, Your Scope, PDF Structure Fundamentals and Verification Tools, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
PDF Accessibility is an agent skill from Community-Access/accessibility-agents. Scan and fix PDFs: PDF/UA, Matterhorn checks, tags and reading order.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `agents/openai.yaml`, `examples/findings.json` and `references/remediation-guidance.md`).
It sits in Documents & Office, covering PDF and Accessibility. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.
When your agent uses it
- Tasks that involve PDF
- Tasks that involve Accessibility
Example prompts
- “/pdf-accessibility”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Always scan before advising - never guess at PDF issues
- Report rule IDs with every finding for traceability
- Distinguish automated findings from items needing human review
- For untagged PDFs, recommend rebuilding from source as first option
- Never suggest removing tags to "fix" issues
- Always recommend veraPDF for full PDF/UA conformance verification
- When in doubt about alt text quality or reading order, flag for human review
What it can do on your machine
Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
PDF Accessibility loads about 1.4k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 22 tokens; SKILL.md has 623 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 623 words, ~1,393 tokens.
Download SKILL.mdSave it as
.claude/skills/pdf-accessibility/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- pdf-accessibility
- description
- Scan and fix PDFs: PDF/UA, Matterhorn checks, tags and reading order.
- license
- MIT
- disable-model-invocation
- true
- metadata.tier
- specialist
- metadata.domain
- documents
- metadata.output
- findings
- metadata.effort
- medium
- metadata.title
- PDF Accessibility
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
Common Structure Elements
Each tag, with its meaning and accessibility role.
| Tag | Meaning | Accessibility Role |
|---|---|---|
/Document | Root container | Document landmark |
/P | Paragraph | Text block |
/H, /H1-/H6 | Headings | Navigation landmarks |
/L, /LI, /Lbl, /LBody | List structure | Structured list |
/Table, /TR, /TH, /TD | Table structure | Data table |
/Figure | Image/illustration | Requires /Alt text |
/Link | Hyperlink | Must have text content |
/Form | Form widget | Requires label |
/Artifact | Decorative/non-content | Ignored by AT |
/Span | Inline container | Language changes |
Verification Tools
Show full SKILL.md (258 more words)Show less
Automated
- MCP scan_pdf_document tool - Built-in scanner checking structure, metadata, and tagging
- veraPDF - Open-source PDF/UA validator:
verapdf --flavour ua1 file.pdf - PAC (PDF Accessibility Checker) - Windows GUI tool for PDF/UA validation
Manual Verification Required
These aspects cannot be fully verified by automated tools:
- Alt text quality (describes the meaningful content, not just "image")
- Reading order correctness (visual order matches logical order)
- Color contrast within embedded images
- Table header/data cell relationships in complex tables
- Language changes within mixed-language content
- Form field grouping and instructions
- Meaningful sequence of content
Configuration
Pair with pdf-scan-config to manage which rules are active:
// .a11y-pdf-config.json
{
"enabled": true,
"disabledRules": [],
"severityFilter": ["error", "warning", "tip"],
"maxFileSize": 104857600
}Preset Profiles
- strict - All rules enabled, all severities (recommended for public/government documents)
- moderate - All rules enabled, errors + warnings only
- minimal - Only PDFUA and PDFQ error rules
Behavioral Rules
- Always scan before advising - never guess at PDF issues
- Report rule IDs with every finding for traceability
- Distinguish automated findings from items needing human review
- For untagged PDFs, recommend rebuilding from source as first option
- Never suggest removing tags to "fix" issues
- Always recommend veraPDF for full PDF/UA conformance verification
- When in doubt about alt text quality or reading order, flag for human review
Reference files
Read one only when the task reaches it. Do not read them all up front.
references/rule-layers.md- Rule Layersreferences/remediation-guidance.md- Remediation Guidancereferences/structured-output-for-sub-agent-use.md- Structured Output for Sub-Agent Use, Multi-Agent Reliability
Output contract
Return only JSON matching skills/a11y-core/schemas/findings.schema.json.
No prose, no summary, no restated instructions. One object, one array of findings.
Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md.
Authoritative specifications for this skill: skills/a11y-core/references/sources.md.
© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in skills/pdf-accessibility of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
- examples/findings.json
- references/remediation-guidance.md
- references/rule-layers.md
- references/structured-output-for-sub-agent-use.md
Open the folder on GitHubat commit decf6ba
Compare with similar skills
PDF Accessibility next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| PDF Accessibility this skillCommunity-Access/accessibility-agents | 422 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Accessible Document CreatorFerroxLabs/wayland | 608 | — | ~4.3k | Automated safety check: Pass | Apache-2.0 | |
| Thu Digitizerfranklee16/academic-research-skills | 223 | — | ~8.5k | Automated safety check: Pass | MIT | |
| Minimax PDFpoco-ai/poco-claw | 1.4k | 6 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Openkb HTML CriticVectifyAI/OpenKB | 4.7k | 1 repos | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Frontend Textbooksonepixelaway/frontend-textbooks | 106 | — | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
Thu Digitizer
franklee16/academic-research-skills
Extract and validate numeric data from chart images, PDF figures, and official source-data files locally and reproducibly, with calibrated axes, compact-scatter recovery plus residual audits…
Minimax PDF
poco-ai/poco-claw
A skill your agent uses when visual quality and design identity matter for a PDF.
Openkb HTML Critic
VectifyAI/OpenKB
A skill your agent uses to review a generated HTML deck or single-page artifact for visual quality and structural correctness.
Frontend Textbooks
onepixelaway/frontend-textbooks
Turns a manuscript into a designed US Letter HTML book with a matching PDF, original cover art and checks that the manuscript text is preserved.
Sharepoint Safe HTML
pnp/sharepoint-skills
Creates accessible, single-file HTML artifacts that render reliably in SharePoint, OneDrive, Teams, File Viewer, and embedded iframe preview surfaces.
More from Community-Access/accessibility-agents
All 108 skills in this repoA11y Core
Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.
Kb Web Scanning
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Accessibility Lead
Community-Access/accessibility-agents
Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.
Alt Text Headings
Community-Access/accessibility-agents
Alt text, SVGs, figures, charts, heading order, page titles and landmarks.
Aria Specialist
Community-Access/accessibility-agents
ARIA roles, states and properties for custom widgets and dynamic content.
Cognitive Accessibility
Community-Access/accessibility-agents
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
Related
Categories
Questions about PDF Accessibility
What does PDF Accessibility do?
Scan and fix PDFs: PDF/UA, Matterhorn checks, tags and reading order. PDF Accessibility is an agent skill from Community-Access/accessibility-agents. Scan and fix PDFs: PDF/UA, Matterhorn checks, tags and reading order.
When should I use PDF Accessibility?
PDF Accessibility fits situations like: tasks that involve PDF; tasks that involve Accessibility.
How do I install PDF Accessibility in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill pdf-accessibility -a claude-code`. Or copy the skill folder (skills/pdf-accessibility in Community-Access/accessibility-agents) into .claude/skills/pdf-accessibility in your project. Claude Code loads it when a task matches its description.
How do I install PDF Accessibility in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill pdf-accessibility -a codex`. Or copy the skill folder (skills/pdf-accessibility in Community-Access/accessibility-agents) into .agents/skills/pdf-accessibility in your project. Codex loads it when a task matches its description.
Can I use PDF Accessibility in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill pdf-accessibility -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pdf-accessibility, .gemini/skills/pdf-accessibility, .github/skills/pdf-accessibility and .opencode/skills/pdf-accessibility in your project.
What does PDF Accessibility need to run?
SKILL.md names no scripts, command-line tools or credentials: PDF Accessibility is instructions for the agent only.
Does PDF Accessibility access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is PDF Accessibility safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does PDF Accessibility use?
PDF Accessibility is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does PDF Accessibility use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.6k tokens, read only when the agent opens those files.
What are the alternatives to PDF Accessibility?
Skills that share tags, products or a category with PDF Accessibility: Accessible Document Creator (FerroxLabs/wayland, 608 stars), Thu Digitizer (franklee16/academic-research-skills, 223 stars), Minimax PDF (poco-ai/poco-claw, 1.4k stars) and Openkb HTML Critic (VectifyAI/OpenKB, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PDF Accessibility?
Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 422 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.
Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.