# Visible Interface Text Beats Hover-Dependent Explanation ## Claim A control's identity or explanation reaches every user faster when it's printed as persistent visible text than when it's gated behind a hover or focus interaction, because the hover/focus step is an extra discovery cost that visible text doesn't impose. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds whenever layout space and visual design allow a visible label; the claim is about default priority, not an absolute ban on tooltips. - A tooltip/toggletip remains legitimate as a genuine fallback for icon-only controls in constrained layouts, or as supplementary (not sole) explanation for an already-labeled control — provided the accessible name is still programmatically exposed even when the visible tooltip hasn't been triggered. - Does not apply to progressive-disclosure patterns where hiding detail by design is the point (e.g., an optional "learn more" toggletip on a control that already has a visible label) — there the fallback role is correct, not a violation. ## Evidence WordPress 7.1's own dev note for its new `wp_get_tooltip()` / `wp_get_toggletip()` helpers states its priority ordering explicitly: "It is always preferable for interface controls to have visible, persistent text labels." Core ships the tooltip helpers anyway, but frames them as the fallback for icon-only admin controls where a visible label isn't feasible — an internal concession from the same team that builds the interface. > [!quote] It is always preferable for interface controls to have visible, persistent text labels. ## Links - [[3. Resources/Permanent Notes/Machine Consumers Make Semantic Markup a Commercial Requirement]] — because extends; both claims turn on the same accessible-name mechanism, one framed for human screen-reader users, one for AI-agent consumers of the same markup - [[3. Resources/MOCs/Open Source Governance MOC]] — because applies-in; this is Core codifying an accessibility priority order as shared infrastructure rather than leaving it to individual plugin authors ## Tests / falsifiers - Find a case where a visible label measurably underperforms a well-implemented tooltip for the same control and user population — that would break the "beats" framing, not just the "always preferable" language. - Check whether the shipped implementation actually keeps the accessible name available to assistive technology even before hover/focus triggers the visible tooltip; if the name is *only* available on hover, the claim as evidenced doesn't hold for that implementation. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/Introducing name and informational tool tips in WordPress 7.1]] — Make WordPress Core dev note, 2026-08-03, ticket #51006.