Review tooltips so their extra information is available to screen reader users. Check accessible names, meaning labels available to assistive technology, and links to the elements that trigger them, then suggest fixes and verification steps.
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for tooltips. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Review whether the extra information in tooltips reaches assistive technology such as screen readers. For elements with role="tooltip", the skill checks whether they have an accessible name or are referenced by their trigger element through aria-describedby. It identifies missing names and incorrect associations for specific elements, then explains how to fix and verify them.
Use it when adding extra descriptions to buttons or input fields, or when reviewing a shared tooltip component. It helps investigate cases where an explanation appears on screen but is unavailable through screen reader output. Keyboard interactions and focus movement are also checked when needed.
The review examines rendered HTML and states reached during interaction. Changes are verified with browser accessibility tools or assistive technology. Detailed implementation examples are provided through the accompanying references/rule.md.
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.
Tooltips often contain essential information; if they aren't properly named or associated with an element, that information remains hidden from screen reader users.
aria-describedbyVerify that all elements with role="tooltip" have an accessible name or are linked to a trigger element via aria-describedby.
Assign an accessible name to the tooltip or ensure it is correctly referenced by the element it describes.
Explain how to correctly associate tooltips with triggers so that screen readers announce the extra information.
Review the rendered markup and interactive states that affect Provide accessible names for tooltips. 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-tooltip-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.