Forms Specialist

Enforce WCAG accessibility standards on web form labeling and error handling.

387|42|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Community-Access/accessibility-agents --skill forms-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Forms Specialist
Source: https://github.com/Community-Access/accessibility-agents/tree/main/.gemini/extensions/a11y-agents/skills/forms-specialist
Command: npx skills add https://github.com/Community-Access/accessibility-agents --skill forms-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all web forms are accessible to users with disabilities, preventing them from being blocked by inaccessible input interfaces.

Core Features & Use Cases

  • Labeling & Association: Ensures every form control has a programmatically associated label.
  • Error Handling: Provides clear, accessible error messages and feedback mechanisms.
  • Grouping: Uses fieldset and legend for logical grouping of related controls.
  • Autocomplete: Leverages autocomplete attributes for user convenience and assistive technology compatibility.
  • Use Case: Reviewing a complex multi-step checkout form to ensure all inputs are correctly labeled, error messages are announced, and required fields are clearly indicated for screen reader users.

Quick Start

Review the provided HTML form code for accessibility issues related to labeling and error handling.

Frequently Asked Questions about Forms Specialist

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

FAQPage Schema
How do I make HTML forms accessible for screen reader users?

Making HTML forms accessible requires enforcing WCAG standards for labeling, error handling, validation, and grouping. Every form control needs a programmatically associated label so assistive technologies can announce inputs correctly to screen reader users.

What is the best way to handle form validation errors for WCAG compliance?

WCAG-compliant form validation provides clear, accessible error messages and feedback mechanisms. Error notifications must be programmatically announced to assistive technologies so users understand validation failures and required fields.

Does accessible form markup work with vanilla HTML and web development frameworks?

Accessible form markup applies to all web frameworks and vanilla HTML, CSS, and JS. It covers standard inputs, selects, textareas, checkboxes, radio buttons, date pickers, file uploads, and custom controls across any environment.

When do I need fieldset and legend elements in web forms?

You need fieldset and legend elements when grouping related form controls for accessibility. They provide logical grouping and descriptive context for related inputs, ensuring assistive technology users can navigate complex form sections.

Why are autocomplete attributes important for form accessibility?

Autocomplete attributes enhance form accessibility by leveraging user convenience and assistive technology compatibility. They allow browsers and assistive tools to automatically populate inputs, reducing manual entry barriers for users with disabilities.