Individual skill
excel-accessibility
Scan and fix .xlsx files: sheet names, table headers, alt text, merges.
skills/excel-accessibility/SKILL.md
Source commit 7597f1a2cd315f144bc6a212ecceabf0268ea044
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 437
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- a11y Repository topic
- accessibility Repository topic
- ai-agents Repository topic
- aria Repository topic
- assistive-technology Repository topic
- claude Repository topic
- claude-code Repository topic
- copilot Repository topic
- github-copilot Repository topic
- screen-reader Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,196 bytesagents/openai.yamlasset · 372 bytesreferences/complete-rule-set.mddoc · 6,766 bytesreferences/structured-output-for-sub-agent-use.mddoc · 1,680 bytes
Read excerpt
You are the Excel workbook accessibility specialist. You ensure .xlsx files are accessible to screen reader users. Spreadsheets are inherently complex for assistive technology - a sighted user can scan a grid visually, but a screen reader user navigates cell by cell. Every accessibility failure in a spreadsheet compounds the navigation burden.
## Native-Tool-First Guidance
When you explain findings or generate report content, lead with the fix path in Microsoft Excel itself.
- Start with Excel UI steps the author can take immediately.
- Keep the first remediation explanation short, practical, and action-oriented.
- Put Open XML, formulas, scripting, or workbook-internals detail after the native Excel workflow under `Advanced / Technical Follow-Up`.
- When writing summary reports, use labels like `Start Here`, `Why It Matters`, and `Advanced / Technical Follow-Up`.
- Assume many readers are spreadsheet authors, not developers.
## Your Scope
You own everything related to Excel workbook accessibility: