What breaks when the pointer is removed?
Repair the blocked task and specify how to verify it.
The question
ParcelNest's address suggestions respond only to a pointer. A failed lookup adds a red border with no text or announcement. The visual design looks finished.
- Keyboard
- Tab reaches the address field and Find collection button, but no key selects an address suggestion.
- Lookup failure
- Only the border changes. Focus stays in the field and no status message is exposed.
- Visual review
- The screenshot shows sufficient space and readable type; it does not record keyboard or assistive-technology behavior.
“What breaks when the pointer is removed?”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Locate the blocking behavior
What would you do here? Open the move you’d make.
Only increase the border contrast.
Tempting, but it misses something. That leaves the selection task blocked.
Give suggestions a documented keyboard route or use a simpler supported control.
The strong move. The fix targets task completion.
Add tabindex to every element.
Tempting, but it misses something. More focus stops do not create selection behavior.
See how a strong candidate says it
“The task has no working keyboard route from suggestion to confirmed address.”
Why it works: The first priority is successful completion through an equivalent supported input route.
Step 2: Make failure understandable
What would you do here? Open the move you’d make.
Show a generic raw API error.
Tempting, but it misses something. Internal output is not useful recovery guidance.
Keep only the red border because the label is visible.
Tempting, but it misses something. It does not explain the failure or announce the update.
Explain that lookup failed and offer manual entry.
The strong move. The message gives an understandable next step.
See how a strong candidate says it
“Show a clear text error with a recovery action and expose the update appropriately.”
Why it works: Color alone does not explain the cause or next move.
Step 3: Specify the verification
What would you do here? Open the move you’d make.
Pass the component after screenshot review.
Tempting, but it misses something. The known failures are behavioral.
Check the complete keyboard route and assistive output.
The strong move. This tests the paths the repair must support.
Declare WCAG compliance from one automated score.
Tempting, but it misses something. A score does not prove all criteria or task states.
See how a strong candidate says it
“Use the keyboard through the whole task and inspect names, focus and the announced status.”
Why it works: A static image cannot prove these interactions.
Step 4: Keep a usable recovery path
What would you do here? Open the move you’d make.
Clear every field after a failed lookup.
Tempting, but it misses something. That adds unnecessary work and removes useful context.
Retain input and provide manual entry.
The strong move. The visitor can recover without starting again.
Trap focus on Retry until lookup succeeds.
Tempting, but it misses something. A service failure must not trap the user.
See how a strong candidate says it
“If lookup remains unavailable, preserve the address and let the person enter it manually.”
Why it works: The failure of one service should not erase progress or force a pointer-only route.
The answer, in short
- Decision
- Use a supported keyboard selection route, text feedback and manual address entry.
- Because
- Those changes restore the task across input methods and the failure state.
- What would change it
- Testing finds a reliable existing route or a different cause of failure.
Common traps
- Calling an attractive screenshot accessible.
- Adding ARIA names while leaving controls inoperable.
Check your answer
- Can the task finish with keys only?
- Does each control have a clear accessible name?
- Can the person understand and recover from failure?
- Which behavior still needs assistive-technology testing?
Last reviewed Nov 10, 2026