accessibility-basic-check

Name: accessibility-basic-check
Availability: InStock
Author: wanxiajaneyang

Audit UI elements for color contrast, keyboard navigation, and form labeling.

Updated Feb 11, 2026

Search Tags:#ui #checklist #accessibility #a11y #web development #validation

Ready to run

npx skills add https://github.com/WanxiaJaneYang/mvp-agent --skill accessibility-basic-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility-basic-check
Source: https://github.com/WanxiaJaneYang/mvp-agent/tree/main/.agents/skills/accessibility-basic-check
Command: npx skills add https://github.com/WanxiaJaneYang/mvp-agent --skill accessibility-basic-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure that UI changes meet basic accessibility standards, preventing common issues before they reach users.

Core Features & Use Cases

Color Contrast Check: Validates that text and background colors have sufficient contrast.
Keyboard Navigation: Verifies that interactive elements are focusable and navigable via keyboard.
Form Labeling: Ensures all form controls have associated, descriptive labels.
Use Case: A developer makes a change to a form's styling. Before submitting a pull request, they use this Skill to quickly check if the new styling breaks color contrast or keyboard accessibility.

Quick Start

Run a basic accessibility check on the new login form component.

Frequently Asked Questions about accessibility-basic-check

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

FAQPage Schema

How do I perform a basic accessibility check on my web development UI components?▼

To perform a basic accessibility check, provide the affected UI components and design specifications to validate color contrast, keyboard navigation, and form labeling for common violations.

What is checked during a basic UI accessibility audit for web development?▼

A basic UI accessibility audit checks for sufficient text and background color contrast, verifies interactive elements are keyboard navigable, and ensures all form controls have associated descriptive labels.

Do I need to provide design specifications for a11y validation?▼

Yes, you need to provide design specifications and user input on the affected pages or components to ensure accurate validation of color contrast, keyboard navigation, and form labeling.

How do I verify keyboard navigation and form labeling for my web forms?▼

You can verify keyboard navigation and form labeling by running an accessibility audit that checks if interactive elements are focusable and if all form controls have associated, descriptive labels.

When should I use an accessibility checklist before submitting a pull request?▼

You should use an accessibility checklist before submitting a pull request when you make UI changes, such as altering form styling, to prevent breaking color contrast or keyboard accessibility.