AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

A11y

skill-crewforth-crewforth-a11y · by crewforth

|

↗ Website ↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-crewforth-crewforth-a11y

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-crewforth-crewforth-a11y)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of A11y? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Accessibility (a11y)

Trigger phrases: "a11y", "accessibility", "WCAG", "screen reader", "keyboard navigation", "contrast", "ARIA", "keyboard only", "with a keyboard", "keyboard focus", "without a mouse", "focus ring", "tab order", "alt text", "color blind", "colour blind", "voiceover", "talkback", "reduced motion"

Goal: make the interface usable by everyone, including keyboard, screen reader, and low vision. Baseline target: WCAG 2.1 AA. Stack-agnostic (web/React/RN); do a web search when needed for framework-specific APIs.

Checklist

  • [ ] Semantic HTML: button/a/nav/main/h1..h6 correct; no div-buttons
  • [ ] Keyboard: every interaction reachable via Tab, sensible order, visible focus ring
  • [ ] Focus management: focus moves on modal/route change, focus trap correct
  • [ ] Contrast: text ≥ 4.5:1, large text ≥ 3:1
  • [ ] Alt text: alt on meaningful images; alt="" on decorative images
  • [ ] Forms: every input has a label; error message programmatically linked (aria-describedby)
  • [ ] ARIA: only when needed; wrong ARIA is worse than no ARIA; role/name/state correct
  • [ ] Motion/animation: respect prefers-reduced-motion
  • [ ] Language: `` correct (coordinate with i18n)

How

  1. Start with semantics — the right element solves 80%. Use button instead of role="button"+div.
  2. Navigate with the keyboard — drop the mouse, run the whole flow with Tab/Shift-Tab/Enter/Escape; is focus visible and its order sensible.
  3. Naming — does every interactive element have an accessible name (aria-label on visual-only icon buttons).
  4. Contrast — check color pairs against the ratio; don't convey meaning by color alone (add an icon/text).
  5. Dynamic content — notify the screen reader via a live region (aria-live); manage modal focus.
  6. Automated + manual — tools like linters/axe are the baseline; but manual keyboard+reader testing is essential (tools don't catch 100%).

React / RN note

  • Web React: semantic element in JSX + htmlFor/aria-*; use button instead of a clickable div.
  • React Native: accessible, accessibilityLabel, accessibilityRole, accessibilityState (coordinate with frontend-rn-expo).

Invariant rules

  1. Semantics first, ARIA second — wrong ARIA does harm.
  2. Must be fully usable by keyboard — without a mouse.
  3. Color cannot be the sole carrier of meaning.
  4. Automated tools are not enough — manual keyboard+reader testing.
  5. Follow the existing design system — if there is a component library, keep its accessible pattern.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML