accessibility

accessibility is a skill for Claude Code, Codex from Vimalk0703/shipworthy. It costs 33 tokens per session (564 once invoked), scanned A, original, MIT.

A baseline for making websites and applications usable by people with disabilities. It covers WCAG 2.1 AA, a commonly used accessibility standard, including keyboard use, screen readers, readable contrast, and visible focus.

In plain words
What is it for?
Use it when building user interfaces to choose meaningful HTML elements, label controls, maintain sufficient color contrast, and manage keyboard focus.
Why use it?
It helps prevent interfaces that some users cannot navigate, understand, or operate.

Skill for Claude CodeCodex

Part of the shipworthy plugin — 41 skills, 7 commands, 6 agents, 3 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/vimalk0703/shipworthy/accessibility
Any agent
npx skills add Vimalk0703/shipworthy --skill accessibility
Clone the repo
git clone --depth 1 https://github.com/Vimalk0703/shipworthy

Made for: Claude Code, Codex.

Or install shipworthy, the plugin that ships this one along with the rest of its 41 skills, 7 commands, 6 agents, 3 hooks.

Wrote 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.

agentmods badge for accessibility

README.md
[![agentmods](https://agentmods.dev/badge/skills/vimalk0703/shipworthy/accessibility.svg)](https://agentmods.dev/skills/vimalk0703/shipworthy/accessibility)
Your own site
<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/accessibility"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/accessibility.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 564 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.00564
Opus 5 $0.00016 $0.00282
Sonnet 5 $0.00007 $0.00113
Haiku 4.5 $0.00003 $0.00056

Measured 4d ago against content hash c09c9eac4cf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 4d 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.

skills/frontend/accessibility/SKILL.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Accessibility

Baseline: WCAG 2.1 AA

Every user-facing interface must meet WCAG 2.1 Level AA. This is not optional — it's a legal requirement in many jurisdictions and the right thing to do.

Semantic HTML

Use the correct element, not a styled div:

  • <button> for actions (not <div onClick>)
  • <a> for navigation (not <span onClick>)
  • <nav> for navigation regions
  • <main> for primary content
  • <header>, <footer>, <section>, <article> for document structure
  • <h1>-<h6> in proper order (no skipping levels)
  • <ul>/<ol> for lists
  • <table> for tabular data (not for layout)

ARIA Labels

  • Every interactive element needs an accessible name
  • aria-label for elements without visible text
  • aria-labelledby to reference visible text
  • aria-describedby for additional context
  • aria-hidden="true" for decorative elements
  • Never use ARIA when native HTML semantics suffice

Color and Contrast

  • Text contrast ratio: 4.5:1 minimum (3:1 for large text)
  • Never convey information through color alone (add icons, text, patterns)
  • Ensure focus indicators are visible against all backgrounds

Keyboard Navigation

  • Every interactive element reachable via Tab
  • Logical tab order (follows visual layout)
  • Escape closes modals/popups
  • Enter/Space activates buttons
  • Arrow keys for menus, tabs, and lists
  • Visible focus indicator on all interactive elements

Images

  • Meaningful images: alt text describing the content
  • Decorative images: alt="" (empty alt, not missing alt)
  • Complex images (charts, diagrams): detailed aria-describedby

Forms

  • Every input has a <label> (linked via for/id)
  • Error messages linked to inputs via aria-describedby
  • Required fields marked with aria-required="true"
  • Form validation errors announced to screen readers

Focus Management

  • When modals open, focus moves to the modal
  • When modals close, focus returns to the trigger
  • Focus trapped inside modals (can't tab to background)
  • Route changes announce the new page to screen readers

Read the full file on GitHub · 68 lines

Changes

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.

  1. 4d ago First seen · 68 lines · 33 tokens per session scan A c09c9eac4cf9

Subscribe to this mod's changes

accessibility is a skill published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 564 once invoked, about $0.0002 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-08-31.

Related

Other skills, from other repositories

bmad-ux

Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX".

skyf0xx/hedgehog · 37 tokens

hedgehog-planning-intake

Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining 04-prd.md into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different…

skyf0xx/hedgehog · 0 tokens

inbound-triage

Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the issues", "check the PRs", "review inbound", "what's in the queue". Reads each item read-only, judges it for security and for whether it is real, then fixes and closes or comments and closes. Not part of the…

skyf0xx/hedgehog · 102 tokens

bmad-product-brief

Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.

skyf0xx/hedgehog · 31 tokens

bmad-revendor

Maintainer-only. Use when re-vendoring vendor-skills/BMAD/ against a newer BMAD-METHOD commit — "update BMAD", "re-vendor BMAD", "bump the BMAD pin". Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.

skyf0xx/hedgehog · 72 tokens

bmad-deep-recon

Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill a succinct cited summary with metadata that downstream skills consume without reprocessing — or run the research here…

skyf0xx/hedgehog · 167 tokens