skills.rest
kanopi
kanopiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

accessibility-checker

Validate UI elements for WCAG 2.1 AA accessibility criteria.

16|4|Updated Oct 13, 2025
Search Tags:#testing#ui#accessibility#a11y#semantic-html#keyboard-accessibility#wcag-2.1
One-click install
npx skills add https://github.com/kanopi/cms-cultivator --skill accessibility-checker-kanopi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-checker
Source: https://github.com/kanopi/cms-cultivator/tree/main/skills/accessibility-checker
Command: npx skills add https://github.com/kanopi/cms-cultivator --skill accessibility-checker-kanopi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and reports accessibility issues fast on specific UI components, forms, or pages, helping developers meet WCAG requirements without performing full site audits.

Core Features & Use Cases

  • Focused checks on interactive and content elements (buttons, inputs, links, images) for keyboard accessibility, proper labeling, and contrast.
  • Use case: during development, you ask the tool to verify a form field's label and focus behavior, or to confirm color contrast for a button.

Quick Start

Check a specific UI element for accessibility by asking if it is accessible.

Frequently Asked Questions about accessibility-checker

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

FAQPage Schema
How do I check semantic HTML and keyboard accessibility for a specific UI element?▼

To check semantic HTML and keyboard accessibility for a UI element, you can run focused audits on individual components like buttons and forms to verify navigation, contrast, and labeling against WCAG 2.1 AA criteria.

Can I verify WCAG 2.1 AA color contrast for a single button during development?▼

Yes, you can verify WCAG 2.1 AA color contrast for a single button during development by running a targeted accessibility check that evaluates the specific element and delivers focused feedback for rapid fixes.

What is the best way to test form field labels and focus behavior for WCAG compliance?▼

The best way to test form field labels and focus behavior for WCAG compliance is to perform focused accessibility checks on the specific inputs, validating their semantic labeling and keyboard navigation without needing a full site audit.

Does this accessibility testing approach work for individual images and links?▼

Yes, this accessibility testing approach works for individual images and links by applying targeted checks to verify semantic HTML, keyboard accessibility, and proper labeling for those specific content elements.

Why perform focused accessibility checks instead of full site audits?▼

Performing focused accessibility checks instead of full site audits allows developers to quickly identify and report issues on specific UI components, helping meet WCAG requirements rapidly without the overhead of auditing the entire page.

When should I not use a focused UI accessibility checker?▼

You should not use a focused UI accessibility checker when you need to validate the overall compliance of an entire web application, as it is designed for rapid checks on individual elements rather than comprehensive site audits.

Related Skills

Explore More Software Engineering Skills→
suhwansuhwan

web-design-guidelines

Analyze UI source code for accessibility, semantic HTML, and keyboard navigation issues.

Community
Intermediate
haabehaabe

a11y-check

Audits web interfaces for WCAG 2.1 AA accessibility compliance.

Community
Intermediate
bacchus-labsbacchus-labs
4

accessibility-verification

Verify UI component accessibility with axe-core, keyboard navigation, screen readers, and Lighthouse.

Official
Advanced
MathiasPaulenkoMathiasPaulenko

WaveXis Accessibility

Automate accessibility audits and WCAG 2.2 compliance checks with axe-core.

Community
Advanced