← Back to Skills Marketplace
A11y
by
codenova58
· GitHub ↗
· v1.0.0
· MIT-0
191
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install a11y
Description
Inclusive UI for real users—keyboard and focus, semantics for AT, contrast and motion, forms and errors. Use when fixing WCAG issues, auditing screens, or de...
README (SKILL.md)
A11y
Help ship interfaces that work for keyboard, screen readers, voice control, and low vision—without treating accessibility as a bolt-on checkbox.
What this skill is for
- Concrete fixes: focus traps, missing names/roles, heading order, label–control wiring, live regions, skip links.
- Design trade-offs: custom components vs native elements, motion reduction, contrast vs brand color.
- Verification: what to test in browser + AT, and what still needs human QA.
What to skip or defer
- Legal compliance certification (VPAT, formal audits)—suggest specialists when the user needs signed-off conformance.
- Visual design taste without an accessibility angle—unless it affects contrast, touch targets, or readability.
Workflow (adapt freely)
- Context — Who uses what (keyboard-only, VoiceOver, NVDA, zoom)? Which WCAG level (A/AA) is the target?
- Surface problems — Route critical paths; list failures (not vague “be more accessible”).
- Fix in order — Blockers first (can’t complete task), then serious (wrong info), then polish.
- Prove it — Tab order, focus visible, screen reader labels, automated checks where useful, manual pass on real flows.
Anti-patterns to call out
divbuttons without keyboard support; only running Lighthouse and declaring done.- Hiding focus rings “for aesthetics”; icon-only controls with no accessible name.
- Over-using
aria-*instead of using the right semantic element first.
Done when
- Critical paths are keyboard-operable and named for assistive tech; known gaps are documented with owners.
Usage Guidance
This skill is a lightweight, text-only accessibility advisor — low risk. It cannot execute code or access credentials because it has no install or required env vars. Before you rely on its output: (1) treat its recommendations as guidance, not formal compliance certification (the SKILL.md explicitly defers VPAT/formal audits); (2) have a human reviewer or accessibility specialist validate and test any code or UI changes in real browsers and assistive technologies; and (3) be mindful of what you paste into prompts (don’t share secrets or full production configs). If you need automated scans or integrations with your repo/CI, look for a skill that explicitly declares those capabilities and required credentials.
Capability Analysis
Type: OpenClaw Skill
Name: a11y
Version: 1.0.0
The skill bundle contains only metadata and documentation (SKILL.md) focused on web accessibility (a11y) best practices. There is no executable code, no network activity, and no evidence of prompt injection or malicious intent; the instructions are entirely aligned with the stated purpose of assisting with WCAG compliance and UI audits.
Capability Assessment
Purpose & Capability
Name, description, and runtime instructions all describe accessibility guidance and remediation; there are no extra env vars, binaries, or unrelated requirements.
Instruction Scope
SKILL.md contains high-level workflows, checks, and anti-patterns for accessibility audits and fixes. It does not instruct the agent to read files, access credentials, or send data to external endpoints. The guidance is deliberately general and advisory.
Install Mechanism
No install specification or code files are present (instruction-only), so nothing is written to disk or downloaded during install.
Credentials
The skill requests no environment variables, credentials, or config paths — proportional for a guidance-only accessibility skill.
Persistence & Privilege
always is false and the skill does not request elevated persistence or modify other skills/configs. It can be invoked autonomously by the agent (platform default), which is expected for a helper skill.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install a11y - After installation, invoke the skill by name or use
/a11y - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the a11y skill:
- Provides guidance for building inclusive UIs — including keyboard navigation, focus management, semantic markup, color contrast, and motion considerations.
- Covers typical accessibility tasks: fixing WCAG issues, auditing interfaces, and designing flows with accessibility in mind.
- Outlines a practical workflow for identifying, prioritizing, and verifying accessibility barriers.
- Clarifies the scope: not a replacement for formal audits or compliance certification.
- Lists key anti-patterns and clear indicators for “done.”
Metadata
Frequently Asked Questions
What is A11y?
Inclusive UI for real users—keyboard and focus, semantics for AT, contrast and motion, forms and errors. Use when fixing WCAG issues, auditing screens, or de... It is an AI Agent Skill for Claude Code / OpenClaw, with 191 downloads so far.
How do I install A11y?
Run "/install a11y" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is A11y free?
Yes, A11y is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does A11y support?
A11y is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created A11y?
It is built and maintained by codenova58 (@codenova58); the current version is v1.0.0.
More Skills