Skills accessibility

📦

accessibility

Name: accessibility
Author: addyosmani

v1.1 Content revision r1 Safe ⚙️ External commands📁 Filesystem access🌐 Network access

Improve Web Accessibility

Accessibility issues block users and create compliance risk. This skill gives Claude, Codex, and Claude Code WCAG 2.2 checklists, patterns, and testing guidance.

Supports: Claude Codex Code(CC)

📊 74 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" from https://skillstore.io/skills/addyosmani-accessibility.md and its manifest at https://skillstore.io/api/skills/addyosmani-accessibility/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/addyosmani-accessibility.md Signed manifest GET /api/skills/addyosmani-accessibility/manifest Signed lockfile GET /api/skills/addyosmani-accessibility/lockfile

Test it

Using "accessibility". Audit a checkout form for accessibility issues.

Expected outcome:

Missing labels on required fields should be fixed first because screen reader users need programmatic names.
Error messages should be associated with each field and announced when validation fails.
Keyboard focus should move to the first invalid field after submit.

Using "accessibility". Make a modal dialog keyboard accessible.

Expected outcome:

Use a real dialog pattern with a clear accessible name.
Move focus into the dialog when it opens and return focus when it closes.
Support Escape to close and keep Tab navigation within the dialog while open.

Using "accessibility". Prepare a WCAG 2.2 release checklist.

Expected outcome:

Run automated checks for common accessibility failures.
Test the full workflow with keyboard only.
Verify focus visibility, target size, page language, labels, error handling, and reduced motion support.

Security Audit

Safe

v5 • 7/7/2026 Open versioned report

All 60 static findings were reviewed against the Markdown context. No executable skill code, prompt-injection attempt, malicious data access, or unauthorized network behavior was found; the alerts are documentation examples, Markdown fences, relative links, placeholder URLs, and accessibility snippets.

Files scanned

877

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (44)

📁 Filesystem access (2)

references/A11Y-PATTERNS.md:3 SKILL.md:448

🌐 Network access (4)

references/WCAG.md:111 SKILL.md:399 SKILL.md:403 SKILL.md:447

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

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

Copy report link

https://skillstore.io/skills/addyosmani-accessibility/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/addyosmani-accessibility.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

addyosmani. (2026). accessibility security audit report (audit version 5) [Author version 1.1]. Skillstore. https://skillstore.io/skills/addyosmani-accessibility/audits/5

BibTeX citation

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

CITATION.cff

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

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Audit a Feature Before Release

Review a new page or component for WCAG 2.2 issues before it ships.

Design Accessible Interaction States

Check focus states, target sizes, labels, and motion alternatives during design review.

Build a Manual Test Checklist

Create a practical plan for keyboard, screen reader, zoom, contrast, and reduced motion testing.

Try These Prompts

Run a Basic Audit

Review this page for WCAG 2.2 accessibility issues. Focus on labels, alt text, contrast, focus states, and keyboard navigation.

Fix a Component

Improve this component for accessibility. Explain each change and cite the WCAG area it supports.

Prepare Release Testing

Create an accessibility test plan for this feature. Include automated checks, manual keyboard tests, and screen reader checks.

Prioritize Remediation

Audit these findings and prioritize remediation by user impact, WCAG level, implementation effort, and release risk.

Best Practices

Start with semantic HTML before adding ARIA roles or custom keyboard handling.
Combine automated checks with manual keyboard and screen reader testing.
Prioritize fixes by user impact, WCAG level, and release risk.

Avoid

Do not remove focus outlines without providing a visible replacement.
Do not rely on color alone to communicate errors, status, or required actions.
Do not use custom interactive elements when native controls can provide the same behavior.

Frequently Asked Questions

Does this skill cover WCAG 2.2?

Yes. It includes WCAG 2.2 criteria, conformance levels, and new requirements such as target size and focus visibility.

Can it replace an accessibility specialist?

No. It helps with audits and fixes, but expert review is still important for legal and user-impact decisions.

Does it support automated testing?

Yes. It includes guidance for Lighthouse and axe checks, plus manual testing tasks that automation cannot cover.

Can it help with screen reader support?

Yes. It explains labels, live regions, focus behavior, and common screen reader testing considerations.

What kinds of interfaces does it help with?

It helps with web pages, forms, modals, navigation, tabs, media, notifications, and other browser-based UI patterns.

Does it generate production-ready fixes?

It can suggest practical fixes, but teams should test them in the real application and assistive technology stack.

Developer Details

Author

addyosmani

License

MIT

Author version

v1.1

Skillstore revision

Version notice

The author-declared version is not valid SemVer.

Repository

https://github.com/addyosmani/web-quality-skills/tree/main/skills/accessibility/

Ref

d46e62089a6dfc9e14ea02eebd9b8e2ad2dfe1f4

Maintenance freshness

7/18/2026

Usage

4 downloads · 92 views

File structure

📁 references/

📄 A11Y-PATTERNS.md

📄 WCAG.md

📄 SKILL.md