accessibility

Validate web code and UI against WCAG guidelines for accessibility.

31|3|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/KreerC/ACCESSIBILITY.md --skill accessibility-kreerc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/KreerC/ACCESSIBILITY.md/tree/main/accessibility
Command: npx skills add https://github.com/KreerC/ACCESSIBILITY.md --skill accessibility-kreerc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web projects often ship with accessibility issues that exclude users with disabilities, leading to poor usability and legal risk. This skill provides guidance and checks to ensure products meet accessibility standards from the start.

Core Features & Use Cases

  • Semantics-first development: enforce semantic HTML, proper landmarks, and accessible form controls.
  • Keyboard and ARIA best practices: ensure all interactive elements are reachable and operable via keyboard with thoughtful ARIA usage when necessary.
  • Continuous accessibility checks: integrate linting, audits, and manual reviews into development workflows to catch issues early.
  • WCAG-aligned guidance: document and apply WCAG 2.x guidelines to design decisions and code changes.

Quick Start

Ask the agent to perform an accessibility review of your current web project and report WCAG conformance.

Frequently Asked Questions about accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my web project for WCAG conformance?

To check WCAG conformance, perform an accessibility review that validates your frontend code against WCAG 2.x guidelines, verifying semantic HTML, keyboard operability, and color contrast to ensure inclusivity for users with disabilities.

What is semantic HTML's role in web accessibility?

Semantic HTML provides the foundational structure for web accessibility by enforcing proper landmarks and accessible form controls, ensuring screen readers and assistive technologies can accurately interpret and navigate page content.

How do I ensure keyboard accessibility for interactive UI elements?

Ensure keyboard accessibility by validating that all interactive elements are reachable and operable via keyboard, applying thoughtful ARIA usage only when necessary to supplement native semantic behaviors during your QA review.

Can I integrate accessibility checks into my development workflow?

You can integrate continuous accessibility checks into your development workflow by running linting, automated audits, and manual reviews to catch issues early and maintain WCAG-aligned standards throughout the lifecycle.

What's the best way to apply ARIA best practices without breaking semantics?

The best way to apply ARIA is to first enforce semantic HTML and proper landmarks, using ARIA attributes only to supplement native semantics when necessary, ensuring interactive elements remain fully keyboard accessible.

Does this accessibility review work for both websites and web apps?

This accessibility review applies to frontend development, QA reviews, and design reviews across both sites and apps, applying WCAG 2.x guidelines to document and validate code changes for continuous maintenance.