Agent skill

Accessibility

by omer-metin in omer-metin/skills-for-antigravity

Accessibility isn't a feature - it's a fundamental quality of good software.

Apache-2.0Auto-check passedFrontend & Design

Install Accessibility

skills CLI
$ npx skills add omer-metin/skills-for-antigravity --skill accessibility -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install omer-metin/skills-for-antigravity accessibility --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/omer-metin/skills-for-antigravity.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/accessibility .claude/skills/accessibility && rm -rf skills-src

Use ~/.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/

Facts

Skill name
accessibility
GitHub stars
162
Token cost
~740 tokens
SKILL.md length
287 words
Files
4 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

Accessibility isn't a feature - it's a fundamental quality of good software.

  • Keyboard navigation
  • SKILL.md covers Identity and Reference System Usage
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Semantic-html mentioned

What it does

Accessibility is an agent skill from omer-metin/skills-for-antigravity. Accessibility isn't a feature - it's a fundamental quality of good software. 1 in 4 adults has a disability. Many more have temporary impairments or situational limitations. Your users include people who can't see, can't hear, can't use a mouse, or can't process information the way you do. This skill covers WCAG guidelines, ARIA patterns, keyboard navigation, screen reader compatibility, and automated testing. Key insight: accessible code is better code. The constraints of accessibility lead to simpler, more…

Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/patterns.md`, `references/sharp_edges.md` and `references/validations.md`).

It sits in Frontend & Design, covering Accessibility. The licence is Apache-2.0.

When your agent uses it

  • Keyboard navigation
  • Semantic-html mentioned

Example prompts

  • “t a feature - it”
  • “t see, can”
  • “t use a mouse, or can”
  • “/accessibility”

What it can do on your machine

Read from SKILL.md and the folder at commit e8dcf4e. 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.

    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

Accessibility loads about 740 tokens when it runs, and up to ~7.9k if it reads all its reference files. Until then it costs about 242 tokens; SKILL.md has 287 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~242
When it runs · the whole SKILL.md, loaded when a task matches
~740
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.9k

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 omer-metin/skills-for-antigravity at commit e8dcf4e, republished under its Apache-2.0 licence (© omer-metin). 287 words, ~740 tokens.

Download SKILL.mdSave it as .claude/skills/accessibility/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
accessibility
description
Accessibility isn't a feature - it's a fundamental quality of good software. 1 in 4 adults has a disability. Many more have temporary impairments or situational limitations. Your users include people who can't see, can't hear, can't use a mouse, or can't process information the way you do. This skill covers WCAG guidelines, ARIA patterns, keyboard navigation, screen reader compatibility, and automated testing. Key insight: accessible code is better code. The constraints of accessibility lead to simpler, more semantic, more maintainable implementations. 2025 lesson: Accessibility lawsuits are at an all-time high. "We'll add it later" is both ethically wrong and legally risky. Start accessible, stay accessible. Use when "accessibility, a11y, wcag, aria, screen reader, keyboard navigation, focus trap, alt text, color contrast, skip link, accessible, accessibility, a11y, wcag, aria, screen-reader, keyboard, inclusive, semantic-html" mentioned.

Accessibility

Identity

You're a developer who understands that accessibility is not optional. You've seen teams scramble to retrofit accessibility after lawsuits, watched users struggle with inaccessible interfaces, and learned that building accessible from the start is always cheaper than fixing it later.

Your hard-won lessons: The team that uses semantic HTML ships accessible code by default. The team that uses divs for everything spends months adding ARIA. You've debugged screen reader issues at 2 AM, fought with focus traps, and learned that if you can't tab to it, real users can't use it.

You push for keyboard testing during development, not after. You know that automated tools catch 30% at best - real testing with NVDA and VoiceOver is non-negotiable.

Principles
  • Semantic HTML first - ARIA is a repair tool, not a replacement
  • If you can't use it with a keyboard, it's broken
  • Color is never the only indicator
  • All images need alt text - decorative images get empty alt=""
  • Focus states are not optional
  • Accessible experiences should be equivalent, not separate
  • Test with real assistive technology, not just automated tools

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

© omer-metin, Apache-2.0. 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 3 other files (references) in skills/accessibility of omer-metin/skills-for-antigravity.

  • SKILL.md
  • references/patterns.md
  • references/sharp_edges.md
  • references/validations.md

Open the folder on GitHubat commit e8dcf4e

Compare with similar skills

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.

Accessibility compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Accessibility this skillomer-metin/skills-for-antigravity162—~740Automated safety check: PassApache-2.0
Web Interface Guidelines Reviewervercel-labs/openreview1.7k97 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence
Accessibility Fixeribelick/ui-skills9.5k4 repos~1.2kAutomated safety check: PassMIT
Wcag Audit PatternsvmDeshpande/ai-agent-automation17811 repos~610Automated safety check: PassApache-2.0

Similar skills

  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 97 repos~308 tokens
    Frontend & DesignAuto-check passed
  • Accessibility Review

    markmead/hyperui

    Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

    12k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed
  • Accessibility Fixer

    ibelick/ui-skills

    Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.

    9.5k GitHub starsUsed in 4 repos~1.2k tokens
    Frontend & DesignAuto-check passed
  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 11 repos~610 tokens
    Frontend & DesignAuto-check passed
  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.5k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed

More from omer-metin/skills-for-antigravity

All 11 skills in this repo
  • A B Testing

    omer-metin/skills-for-antigravity

    The science of learning through controlled experimentation. An agent skill from omer-metin/skills-for-antigravity.

    162 GitHub stars~666 tokensUpdated 8 mo ago
    Auto-check passed
  • Agent Memory Systems

    omer-metin/skills-for-antigravity

    Memory is the cornerstone of intelligent agents. An agent skill from omer-metin/skills-for-antigravity.

    162 GitHub stars~731 tokensUpdated 8 mo ago
    Auto-check passed
  • Agent Tool Builder

    omer-metin/skills-for-antigravity

    Tools are how AI agents interact with the world. An agent skill from omer-metin/skills-for-antigravity.

    162 GitHub stars~705 tokensUpdated 8 mo ago
    Auto-check passed
  • AI Ad Creative

    omer-metin/skills-for-antigravity

    The intersection of AI generation and performance marketing.

    162 GitHub stars~733 tokensUpdated 8 mo ago
    Auto-check passed
  • AI Agents Architect

    omer-metin/skills-for-antigravity

    Expert in designing and building autonomous AI agents. An agent skill from omer-metin/skills-for-antigravity.

    162 GitHub stars~558 tokensUpdated 8 mo ago
    Auto-check passed
  • AI Brand Kit

    omer-metin/skills-for-antigravity

    Build comprehensive AI-native brand asset systems that maintain consistency across all AI-generated content.

    162 GitHub stars~782 tokensUpdated 8 mo ago
    Auto-check passed

Questions about Accessibility

What does Accessibility do?

Accessibility isn't a feature - it's a fundamental quality of good software. Accessibility is an agent skill from omer-metin/skills-for-antigravity. Accessibility isn't a feature - it's a fundamental quality of good software.

When should I use Accessibility?

Accessibility fits situations like: keyboard navigation; semantic-html mentioned.

How do I install Accessibility in Claude Code?

Run `npx skills add omer-metin/skills-for-antigravity --skill accessibility -a claude-code`. Or copy the skill folder (skills/accessibility in omer-metin/skills-for-antigravity) into .claude/skills/accessibility in your project. Claude Code loads it when a task matches its description.

How do I install Accessibility in Codex?

Run `npx skills add omer-metin/skills-for-antigravity --skill accessibility -a codex`. Or copy the skill folder (skills/accessibility in omer-metin/skills-for-antigravity) into .agents/skills/accessibility in your project. Codex loads it when a task matches its description.

Can I use 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 omer-metin/skills-for-antigravity --skill 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/accessibility, .gemini/skills/accessibility, .github/skills/accessibility and .opencode/skills/accessibility in your project.

What does Accessibility need to run?

SKILL.md names no scripts, command-line tools or credentials: Accessibility is instructions for the agent only.

Does 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 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 Accessibility use?

Accessibility is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Accessibility use?

About 740 tokens (SKILL.md is roughly 3k 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 7.2k tokens, read only when the agent opens those files.

What are the alternatives to Accessibility?

Skills that share tags, products or a category with Accessibility: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Accessibility?

omer-metin (a GitHub user) maintains it in omer-metin/skills-for-antigravity, which has 162 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on January 22, 2026.

Source: omer-metin/skills-for-antigravity on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.