Research Guides
Test Focus Arrival Separately from Opening a Research Result
A researcher presses Tab to inspect a report link. Before they choose it, a new page opens. They were navigating the controls, not requesting a new report. This distinction is easy to miss when testing only with mouse clicks, because a click can both focus and activate a control.
This guide provides a focus-only test for research interfaces. It does not claim that Colquhoun.AI runs automatic accessibility certification or offers a particular interface component.
1. Separate arrival from activation
The W3C explanation of On Focus says that receiving focus must not initiate a change of context. Examples include submitting a form, opening a new window or moving focus elsewhere. It also notes that a content change is not necessarily a context change. The review should identify the actual effect rather than treat every visual response as a failure.
For each control, distinguish three events: moving focus onto it, changing its value and activating its action. Testing one event does not establish the behavior of the other two.
2. Reproduce a fictional report-link defect
Imagine a fictional research page with three saved report links. Its designer has attached the open-report action to a focus event so that the interface feels immediate. Tabbing to the first link navigates away before the reviewer can reach the second.
The issue record should say that receiving keyboard focus triggered navigation. Saying only that the link opens the wrong way loses the essential reproduction detail. The intended repair is to keep navigation attached to deliberate activation, while leaving ordinary focus available for inspection.
After the repair, the reviewer tabs across all three links without activating them, then deliberately opens the selected report. Both paths matter: preventing the surprise must not leave the link unusable.
3. Run a focus-only pass
Start from a known page state with synthetic or public test material. Move through the controls with the keyboard without submitting, selecting or opening anything. Record the focused component and any navigation, dialog, unexpected focus movement or substantial page rearrangement that follows.
If the page changes, stop and identify the trigger before repeating the action. Do not accidentally resubmit forms or launch paid research while collecting evidence. Where a safe test fixture is unavailable, document the limitation and inspect the implementation without claiming an interaction pass.
4. Check helpful behavior for unintended interruption
A field may show guidance when it receives focus. Ask whether that guidance leaves the researcher able to continue through the form, or whether an unsolicited dialog takes over the task.
In a fictional URL-entry form, a short inline explanation can remain beside the field while the user types. A separate help action can open a more detailed dialog when requested. This is a design proposal to test, not a universal requirement that every help message use the same presentation.
5. Copy this focus-event record
- Page and state: starting location and relevant test data.
- Component: visible label and identifier.
- Input event: focus arrival, value change or activation.
- Observed effect: what changed and where focus ended.
- Expected effect: behavior appropriate to that specific event.
- Reproduction: exact keys and environment used.
- Repair: event handling changed without removing the control's purpose.
- Retest: focus-only navigation and intentional activation results.
Test repeated instances when they share a component. A corrected report list does not prove that the same interaction is fixed in search results or account history.
6. Report the tested boundary
A clear completion note names the controls and states that were inspected. Keep focus visibility, keyboard order and value-change behavior as separate checks rather than treating this one test as a complete keyboard audit.
The outcome is predictable navigation: researchers can reach a control, understand it and choose whether to act. Moving through the page should not silently make that choice for them.