← Back to Skills Marketplace
accessibility-check
by
Bovin Phang
· GitHub ↗
· v1.0.0
· MIT-0
158
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install accessibility-check
Description
审查或改进前端 UI 的语义结构、键盘支持、焦点管理、标签以及常见的 WCAG 相关问题，并将报告保存为 Markdown 文件。当用户提到无障碍、accessibility、a11y、WCAG，或在实现交互组件时自动激活。
README (SKILL.md)
无障碍实现规范（WCAG 2.1 AA）
必须项
- 所有图片必须有有意义的
alt文字 - 交互元素必须可键盘访问（Tab、Enter、Space、Escape）
- 表单元素必须有关联
\x3Clabel> - 模态框必须捕获焦点并支持 Esc 关闭
ARIA 使用原则
- 优先使用语义化 HTML，而非 ARIA
role属性不覆盖原生语义- 动态内容更新使用
aria-live
可访问性检查
在以下场景使用该 Skill：
- 实现或评审表单、对话框、菜单、表格、标签页、树、抽屉和自定义组件
- 将设计稿转换为代码
- 页面上线前做 QA 或发布前检查
检查清单
- 语义地标和标题层级
- 表单标签与描述
- 按钮和链接命名
- 键盘导航顺序
- 焦点环是否可见
- 对话框焦点锁定与关闭后焦点恢复
- 在需要时正确使用 aria-expanded / aria-controls / aria-selected
- 表格语义是否正确
- 是否存在明显的颜色对比度风险
- 纯图标控件是否具备可访问名称
- 在需要时是否对 loading、empty、error 状态进行了提示
输出格式
# 无障碍检查报告
> 生成时间: YYYY-MM-DD HH:mm
> 评审工具: frontend-craft
> 标准: WCAG 2.1 AA
## 🔴 必须修复 (N项)
- **[文件:行号]** 问题描述 → 建议修改
## 🟡 建议改进 (N项)
- **[文件:行号]** 问题描述 → 建议修改
## ✅ 已通过项
- ...
## 建议的代码修改
- ...
报告文件输出
检查完成后，必须将报告内容使用 Write 工具保存为 Markdown 文件：
- 目录：项目根目录下的
reports/（如不存在则创建） - 文件名：
accessibility-review-YYYY-MM-DD-HHmmss.md（使用当前时间戳） - 保存后告知用户报告文件路径
务求实用。优先使用原生语义，不要过度依赖 ARIA。
Usage Guidance
This skill appears coherent and low-risk: it will generate an accessibility report and save it under reports/ in the project. Before installing or running it, confirm you are comfortable allowing the agent to read project files (source/markup/CSS) so it can perform the review, and verify where the agent's "Write" tool will create files (it will create reports/accessibility-review-YYYY-MM-DD-HHmmss.md). If you are analyzing sensitive code, consider running the skill on a copy of the repo or in a restricted workspace. Note: the SKILL.md mentions a review tool name ('frontend-craft') as a header only — there are no installs or external network calls specified in the skill.
Capability Analysis
Type: OpenClaw Skill
Name: accessibility-check
Version: 1.0.0
The skill bundle is a legitimate tool designed to perform web accessibility (a11y) audits based on WCAG 2.1 AA standards. The SKILL.md file contains instructions for the agent to review frontend code for semantic structure, keyboard support, and ARIA usage, and then save a report to a local directory. There are no indicators of data exfiltration, malicious execution, or prompt injection attacks.
Capability Assessment
Purpose & Capability
Name, description and SKILL.md consistently describe an accessibility (WCAG 2.1 AA) review and producing a Markdown report. No unrelated credentials, binaries, or installs are requested.
Instruction Scope
The instructions focus on accessibility checks and mandate saving a Markdown report under project-root reports/. They do not attempt to access unrelated system config or external endpoints. The SKILL.md does not explicitly describe how the agent should obtain or analyze project source files (linters, file reads, or tools), so the agent may read workspace files to produce the report — that is expected for a review task but the skill does not document the exact file-read behavior.
Install Mechanism
No install spec and no code files — instruction-only skill. Lowest-risk install profile.
Credentials
No environment variables, credentials, or config paths are requested. The only capability implied is write access to the project workspace to create reports/, which is proportional to the stated purpose.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill does not request permanent system presence or modifications to other skills or global agent settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install accessibility-check - After installation, invoke the skill by name or use
/accessibility-check - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Accessibility check skill 1.1.0 adds improved guidance, coverage, and markdown report structure.
- Expanded instructions to cover more accessibility (a11y) scenarios, including detailed checklists.
- Now mandates markdown report output in a standardized format, including file naming conventions.
- Checklist expanded for semantic HTML, keyboard navigation, ARIA, focus management, contrast, and labeling.
- Includes practical WCAG 2.1 AA requirements and actionable reporting templates.
- Stronger emphasis on practical fixes and using semantic HTML over ARIA when possible.
Metadata
Frequently Asked Questions
What is accessibility-check?
审查或改进前端 UI 的语义结构、键盘支持、焦点管理、标签以及常见的 WCAG 相关问题，并将报告保存为 Markdown 文件。当用户提到无障碍、accessibility、a11y、WCAG，或在实现交互组件时自动激活。 It is an AI Agent Skill for Claude Code / OpenClaw, with 158 downloads so far.
How do I install accessibility-check?
Run "/install accessibility-check" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is accessibility-check free?
Yes, accessibility-check is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does accessibility-check support?
accessibility-check is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created accessibility-check?
It is built and maintained by Bovin Phang (@bovinphang); the current version is v1.0.0.
More Skills