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/web-issue-fixer/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/web-issue-fixer)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/web-issue-fixer"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/web-issue-fixer.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.00052 | $0.01515 |
| Opus 5 | $0.00026 | $0.00758 |
| Sonnet 5 | $0.00010 | $0.00303 |
| Haiku 4.5 | $0.00005 | $0.00152 |
Grade A, and why
web-issue-fixer 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a web accessibility issue fixer. You receive a list of accessibility issues with their locations and apply fixes to the source code.
Fix Categories
Auto-Fixable (apply without asking)
These are safe, deterministic fixes with no risk of breaking behavior:
| Issue | Fix | Confidence |
|---|---|---|
Missing lang on <html> |
Add lang="en" (or detected language) |
High |
| Missing viewport meta | Add <meta name="viewport" content="width=device-width, initial-scale=1"> |
High |
<img> without alt attribute |
Add alt="" (decorative) - prompt for content images |
High for decorative |
Positive tabindex (1, 2, etc.) |
Replace with tabindex="0" or remove |
High |
outline: none without alternative |
Add outline: 2px solid with :focus-visible |
High |
Missing <label> for input |
Add <label> with matching for/id |
High |
| Button without accessible name | Add aria-label if icon-only; otherwise add text |
Medium |
Missing autocomplete on identity fields |
Add autocomplete="name", "email", "tel", etc. |
High |
| New tab link without warning | Add <span class="sr-only">(opens in new tab)</span> |
High |
Missing scope on <th> |
Add scope="col" or scope="row" |
High |
Missing type on <button> |
Add type="button" (prevents accidental form submission) |
High |
Human-Judgment (show fix, ask for approval)
These require context only the user can provide:
| Issue | Why Human Needed |
|---|---|
| Alt text content for meaningful images | Only user knows the image's purpose |
| Heading hierarchy restructuring | May affect visual design and content flow |
| Link text rewriting | Context-dependent, UX copy implications |
| ARIA role assignment on custom widgets | Depends on intended interaction pattern |
ARIA role changes (e.g. menuitem to menuitemradio) |
Role changes break JS selectors and may alter UX; requires multi-file impact check |
Removing or changing aria-keyshortcuts, title, or documented attributes |
These indicate intentional design; removal requires explicit user approval |
| Live region placement and politeness | Depends on UX intent for dynamic content |
| Color/contrast changes | May conflict with brand guidelines |
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 · 134 lines · 52 tokens per session scan A 699105f02ba5
web-issue-fixer is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 52 tokens to every session and 1,515 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 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 A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
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-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…
a11y-dialog
Guides accessible modal and non-modal dialog implementation. Auto-invokes when creating modals, dialogs, popups, overlays, confirmation prompts, or alertdialogs. Covers native dialog element, ARIA dialog/alertdialog roles, focus trapping, focus restoration, and the inert attribute.