Form Labelling — Inclusive Design Skills

When to use it

Use on checkout, signup or settings forms to specify persistent labels, fieldset/legend groups and associated help/error text. Label placement and wording are defaults to adapt to the form; verify native required semantics and actual accessible names in implementation. This is design guidance, not assistive-technology testing or proof of conformance. No runtime testing was performed.

Compatible agents

Claude CodeOpenAI CodexGemini CLICursor

Installation

In Claude Code run /plugin marketplace add Owl-Listener/inclusive-design-skills, then /plugin → Discover and select accessible-content. For other SKILL.md-capable agents copy accessible-content/skills/form-labelling/ into the tool’s documented skills directory.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Oct 22, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.