Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Design form labels, instructions, and grouping that work for screen readers and cognitive accessibility.
Install Form Labelling
$ npx skills add Owl-Listener/inclusive-design-skills --skill form-labelling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills form-labelling --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/accessible-content/skills/form-labelling .claude/skills/form-labelling && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "form-labelling" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/form-labelling into .claude/skills/form-labelling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-labelling", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/form-labellingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/inclusive-design-skills --skill form-labelling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills form-labelling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/accessible-content/skills/form-labelling .agents/skills/form-labelling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "form-labelling" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/form-labelling into .agents/skills/form-labelling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-labelling", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill form-labelling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills form-labelling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/accessible-content/skills/form-labelling .cursor/skills/form-labelling && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "form-labelling" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/form-labelling into .cursor/skills/form-labelling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-labelling", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/inclusive-design-skills.git --path accessible-content/skills/form-labelling--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/inclusive-design-skills --skill form-labelling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills form-labelling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/accessible-content/skills/form-labelling .gemini/skills/form-labelling && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "form-labelling" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/form-labelling into .gemini/skills/form-labelling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-labelling", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/inclusive-design-skills form-labellingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/inclusive-design-skills --skill form-labelling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/accessible-content/skills/form-labelling .github/skills/form-labelling && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "form-labelling" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/form-labelling into .github/skills/form-labelling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-labelling", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill form-labelling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills form-labelling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/accessible-content/skills/form-labelling .opencode/skills/form-labelling && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "form-labelling" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessible-content/skills/form-labelling into .opencode/skills/form-labelling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-labelling", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
form-labelling- GitHub stars
- 103
- Token cost
- ~869 tokens
- SKILL.md length
- 421 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design form labels, instructions, and grouping that work for screen readers and cognitive accessibility.
- Reviewing forms
- SKILL.md covers Core Rules, Grouping Patterns, Instruction Patterns and Common Mistakes, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Any data entry interface
What it does
Form Labelling is an agent skill from Owl-Listener/inclusive-design-skills. 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.
Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Accessibility. The repository describes itself as: Inclusive design skills for AI coding agents — from cognitive accessibility to adaptive interfaces, inclusive research, and accessibility decision-making. The licence is MIT.
When your agent uses it
- Reviewing forms
- Any data entry interface
- Form instructions
- Form accessibility
Example prompts
- “/form-labelling”
What it can do on your machine
Read from SKILL.md and the folder at commit 6e0740f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Form Labelling loads about 869 tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 421 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 421 words, ~869 tokens.
Download SKILL.mdSave it as
.claude/skills/form-labelling/SKILL.md (or your agent's skills folder).- name
- form-labelling
- description
- 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.
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
<label>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
<fieldset>and<legend> - 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
Show full SKILL.md (172 more words)Show less
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
<label>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
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in accessible-content/skills/form-labelling of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
Form Labelling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Form Labelling this skillOwl-Listener/inclusive-design-skills | 103 | — | ~869 | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 98 repos | ~308 | Automated safety check: Pass | None | |
| Accessibility Reviewmarkmead/hyperui | 12k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Web Animation DesignbaptisteArno/typebot.io | 11k | 2 repos | ~2.7k | Automated safety check: Pass | Custom licence | |
| Accessibility Fixeribelick/ui-skills | 9.5k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Wcag Audit PatternsvmDeshpande/ai-agent-automation | 178 | 11 repos | ~610 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
Baseline UI
ibelick/ui-skills
Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.
More from Owl-Listener/inclusive-design-skills
All 55 skills in this repoAssistive Technology Scenarios
Owl-Listener/inclusive-design-skills
Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.
Error Prevention and Recovery
Owl-Listener/inclusive-design-skills
Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.
Accessible Heading Structure
Owl-Listener/inclusive-design-skills
Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.
Ability Spectrum Mapping
Owl-Listener/inclusive-design-skills
Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.
Accessibility Debt Tracking
Owl-Listener/inclusive-design-skills
Track and manage accessibility debt — known accessibility issues that have been deferred.
Accessibility Testing Strategy
Owl-Listener/inclusive-design-skills
Plan what to test, how to test, and who should test for accessibility.
Related
Categories
Questions about Form Labelling
What does Form Labelling do?
Design form labels, instructions, and grouping that work for screen readers and cognitive accessibility. Form Labelling is an agent skill from Owl-Listener/inclusive-design-skills. Design form labels, instructions, and grouping that work for screen readers and cognitive accessibility.
When should I use Form Labelling?
Form Labelling fits situations like: reviewing forms; any data entry interface; form instructions; form accessibility.
How do I install Form Labelling in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill form-labelling -a claude-code`. Or copy the skill folder (accessible-content/skills/form-labelling in Owl-Listener/inclusive-design-skills) into .claude/skills/form-labelling in your project. Claude Code loads it when a task matches its description.
How do I install Form Labelling in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill form-labelling -a codex`. Or copy the skill folder (accessible-content/skills/form-labelling in Owl-Listener/inclusive-design-skills) into .agents/skills/form-labelling in your project. Codex loads it when a task matches its description.
Can I use Form Labelling in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/inclusive-design-skills --skill form-labelling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/form-labelling, .gemini/skills/form-labelling, .github/skills/form-labelling and .opencode/skills/form-labelling in your project.
What does Form Labelling need to run?
SKILL.md names no scripts, command-line tools or credentials: Form Labelling is instructions for the agent only.
Does Form Labelling access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Form Labelling safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Form Labelling use?
Form Labelling is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Form Labelling use?
About 869 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Form Labelling?
Skills that share tags, products or a category with Form Labelling: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Form Labelling?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 103 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.
Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.