Colquhoun.AI
← All guides

Research Guides

Test a Research Board Without Dragging

· Colquhoun.shop editorial

A research board may let someone arrange sources by dragging cards into groups. That can be convenient without being the only usable route. Review whether the same organizational task can be completed through simple clicks or taps, and whether the resulting evidence stays attached to the right record.

This is a manual review worksheet for an authorized interface or prototype. It does not claim that Colquhoun.shop includes a draggable research board or that any interface has passed a complete accessibility assessment.

1. Describe the outcome before the gesture

Choose a specific task: move one source from “To review” to “Verified,” place a citation before another citation, or change a comparison range. Record the starting state and expected final state. Use harmless sample records so testing cannot accidentally publish, delete or notify anyone.

Do not write “test drag and drop” as the whole acceptance criterion. The underlying task matters more than reproducing a particular movement.

2. Look for a pointer route without dragging

W3C's Dragging Movements guidance requires functionality operated through dragging to have a single-pointer alternative that does not require dragging, subject to essential-functionality and unmodified user-agent exceptions. It explicitly distinguishes this from keyboard accessibility: a keyboard shortcut alone does not necessarily supply a click-or-tap alternative. W3C: Understanding Dragging Movements

Inspect the actual controls offered to a reader. Record the sequence needed to complete the task without holding a pointer down while moving it. If the alternative is hidden in a menu, include how the menu is found and opened in the test record.

3. Compare results using identifiable records

In an invented research board, three cards have similar titles but different source URLs. A reviewer moves the middle card to the verified group using the non-drag route, then checks its URL, notes and group membership. Merely seeing a card appear in the target group is not enough to establish that the correct record moved.

Reset the fixture and perform the same task through dragging. Compare the final records, not only their screen positions. If one route changes the saved group while the other changes only the visual arrangement, the two routes do not deliver the same tested outcome.

This is a proposed test fixture, not a report of a defect found in a real product. Keep examples clearly separate from observed findings.

4. Test boundaries and interruption

Include the first and last item in a list, an empty target group and an item with a long label. Check whether narrow layouts conceal the alternative controls. Record the browser and viewport so a later reviewer can reproduce the case.

Try canceling before committing the change where the interface supports cancellation. Confirm which state remains afterward. If the action is immediately saved, record that behavior rather than assuming a separate save step exists.

Evaluate keyboard and assistive-technology behavior separately. A successful pointer alternative does not establish that labels, focus handling or announcements are correct.

5. Keep a task-equivalence record

After an authorized repair, repeat both routes with the same fixture. Verify that improving one path has not removed another path that people rely on.

Close with a precise statement such as “the sampled source can be reassigned using clicks, with its URL and notes preserved.” That is stronger than saying a board is accessible simply because a move button was added.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.