
A review note that disappears when you move the pointer onto it prevents the reviewer from reading or using the note. Check three separate behaviors: whether the note can be dismissed without moving away, whether the pointer can enter it, and whether it stays available long enough to read. Fixing only the display delay does not cover all three.
Key Takeaways
- Move from the annotation marker onto the note during review.
- Check dismissal while keeping the same pointer position or focus.
- Provide another usable route for essential instructions on touch devices.
Identify which interaction owns the note
Record the exact image revision and marker involved. A review annotation already needs a stable source and an actionable instruction, as described in the annotation handoff guide. This check concerns the website interaction that reveals the instruction, rather than what the instruction asks the editor to change.
Determine whether the note appears on pointer hover, keyboard focus, an explicit click, or another action. W3C's Content on Hover or Focus explanation covers additional content appearing through hover or focus. A modal dialog has a different interaction model and is outside that particular criterion's scope.
Check whether the reviewer can reach the note
Move onto the marker, then move directly onto the displayed note. Keep the pointer over the note while reading its full content. If a narrow gap makes it disappear during that movement, record the route and the failure rather than asking reviewers to move faster.
Repeat with magnification and a larger pointer when those are part of the intended review environment. A note visible at ordinary zoom may extend beyond the magnified viewport. Hovering the note itself lets the reviewer inspect that content instead of being forced to remain on the original tiny marker.
Check dismissal without losing the review position
If the note obscures meaningful image detail, verify a dismissal method that does not require moving pointer hover or keyboard focus. Escape is one possible method discussed by W3C; the implementation must be tested rather than inferred from the existence of a close icon.
There are exceptions to that dismissibility condition, including input-error messages and added content that does not replace or obscure meaningful content. Do not turn those exceptions into a reason to leave an ordinary annotation covering the exact defect a reviewer is trying to inspect.
Check persistence separately from appearance speed
Once revealed, the note should remain until the relevant hover or focus is removed, the user dismisses it, or the information is no longer valid. A short automatic timeout can interrupt someone who reads slowly or needs to pan a magnified view.
Use a proposed product-proof check: a note explains a label correction, but closes while the reviewer is still reading. Record that failure separately from a note that vanishes when the pointer crosses onto it. One concerns persistence; the other concerns hoverability. Increasing the delay before either failure is not equivalent to removing it.
Preserve the instruction across other input methods
Check that keyboard users can reveal and dismiss the note. On a touch device, provide a usable way to reach essential feedback without requiring hover. This is a proposed delivery requirement, not a claim that every review service offers the same control.
The fair comparison guide covers which evidence a comparison should show. Ensure its important explanation is actually reachable. If the note includes an image, apply the guidance for describing images as well.
Keep a compact acceptance record
For each tested marker, record the page revision, input method, whether the pointer reached the note, dismissal behavior and persistence result. Preserve the original feedback in a readable alternative if a component remains unresolved. Accept only after the saved review page passes the intended interaction checks; an editor screenshot showing an open note is insufficient evidence.
Related tasks
- How Do I Tell a Photo Editor Exactly Which Area Needs Changing?
- Should I Use My Generation Prompt as Alt Text for an AI Image?
- How Do I Show AI Photo Before-and-After Examples Without Misleading Viewers?
Sources and scope
- WCAG Understanding Content on Hover or Focus: Official documentation for the interaction requirements and scope discussed above.
Documentation-based guidance. The scenarios and acceptance steps are proposed; no production interaction test, certification, search-volume measurement or AI-citation result is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.