Ensure HTML forms implement accessible names, grouping, and validation feedback.
npx skills add https://github.com/TheNordicOne/ngx-formbar --skill a11y-forms
Please help me install this Agent Skill. Skill: a11y-forms Source: https://github.com/TheNordicOne/ngx-formbar/tree/main/.claude/skills/a11y-forms Command: npx skills add https://github.com/TheNordicOne/ngx-formbar --skill a11y-forms
Accessible forms often fail when controls lack proper names, grouping, input semantics, or error announcements, creating barriers for screen reader and assistive technology users.
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.
High-intent search queries and answers about installing and using this skill.
To make HTML forms accessible to screen readers, you must use explicit label associations, group related controls with fieldset and legend, and use appropriate input types to ensure correct semantics and autofill behavior.
To announce validation errors with aria live regions, mark invalid fields, connect error messages via aria-describedby, and use alert roles or aria-live attributes to announce form-level issues to screen reader users.
Screen readers fail to announce form input names correctly when using placeholder-only labeling or missing explicit label associations; you must bind labels to inputs to expose a proper accessible name.
Yes, adding autocomplete attributes to appropriate input types improves autofill behavior and is required for accessible forms, ensuring credential and personal fields are properly identified by assistive technologies.
The best way to group related form fields for accessibility is using the fieldset and legend elements, which provide semantic grouping and descriptive context that screen readers use to navigate controls.
To label icon-only form controls for screen readers, provide an explicit accessible name instead of relying on visual icons alone, ensuring the control's purpose is announced correctly to assistive technology users.
TheNordicOneGuide semantic HTML authoring with landmarks and Baseline 2024 elements.
JaivishChauhanApply WCAG-compliant semantics to portfolio pages for keyboard and screen reader accessibility.
hdickoCreate accessible HTML web forms with ARIA and server-side handling.
t-stringsReview frontend UI code for HTML semantics, ARIA, keyboard navigation, and contrast.
