Check checkboxes, radio buttons, and switches for descriptive names that screen readers can announce. Identify missing or unclear labels, suggest appropriate HTML or ARIA labeling, and explain how to verify the changes with accessibility tools.
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for toggle fields. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
This skill checks whether checkboxes, radio buttons, and switches have names that explain their purpose when read aloud. An accessible name is the name assistive technology uses to identify a control.
It finds empty labels and unclear names, then suggests fixes using <label>, aria-label, or aria-labelledby. The review identifies specific elements and roles and explains how to verify the changes.
Use it to check whether people listening to a settings screen or form can understand what they are selecting or turning on and off. It also helps review labels in shared UI components and design systems.
The skill reviews browser-rendered HTML and interaction states as well as code. It checks native HTML semantics first, then examines keyboard operation and focus movement where needed. Changes are verified using browser accessibility tools or assistive technology.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Toggle fields like checkboxes and switches are unusable for screen reader users if they don't have a label, as the user won't know what they are turning on or off.
aria-label, aria-labelledby, or <label> for checkboxes and radiosCheck all toggle fields (checkboxes, radio buttons, switches) for a valid accessible name.
Add an accessible name to the toggle field using a label element, aria-label, or aria-labelledby.
Explain why all interactive toggle controls must have descriptive names for users to understand their purpose.
Review the rendered markup and interactive states that affect Provide accessible names for toggle fields. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/accessibility/aria-toggle-field-name
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.