accessibility-checker

Check UI components and forms for accessibility attributes and markup suggestions.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/mouayadakel/flixCamFinal --skill accessibility-checker-mouayadakel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-checker
Source: https://github.com/mouayadakel/flixCamFinal/tree/main/.cursor/skills/accessibility-checker
Command: npx skills add https://github.com/mouayadakel/flixCamFinal --skill accessibility-checker-mouayadakel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure that user interfaces are accessible to everyone, including people with disabilities, by identifying and suggesting fixes for common accessibility issues.

Core Features & Use Cases

  • Component Auditing: Checks UI components for accessibility best practices.
  • Form Validation: Ensures form elements are properly labeled and accessible.
  • Semantic HTML: Verifies the correct use of HTML elements for structure and navigation.
  • Use Case: When developing a new form, use this Skill to automatically check that all input fields have associated labels, error messages are announced correctly, and focus indicators are visible.

Quick Start

Use the accessibility-checker skill to audit the accessibility of the new login form.

Frequently Asked Questions about accessibility-checker

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

FAQPage Schema
How do I check my web components for missing ARIA attributes and accessibility issues?

To check web components for accessibility issues, you audit interactive elements for missing ARIA attributes, unlabeled controls, and poor color contrast. This process identifies semantic HTML errors and provides specific markup suggestions to ensure proper focus management and screen reader support.

How do I ensure my HTML forms are accessible and properly labeled?

To ensure HTML forms are accessible, you must verify that all input fields have associated labels and that error messages are announced correctly via ARIA. Validating form elements checks that focus indicators are visible and controls are fully operable by all users.

What is the best way to add alt text and semantic HTML to UI elements?

The best way to add alt text and semantic HTML is to audit UI components for missing accessibility attributes. This identifies missing alt text on images and incorrect HTML structure, providing specific markup suggestions to enhance navigation and screen reader compatibility.

Can I automatically identify poor color contrast and unlabeled controls in my UI?

Yes, you can identify poor color contrast and unlabeled controls by running an accessibility audit on your UI components. The audit checks interactive elements against accessibility best practices and returns specific markup suggestions to resolve contrast and labeling violations.

When do I need to check focus management for interactive web elements?

You need to check focus management for interactive web elements whenever you develop new forms or UI components. Verifying focus indicators and correct semantic HTML ensures keyboard navigation and screen reader focus move logically through all interactive controls.