Skills accessibility-wcag
📦

accessibility-wcag

v1.0 Content revision r1 Low Risk ⚙️ External commands🌐 Network access

Audit Interfaces for WCAG 2.2 Compliance

Accessibility defects make products difficult to use and increase compliance risk. This skill guides Claude, Codex, and Claude Code through WCAG 2.2 checks for UI work.

Supports: Claude Codex Code(CC)
📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "accessibility-wcag" from https://skillstore.io/skills/doyajin174-accessibility-wcag.md and its manifest at https://skillstore.io/api/skills/doyajin174-accessibility-wcag/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/doyajin174-accessibility-wcag.md Signed manifest GET /api/skills/doyajin174-accessibility-wcag/manifest Signed lockfile GET /api/skills/doyajin174-accessibility-wcag/lockfile

Test it

Using "accessibility-wcag". A custom clickable card uses a div, mouse click handling, and no focus style.

Expected outcome:

The review flags missing semantic button behavior, missing keyboard activation, and hidden focus. It recommends a native button or complete role, tab, key, and focus support.

Using "accessibility-wcag". A form uses placeholder text instead of labels for email and password fields.

Expected outcome:

The review identifies missing programmatic labels and explains the screen reader impact. It recommends visible labels linked to each input.

Using "accessibility-wcag". A dashboard uses light gray text, icon-only controls, and drag-only sorting.

Expected outcome:

The review reports contrast, name, and dragging alternative issues. It suggests stronger colors, accessible names, and move up or down buttons.

Security Audit

Low Risk
v8 • 7/6/2026 Open versioned report

Static analyzer hits were false positives caused by Markdown code fences, CSS examples, keyboard-event text, and reference links in SKILL.md. No prompt injection, credential access, obfuscation, data exfiltration, or executable malware intent was found. The only residual concern is broad Bash permission for a skill that is mostly documentation and review guidance.

1
Files scanned
299
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Low
SKILL.md:4SKILL.md:225-234
Overbroad Bash Tool Permission
The skill declares Bash access while its main purpose is accessibility guidance. The documentation also includes optional npm and Lighthouse CI commands, so agents should require explicit user approval before running setup or audit commands.
The Bash permission and command examples are visible in the skill file, but they are framed as optional testing tools. This is a permission-scope risk, not evidence of malicious intent.

Risk Factors

⚙️ External commands (29)
SKILL.md:33-41 SKILL.md:41-45 SKILL.md:45-56 SKILL.md:56-60 SKILL.md:60-78 SKILL.md:78-82 SKILL.md:82-97 SKILL.md:97-107 SKILL.md:107-119 SKILL.md:119-123 SKILL.md:123-133 SKILL.md:133-137 SKILL.md:137-157 SKILL.md:157-161 SKILL.md:161-178 SKILL.md:178-184 SKILL.md:184-196 SKILL.md:196-200 SKILL.md:200-209 SKILL.md:209-213 SKILL.md:213-219 SKILL.md:219-225 SKILL.md:225-235 SKILL.md:235-239 SKILL.md:239-249 SKILL.md:249-264 SKILL.md:264-270 SKILL.md:270-274 SKILL.md:274-280
🌐 Network access (1)
SKILL.md:298
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/doyajin174-accessibility-wcag/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/doyajin174-accessibility-wcag/security.svg)](https://skillstore.io/skills/doyajin174-accessibility-wcag?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/doyajin174-accessibility-wcag?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/doyajin174-accessibility-wcag/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/doyajin174-accessibility-wcag.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

Doyajin174. (2026). accessibility-wcag security audit report (audit version 8) [Author version 1.0]. Skillstore. https://skillstore.io/skills/doyajin174-accessibility-wcag/audits/8

BibTeX citation

@techreport{doyajin174-doyajin174-accessibility-wcag-2026, author = {Doyajin174}, title = {accessibility-wcag security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/doyajin174-accessibility-wcag/audits/8}, note = {Author version 1.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "accessibility-wcag security audit report (audit version 8)" version: "1.0" type: report authors: - name: "Doyajin174" date-released: "2026-07-06" url: "https://skillstore.io/skills/doyajin174-accessibility-wcag/audits/8" identifiers: - type: other value: "skillstore:doyajin174-accessibility-wcag:audit:8" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
70
Community
83
Spec Compliance

What You Can Build

Review a React Component

Check a new component for labels, semantic elements, keyboard behavior, focus states, and ARIA usage before merge.

Prepare an Accessibility Audit

Create a WCAG 2.2 review checklist with manual and automated test steps for a feature release.

Improve Design Handoff Quality

Translate accessibility requirements into concrete UI acceptance criteria for touch targets, contrast, focus, and alternatives.

Try These Prompts

Check Basic Accessibility 
Review this component for WCAG 2.2 basics. Focus on semantic HTML, alt text, labels, keyboard access, and color contrast.
Find Keyboard Issues 
Audit this interaction for keyboard accessibility. Check tab order, focus visibility, Enter and Space behavior, escape behavior, and alternatives to dragging.
Create a Release Checklist 
Build a WCAG 2.2 AA checklist for this feature. Include automated tests, manual screen reader checks, contrast checks, and acceptance criteria.
Refactor for WCAG 2.2 AA 
Review this UI code and propose a WCAG 2.2 AA remediation plan. Prioritize blockers, explain user impact, and suggest implementation steps.

Best Practices

  • Start with native HTML controls before adding ARIA roles or custom interaction code.
  • Test every critical workflow with only the keyboard before relying on automation results.
  • Document each accessibility fix with the user impact and the WCAG criterion it addresses.

Avoid

  • Replacing buttons and links with clickable div elements without keyboard support.
  • Using color alone to communicate errors, state, status, or required actions.
  • Adding ARIA attributes to hide structural problems instead of fixing semantic markup.

Frequently Asked Questions

Which WCAG version does this skill target?
It targets WCAG 2.2 and emphasizes AA requirements for common frontend work.
Can it run automated accessibility tests?
It can suggest tools and commands, but any command should run only after user approval.
Does it replace a full accessibility audit?
No. It supports code review and checklist creation, but full audits need manual testing and assistive technology review.
Does it cover ARIA?
Yes. It guides dialog roles, live regions, busy states, labels, and when native HTML is better than ARIA.
Can designers use it?
Yes. Designers can use it to create acceptance criteria for contrast, target size, focus, labels, and alternatives.
Is it useful for Claude Code and Codex?
Yes. The skill provides review prompts and remediation guidance for Claude, Codex, and Claude Code workflows.

Developer Details

Author

Doyajin174

License

MIT

Author version

v1.0

Skillstore revision

r1

Version notice

The author-declared version is not valid SemVer.

Repository

https://github.com/Doyajin174/myskills/tree/main/.public/skills/accessibility-wcag

Ref

72d5025b022c77f7a51bdf5c1637c689c80e89d1

Maintenance freshness

7/18/2026

Usage

4 downloads · 217 views

File structure

📄 SKILL.md