mirror of
https://github.com/ngthanhvu/kr-phim.git
synced 2026-08-10 16:27:47 +00:00
68 lines
2.0 KiB
Markdown
68 lines
2.0 KiB
Markdown
|
---
|
||
|
|
name: accessibility-checker
|
||
|
|
display_name: Accessibility Checker
|
||
|
|
description: Audit and fix accessibility issues — WCAG 2.2 compliance, ARIA labels, color contrast, keyboard navigation, and screen-reader compatibility.
|
||
|
|
category: Creative & Design
|
||
|
|
platforms: [claude.ai, claude-code, api]
|
||
|
|
version: 1.0.0
|
||
|
|
author: Claude Code
|
||
|
|
tags: [accessibility-checker]
|
||
|
|
---
|
||
|
|
|
||
|
|
# Accessibility Checker
|
||
|
|
|
||
|
|
## Overview
|
||
|
|
|
||
|
|
Audit and fix accessibility issues — WCAG 2.2 compliance, ARIA labels, color contrast, keyboard navigation, and screen-reader compatibility.
|
||
|
|
|
||
|
|
## When to Use This Skill
|
||
|
|
|
||
|
|
Use **Accessibility Checker** when you need to:
|
||
|
|
|
||
|
|
- Work with accessibility checker tasks in your project or workflow
|
||
|
|
- Automate accessibility checker operations at scale
|
||
|
|
- Generate production-quality accessibility checker output quickly
|
||
|
|
|
||
|
|
## Instructions
|
||
|
|
|
||
|
|
When this skill is active, Claude will:
|
||
|
|
|
||
|
|
1. Understand the full context of your accessibility checker request
|
||
|
|
2. Apply best practices and conventions for Creative & Design
|
||
|
|
3. Produce clean, well-structured, production-ready output
|
||
|
|
4. Explain key decisions and offer alternatives where relevant
|
||
|
|
|
||
|
|
## Examples
|
||
|
|
|
||
|
|
### Example 1 — Basic Usage
|
||
|
|
|
||
|
|
**User:** Help me get started with accessibility checker.
|
||
|
|
|
||
|
|
**Claude:** I'll walk you through the essential steps for accessibility checker in your context...
|
||
|
|
|
||
|
|
### Example 2 — Advanced Usage
|
||
|
|
|
||
|
|
**User:** I need a production-ready accessibility checker setup with full error handling.
|
||
|
|
|
||
|
|
**Claude:** Here's a complete, production-hardened accessibility checker implementation...
|
||
|
|
|
||
|
|
## Guidelines
|
||
|
|
|
||
|
|
- Always validate inputs before processing
|
||
|
|
- Follow the conventions of the target platform or language
|
||
|
|
- Prefer explicit over implicit — clarity beats cleverness
|
||
|
|
- Include comments for non-obvious logic
|
||
|
|
- Suggest tests or validation steps where appropriate
|
||
|
|
|
||
|
|
## Dependencies
|
||
|
|
|
||
|
|
Required: axe, lighthouse
|
||
|
|
|
||
|
|
## Platforms
|
||
|
|
|
||
|
|
Available on: claude.ai, claude-code, api
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|