ClawHub

Accessibility V2

v1.0.0

Prüft UI-Komponenten auf WCAG-Verstöße und verbessert Zugänglichkeit durch ARIA-Labels, Farbkontraste und Screenreader-Support.

⭐ 0· 72·1 current·1 all-time
by@hupmann86-cell·duplicate of @hupmann86-cell/accessibility-checker
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (WCAG checks and accessibility fixes) align with the SKILL.md workflow (AUDIT → IDENTIFY → FIX → TEST). The skill declares no binaries, env vars, or installs that would be unrelated to performing UI accessibility checks.
ℹ
Instruction Scope
SKILL.md is high‑level and does not specify concrete commands, file paths, or how fixes are applied. That vagueness gives the agent broad discretion (e.g., reading project files or proposing/writing changes). The actions described (run Lighthouse, add ARIA labels, adjust contrast) are within the skill's scope, but you should expect to review any automated edits before they are applied.
✓
Install Mechanism
No install spec and no code files are present (instruction-only). Nothing will be downloaded or written to disk by the skill itself based on the provided metadata.
✓
Credentials
The skill requests no environment variables, credentials, or config paths — appropriate for an instruction-only accessibility checker.
✓
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill does not request persistent system presence or modification of other skills/configs.
Assessment
This skill appears coherent and minimal, but it is very high-level. Before enabling it: 1) Clarify whether the agent will only suggest fixes (diffs/PRs) or will modify files directly; prefer suggestions/PRs you can review. 2) Limit the agent's repository/file access to only the UI code it needs and avoid giving access to secrets or unrelated projects. 3) Specify which tools/versions (e.g., Lighthouse) you want used and run the checks in a sandbox or CI pipeline first. 4) Require human approval for any automated writes. If you need stronger guarantees, ask the author for a more detailed SKILL.md that lists exact commands, expected inputs/outputs, and the mechanism for applying fixes.

Like a lobster shell, security has layers — review code before you run it.

latestvk971cz3ryn072bpskz2mfwrqas84afzp

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments