Skip to content
Agentmart
Submit a tool

accessibility-audit

To ensure the application is usable by people with disabilities, complying with WCAG standards and improving SEO/UX.

Skill by jyjeanne

IndexedMIT★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/jyjeanne-accessibility-audit

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

To ensure the application is usable by people with disabilities, complying with WCAG standards and improving SEO/UX. Use when: During development of UI components; Before major releases.

Use cases: design, security, marketing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/accessibility-audit

What's inside

Skill name
accessibility-audit
Description
To ensure the application is usable by people with disabilities, complying with WCAG standards and improving SEO/UX. Use when: During development of UI components; Before major releases.
License
MIT
Instructions
25 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

## Purpose
To ensure the application is usable by people with disabilities, complying with WCAG standards and improving SEO/UX.

## When to Use
- During development of UI components.
- Before major releases.

## Procedure
1.  **Semantic HTML**: Use correct tags (`<button>` vs `<div>`, `<nav>`, `<main>`).
2.  **Keyboard Navigation**: Ensure all interactive elements are focusable and usable via Tab/Enter/Space.
3.  **ARIA Labels**: Add `aria-label` or `aria-labelledby` where text is missing (icons).
4.  **Color Contrast**: Check text vs background contrast ratio (aim for AA standard).
5.  **Alt Text**: Ensure all meaningful images have `alt` attributes.
6.  **Tools**:
    - Run `Lighthouse` audit in Chrome DevTools.
    - Use `eslint-plugin-jsx-a11y` to catch issues while coding.

## Constraints
- Do not use `tabindex` greater than 0.
- Do not rely on color alone to convey information (use icons/text too).

## Expected Output
A report of accessibility issues and a refactored UI that passes automated a11y checks.

From jyjeanne/ai-setup-forge, MIT.

More from jyjeanne/ai-setup-forge

Signals

Stars
1
Forks
0
Open issues
0
Last commit (this folder)
Mar 16, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from jyjeanne

Cite this page

accessibility-audit skill. Agent Mart. https://agentmart.dev/skills/jyjeanne-accessibility-audit (last updated 2026-10-24)