Content on Hover or Focus — tooltip ARIA pattern
Tooltip implementations should follow the WAI-ARIA Authoring Practices Tooltip pattern: tooltip element gets `role="tooltip"`, the trigger element gets `aria-describedby` pointing at the tooltip id, and Escape dismisses while keeping focus on the trigger.
What it requires
A focused subsection of 1.4.13 covering the canonical tooltip ARIA pattern. The pattern consists of: (1) tooltip container `<div role="tooltip" id="...">`; (2) trigger `<button aria-describedby="...">`; (3) JavaScript that shows the tooltip on focus + hover and dismisses it on Escape + blur + pointer-leave (with the hoverable + persistent guarantees from 1.4.13 itself).
WAI-ARIA APG documents the pattern in detail with reference implementations.
Common Shopify failure
Theme pricing-page tooltips ship as plain `<div>` with no `role="tooltip"` and the trigger has no `aria-describedby`. Screen readers do not announce the tooltip when the trigger receives focus.
How to fix it
AccessComply rewrites tooltip markup to follow the WAI-ARIA APG Tooltip pattern: `role="tooltip"` on the popup, `aria-describedby` on the trigger, JavaScript handlers for Escape + focus + hover + blur.
Primary source: W3C — WCAG 2.1 Understanding 1.4.13 (tooltip ARIA)