Form Labelling

Community

Owl-Listener

form-labelling

Design form labels, instructions, and grouping that work for screen readers and cognitive accessibility. Use when designing or reviewing forms, input fields, checkboxes, radio buttons, select menus, or any data entry interface. Triggers on: form label, label, input label, fieldset, legend, placeholder, form instructions, form group, radio group, checkbox group, required field, form accessibility.

Overview

Publisher	Owl-Listener
Repository	`inclusive-design-skills`
Skill name	`form-labelling`
Stars	108
Forks	28
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Owl-Listener on GitHub. Read the source before you install it.

Installation

Install the Form Labelling AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/form-labelling
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/form-labelling

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git /tmp/inclusive-design-skills
mkdir -p .claude/skills
cp -r /tmp/inclusive-design-skills/accessible-content/skills/form-labelling .claude/skills/form-labelling

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Form Labelling in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Form Labelling on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Form Labelling is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Form Labelling

Every form field needs a visible, persistent label that is programmatically associated with the input. This is the single most common accessibility failure on the web — and the easiest to fix.

Core Rules

Every Input Has a Visible Label

Use element with for/id association
The label must be visible at all times — not just as placeholder text that disappears on focus
Labels go above the input (most accessible and most scannable)
Never use placeholder text as the only label — it disappears when the user starts typing

Labels Describe What to Enter

Good: "Email address"
Bad: "Enter your info here"
Good: "Date of birth (DD/MM/YYYY)"
Bad: "Date"
Include format hints in the label or help text, not just in placeholder

Required Fields Are Clear

Mark required fields with visible text: "required" or *
If using , explain it at the top of the form: " = required"
Use aria-required="true" for programmatic indication
Better: make most fields required by design and mark the optional ones instead — "Company name (optional)"

Grouping Patterns

Related Fields Need Fieldsets

Group related fields with and
Radio buttons: always group with fieldset
- Legend: "Preferred contact method"
- Options: Email, Phone, Text
Checkboxes: group when they share a question
- Legend: "Which topics interest you?"
- Options: Design, Engineering, Product
Address fields: group under "Delivery address" or "Billing address"

When You Have Multiple Forms

Each form section should have a heading or legend
Sections should be visually and structurally separated
Progress indicators help users understand where they are

Instruction Patterns

Help Text

Place help text between the label and the input
Associate with aria-describedby so screen readers announce it
Good: "Must be at least 8 characters with one number"
Keep instructions concise — one sentence

Error Association

Error messages must be programmatically linked to the field (aria-describedby or aria-errormessage)
Place error text directly below the field, not in a remote banner
Include the field label in the error: "Email address: please enter a valid email"

Common Mistakes

Placeholder as label — disappears on input, invisible to many screen readers
Icon-only labels — a magnifying glass without text "Search" label
Labels far from inputs — spatial separation breaks the visual association
Labels that change — don't change label text based on input state
Unlabelled buttons — every button needs visible text or aria-label

Assessment Checklist

Every input has a visible associated with for/id
No placeholder-only labels
Required fields are indicated visually and programmatically
Related fields are grouped with fieldset/legend
Help text is associated with aria-describedby
Error messages are linked to their field
All buttons have visible text labels

Frequently asked questions

What does the Form Labelling AI skill do?

Why use Form Labelling on TypingMind?

Because you install it once and use it with any model. Form Labelling is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Form Labelling in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/form-labelling. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Form Labelling?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Form Labelling?

As many as you like. As long as a model supports skills, you can use Form Labelling with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Form Labelling AI skill free?

Yes. It is published on GitHub by Owl-Listener under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Diagram Maker

openclaw

OrganizationPopular

Create SVG/HTML or Excalidraw diagrams for concepts, architecture, flows, and whiteboards.

Grill With Docs

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Grill Me

A relentless interview to sharpen a plan or design.

Brand Discovery

Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Form Labelling

Core Rules

Every Input Has a Visible Label

Labels Describe What to Enter

Required Fields Are Clear

Grouping Patterns

Related Fields Need Fieldsets

When You Have Multiple Forms

Instruction Patterns

Help Text

Error Association

Common Mistakes

Assessment Checklist

Frequently asked questions

Related AI Skills

Set up your own AI workspace now