forms

Ensure form controls have programmatic labels and accessible error messages.

39|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/mgifford/accessibility-skills --skill forms-mgifford
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forms
Source: https://github.com/mgifford/accessibility-skills/tree/main/skills/forms
Command: npx skills add https://github.com/mgifford/accessibility-skills --skill forms-mgifford

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forms often fail WCAG requirements when controls lack visible labels, clear error messages, or keyboard support, preventing users with disabilities from completing tasks.

Core Features & Use Cases

  • Ensure every form control has a programmatic label and visible labeling
  • Associate errors with fields using aria-describedby and provide actionable messages
  • Preserve keyboard accessibility and logical tab order across input groups during validation

Quick Start

Audit your project for form controls, add explicit labels, enable accessible error messages, and ensure keyboard navigation.

Frequently Asked Questions about forms

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

FAQPage Schema
How do I make form controls accessible with proper labels and keyboard navigation?

Make forms accessible by adding explicit programmatic labels to every control, preserving logical keyboard tab order, and associating actionable error messages using aria-describedby per WCAG guidelines.

How do I associate form validation errors with input fields for screen readers?

Associate validation errors with input fields by applying aria-invalid to invalid fields and linking actionable error messages to controls using the aria-describedby attribute.

What WCAG requirements apply to form labels and error messages?

WCAG requirements for forms mandate programmatic labels for all controls and actionable error messages, ensuring users with disabilities can successfully navigate and complete validation flows.

Does this form accessibility approach work with existing selects and input groups?

Yes, this form accessibility approach applies to existing selects and input groups, enforcing programmatic labels, accessible autocomplete patterns, and keyboard navigation across all project validation flows.

Why do my forms fail WCAG requirements for keyboard navigation and error handling?

Forms fail WCAG requirements when controls lack visible labels, clear error messages, or keyboard support, preventing users with disabilities from completing tasks during validation flows.