
Accessible Website Dialogs: Plan Focus, Closing, and the Return Journey
Build useful modal dialogs with deliberate focus, clear dismissal, accessible errors, and a reliable return to the surrounding page.
Web Development
Design website tooltips as optional help, with clear keyboard and pointer behavior, persistent essential instructions, and practical accessibility checks.

LET’S BUILD SOMETHING USEFUL
Talk to Ataraxy Developers about your website, app, or custom software.
A small question-mark icon can make a busy form feel cleaner, but it can also conceal the sentence someone needs to complete it. Consider a service enquiry form with a tooltip beside “Project reference.” If the reference is optional, that fact belongs beside the field. If a short explanation describes where an existing customer can find it, supplementary help may be appropriate. The design decision starts with the importance of the information, before choosing a popup component.
Good tooltips support a task without becoming another task themselves. They explain unfamiliar terminology, expand a short label, or describe a secondary detail. They should work with a keyboard and pointer, remain readable when enlarged, and have an understandable alternative on touch devices. The following review applies to custom website tooltips rather than treating a browser’s default title bubble as a complete help system.
Classify each proposed explanation as essential instruction, optional clarification, or an action. Required formats, additional charges, submission consequences, and errors need a dependable place in the page. They should not depend on discovering an icon. Optional definitions can sit in a tooltip when they are short enough to read without interaction. A link to a policy, an editable setting, or a multi-paragraph guide needs a different presentation.
For example, a budget field might visibly say “Enter the total project budget in USD.” A short explanation of what the estimate includes could appear in supporting help. If the explanation changes which amount the customer should enter, move it into the visible instructions instead. Review the form without opening any tooltips: a person should still understand what to supply and what submission will do.
An icon without a useful accessible name does not explain itself to someone navigating with a screen reader. Name a dedicated help trigger for its subject, such as “About project references,” and retain a visible association with the relevant field. Avoid dozens of identical “Help” controls that become indistinguishable when encountered outside their visual surroundings. Keep the field’s own label intact; supplementary help should not replace it.
The WAI-ARIA tooltip pattern describes a noninteractive tooltip linked to its trigger through aria-describedby, with focus remaining on the trigger. The page explicitly identifies the pattern as work in progress, so use it as supporting guidance alongside accessibility requirements and testing. If a proposed popup needs focusable links or controls, review a disclosure or dialog design instead of adding them inside a tooltip.
The WCAG explanation of content on hover or focus discusses dismissible, hoverable, and persistent additional content, including relevant exceptions. In a practical tooltip review, verify that moving the pointer from the trigger onto the explanation does not close it prematurely, that keyboard focus can reveal the same help, and that Escape dismisses an obstructing popup without activating anything else.
Model these behaviors together. A component that closes on pointer exit even while its trigger retains keyboard focus can flicker or reopen unexpectedly. Record which conditions currently request visibility, and record dismissal for the current interaction. After Escape, a tiny pointer movement should not immediately force the same explanation back over the page. Test leaving and re-entering the trigger, changing focus, and opening help inside a larger dialog.
Touch users cannot rely on a stable hover state. Decide whether tapping a clearly labeled help button opens a short disclosure, exposes an inline explanation, or uses another accessible component. Do not make the first tap on a submit button reveal a tooltip and the second tap submit without explaining that behavior. The primary action should remain predictable across mouse, keyboard, and touch use.
A useful implementation review compares the information available through each route, rather than insisting on identical animation. On a narrow screen, an inline help region may be easier to read than an overlay. Its close control and return path should be obvious. If a component adapts its presentation, preserve the relationship between the trigger and explanation and avoid leaving hidden duplicate content in the reading order.
Place a tooltip where it does not cover the control being explained, the current input, or another essential instruction. Check triggers near every viewport edge and within scrollable containers. A popup positioned correctly on the full desktop page may be clipped by a card’s overflow rule or appear beneath a sticky header. Its position must also survive text wrapping and browser zoom.
Keep text concise because the popup has limited space, but do not solve overflow by making the type too small. Prefer a short definition and move longer guidance into the page. Test a translated explanation that occupies twice the original space as a design exercise, then test actual translations separately. When the trigger scrolls out of view or disappears after a form change, close its help rather than leaving an orphaned floating panel.
Treat tooltip text as product content with an owner. If a field’s validation rule changes, its visible instructions and optional help must change together. Store related wording near the field definition or another maintained content source, rather than scattering slightly different versions across desktop and mobile components. A compact help surface is particularly vulnerable to becoming stale because teams rarely review it in ordinary screenshots.
AI can suggest shorter definitions or identify terminology inconsistencies across a form catalogue. A reviewer still needs to check the actual business rule and whether the text belongs in a tooltip at all. Do not let an automated rewrite remove a condition simply to fit a character target. Maintain a small example set showing the original rule, the approved explanation, and the field behavior it describes.
Test one representative help item using only Tab, Shift+Tab, Escape, and the relevant activation keys. Repeat with a pointer that moves slowly into the popup, a touch device, a screen reader, enlarged text, and a narrow viewport. Check that the explanation is announced usefully without replacing the control’s name or causing excessive repeated announcements. Confirm that dismissal restores an unobstructed view of the task.
Then test state changes: disable the field, remove a conditional section, scroll its container, navigate back, and open a second help item. Include these cases in the component’s acceptance notes so future changes are assessed against behavior, not just appearance. Record defects precisely: “Escape closes the dialog as well as the tooltip” is more actionable than “keyboard support feels wrong.” Fix the interaction layer responsible for the conflict.
An effective tooltip adds optional understanding while the page remains usable without it. Keep essential instructions visible, identify the trigger clearly, coordinate focus and hover, provide a deliberate touch experience, and test the explanation in changing layouts. Short help earns its place when it reduces uncertainty without concealing a rule or interrupting the action a visitor came to complete.
LET’S BUILD SOMETHING USEFUL
Talk to Ataraxy Developers about your website, app, or custom software.