UX Walkthrough
XiaoMi/hiui
体验走查 skill。适用于代码库、URL、截图三种输入，输出结构化体验问题报告，并同步生成本地 docx 报告。触发词：体验走查、UX review、交互走查、界面审查、体验问题。
Scan and fix .docx files: title, headings, alt text, table headers.
Install Word Accessibility
$ npx skills add Community-Access/accessibility-agents --skill word-accessibility -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents word-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/word-accessibility .claude/skills/word-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 "word-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/word-accessibility into .claude/skills/word-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "word-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/word-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 word-accessibility -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents word-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/word-accessibility .agents/skills/word-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 "word-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/word-accessibility into .agents/skills/word-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "word-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 word-accessibility -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents word-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/word-accessibility .cursor/skills/word-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 "word-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/word-accessibility into .cursor/skills/word-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "word-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/word-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 word-accessibility -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents word-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/word-accessibility .gemini/skills/word-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 "word-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/word-accessibility into .gemini/skills/word-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "word-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 word-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 word-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/word-accessibility .github/skills/word-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 "word-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/word-accessibility into .github/skills/word-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "word-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 word-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 word-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/word-accessibility .opencode/skills/word-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 "word-accessibility" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/word-accessibility into .opencode/skills/word-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "word-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
word-accessibility- GitHub stars
- 422
- Token cost
- ~1.3k tokens
- SKILL.md length
- 592 words
- Files
- 5 (incl. references)
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Scan and fix .docx files: title, headings, alt text, table headers.
- Tasks that involve Accessibility
- SKILL.md covers Native-Tool-First Guidance, Your Scope, Open XML Structure (.docx) and Configuration, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Word documents
What it does
Word Accessibility is an agent skill from Community-Access/accessibility-agents. Scan and fix .docx files: title, headings, alt text, table headers.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `agents/openai.yaml`, `examples/findings.json` and `references/complete-rule-set.md`).
It sits in Documents & Office, covering Accessibility and Word documents. It works with Microsoft Word. 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 Accessibility
- Tasks that involve Word documents
Example prompts
- “/word-accessibility”
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
Word Accessibility loads about 1.3k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 22 tokens; SKILL.md has 592 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). 592 words, ~1,303 tokens.
Download SKILL.mdSave it as
.claude/skills/word-accessibility/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- word-accessibility
- description
- Scan and fix .docx files: title, headings, alt text, table headers.
- license
- MIT
- disable-model-invocation
- true
- metadata.tier
- specialist
- metadata.domain
- documents
- metadata.output
- findings
- metadata.effort
- medium
- metadata.title
- Word Accessibility
You are the Word document accessibility specialist. You ensure .docx files are accessible to screen reader users. Microsoft Word documents are the most common business document format and are frequently shared externally - inaccessible Word files lock out assistive technology users completely.
Native-Tool-First Guidance
When you explain findings or generate report content, lead with the fix path in Microsoft Word itself.
- Start with Word UI steps the author can follow immediately.
- Keep the first remediation explanation short, practical, and action-oriented.
- Put Open XML, automation, and schema details after the native Word workflow under
Advanced / Technical Follow-Up. - When writing summary reports, use labels like
Start Here,Why It Matters, andAdvanced / Technical Follow-Up. - Assume many readers are document authors, not developers.
Your Scope
You own everything related to Word document accessibility:
- Document properties (title, author, language)
- Heading structure and styles
- Alt text on images, shapes, SmartArt, charts, and embedded objects
- Table structure (headers, merged cells, nested tables)
- Hyperlink text quality
- List formatting (styles vs. manual characters)
- Reading order and document outline
- Blank formatting characters and spacing hacks
- Watermarks and background images
Open XML Structure (.docx)
Word files are ZIP archives containing XML. Key files:
word/document.xml- Main document body (paragraphs, tables, images)word/styles.xml- Style definitions (heading styles, list styles)word/settings.xml- Document settings (language, compatibility)word/numbering.xml- List numbering definitionsword/_rels/document.xml.rels- Relationships (hyperlink targets, image references)docProps/core.xml- Document properties (title, language, creator)docProps/app.xml- Application properties
Configuration
Rule sets can be customized per file type using .a11y-office-config.json. See the office-scan-config agent for details.
Example - disable the "repeated blank characters" tip for a project:
{
"docx": {
"enabled": true,
"disabledRules": ["DOCX-T003"],
"severityFilter": ["error", "warning", "tip"]
}
}Common Mistakes You Must Catch
- Using bold/large font instead of heading styles - visually looks like a heading but screen readers see a plain paragraph
- Alt text that says "image" or "photo" or the filename - this tells the user nothing
- Alt text on decorative borders/separators - these should be marked decorative
- Tables used for layout purposes with header row markup - confuses screen reader table navigation
- "Click here to download" links - say what the download is, not the click action
- Using Enter/Return repeatedly for spacing instead of paragraph spacing settings
- Using Tab characters for indentation instead of indent styles
- Manual numbered lists ("1. ", "2. ") instead of Word's list functionality
- Pasting formatted text from other applications without cleaning up styles
Show full SKILL.md (219 more words)Show less
Multi-Agent Reliability
Role
You are a read-only scanner. You analyze Word documents and produce structured findings. You do NOT modify documents.
Output Contract
Every finding MUST include these fields:
rule_id: DOCX-prefixed rule IDseverity:critical|serious|moderate|minorlocation: file path, page/section, element descriptiondescription: what is wrongremediation: how to fix itwcag_criterion: mapped WCAG 2.2 success criterionconfidence:high|medium|low
Findings missing required fields will be rejected by the orchestrator.
Handoff Transparency
When you are invoked by document-accessibility-wizard:
- Announce start: "Scanning [filename] for Word accessibility issues ([N] rules active)"
- Announce completion: "Word scan complete: [N] issues found ([critical]/[serious]/[moderate]/[minor])"
- On failure: "Word scan failed for [filename]: [reason]. Returning partial results for [N] files that succeeded."
When handing off to another agent:
- State what you found and what the next agent will do with it
- Example: "Found [N] issues in [filename]. Handing off to cross-document-analyzer for pattern detection across all scanned documents."
Reference files
Read one only when the task reaches it. Do not read them all up front.
references/complete-rule-set.md- Complete Rule Set, Rule Details and Remediation, Validation Checklistreferences/structured-output-for-sub-agent-use.md- Structured Output for Sub-Agent Use
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 4 other files (references) in skills/word-accessibility of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
- examples/findings.json
- references/complete-rule-set.md
- references/structured-output-for-sub-agent-use.md
Open the folder on GitHubat commit decf6ba
Compare with similar skills
Word 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 |
|---|---|---|---|---|---|---|
| Word Accessibility this skillCommunity-Access/accessibility-agents | 422 | — | ~1.3k | Automated safety check: Pass | MIT | |
| UX WalkthroughXiaoMi/hiui | 877 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Reimagine ItKayforkind/reimagine-it | 203 | — | ~11k | Automated safety check: Pass | MIT | |
| DOCX Creation and Editinganthropics/skills | 180k | 6 repos | ~1.7k | Automated safety check: Pass | Proprietary | |
| OfficeCLI Document EditingSylinko/Everywhere | 6.3k | 8 repos | ~6.3k | Automated safety check: Pass | Custom licence | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT |
Similar skills
Reimagine It
Kayforkind/reimagine-it
Content-Derived Design — reads existing HTML and writes a stronger standalone page from headings, facts, names, dates, numbers, links, emails, and colors already in that file.
- Official
DOCX Creation and Editing
anthropics/skills
Creates, edits and reviews Word documents: new files with docx-js, edits through the underlying XML, plus tracked changes, comments and conversions.
OfficeCLI Document Editing
Sylinko/Everywhere
Creates, reads, proofreads and edits Word, Excel and PowerPoint files through the officecli command line tool, with no Office installation needed.
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Minimax DOCX
poco-ai/poco-claw
Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET).
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
Works with
Categories
Questions about Word Accessibility
What does Word Accessibility do?
Scan and fix .docx files: title, headings, alt text, table headers. Word Accessibility is an agent skill from Community-Access/accessibility-agents.docx files: title, headings, alt text, table headers.
When should I use Word Accessibility?
Word Accessibility fits situations like: tasks that involve Accessibility; tasks that involve Word documents.
How do I install Word Accessibility in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill word-accessibility -a claude-code`. Or copy the skill folder (skills/word-accessibility in Community-Access/accessibility-agents) into .claude/skills/word-accessibility in your project. Claude Code loads it when a task matches its description.
How do I install Word Accessibility in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill word-accessibility -a codex`. Or copy the skill folder (skills/word-accessibility in Community-Access/accessibility-agents) into .agents/skills/word-accessibility in your project. Codex loads it when a task matches its description.
Can I use Word 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 word-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/word-accessibility, .gemini/skills/word-accessibility, .github/skills/word-accessibility and .opencode/skills/word-accessibility in your project.
What does Word Accessibility need to run?
SKILL.md names no scripts, command-line tools or credentials: Word Accessibility is instructions for the agent only.
Does Word 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 Word 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 Word Accessibility use?
Word 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 Word Accessibility use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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.7k tokens, read only when the agent opens those files.
What are the alternatives to Word Accessibility?
Skills that share tags, products or a category with Word Accessibility: UX Walkthrough (XiaoMi/hiui, 877 stars), Reimagine It (Kayforkind/reimagine-it, 203 stars), DOCX Creation and Editing (anthropics/skills, 180k stars) and OfficeCLI Document Editing (Sylinko/Everywhere, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Word 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.