ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified developer tools Safety 5/5

accessibility-check

审查或改进前端 UI 的语义结构、键盘支持、焦点管理、标签以及常见的 WCAG 相关问题,并将报告保存为 Markdown 文件。当用户提到无障碍、accessibility、a11y、WCAG,或在实现交互组件时自动激活。

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/bovinphang/accessibility-check
Or

What This Skill Does

The accessibility-check skill is a dedicated diagnostic tool for frontend developers and UI engineers to ensure their web applications meet WCAG 2.1 AA standards. Instead of relying on manual checklists, this skill programmatically inspects your DOM, HTML structure, and interactive components. It identifies common pitfalls such as missing alt text for images, broken keyboard navigation, poor focus management, and misuse of ARIA attributes. Once the inspection is complete, the skill generates a comprehensive, structured Markdown report in the reports/ directory, complete with actionable recommendations for code fixes.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/bovinphang/accessibility-check Ensure that your project environment has the necessary write permissions for the file system to allow the skill to save reports.

Use Cases

  • Pre-deployment QA: Run a full accessibility scan on production-ready code before shipping to ensure compliance.
  • Component Development: Use the skill during the creation of complex UI widgets like modals, menus, or custom tree views to verify focus trapping and keyboard shortcuts.
  • Accessibility Remediation: Pass the skill a codebase that has received negative feedback on its a11y support, and let it map out the high-priority issues that need immediate attention.

Example Prompts

  1. "Run an accessibility check on my current registration form component and tell me if the labels are properly associated with the inputs."
  2. "I just finished building a new modal. Can you perform an a11y review to ensure it handles Escape keys and focus trapping correctly?"
  3. "Please scan the header and navigation menu of this project for WCAG 2.1 AA compliance and save the report to my logs."

Tips & Limitations

  • Native First: Always prioritize native HTML elements (like <button> or <nav>) over complex ARIA patterns. The skill is designed to flag where developers have overly complicated their markup.
  • Report Management: The skill generates files with timestamps. Keep an eye on your reports/ folder and periodically clean up old scans to keep your repository organized.
  • Scope: While the tool is highly effective at identifying structural and functional a11y issues, it is not a substitute for human user testing with screen readers like NVDA or VoiceOver. Use this as your primary automation layer, then verify the user experience manually.

Metadata

Stars4190
Views0
Updated2026-04-18
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-bovinphang-accessibility-check": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#accessibility#wcag#frontend#qa#web-development
Safety Score: 5/5

Flags: file-write, file-read