a11y-forms

What problem does it solve?

Accessible forms often fail when controls lack proper names, grouping, input semantics, or error announcements, creating barriers for screen reader and assistive technology users.

Core Features & Use Cases

• Labelling that actually exposes an accessible name: Use explicit label associations and avoid placeholder-only labeling, including icon-only control labeling.
• Correct structure and semantics: Group related controls with fieldset and legend, and use appropriate input types to improve autofill and validation behavior.
• Reliable validation feedback: Mark invalid fields, connect errors via aria-describedby, and announce form-level issues with alert roles or aria-live.

Quick Start

Activate this skill while writing or editing HTML forms to ensure every input, group, and error message is implemented with accessible names, correct semantics, and screen reader-friendly validation announcements.