Colquhoun.AI
← All guides

Research Guides

Review Research Interactions With Unnecessary Motion Disabled

· Colquhoun.shop editorial

A comparison panel slides across the screen whenever a researcher changes a filter. The movement looks polished in a demonstration, but the research task is to compare evidence, not watch a transition. A motion review asks whether the same task remains understandable when unnecessary movement is removed.

This worksheet covers interaction-triggered motion in research interfaces. It does not claim that Colquhoun.AI includes a motion-testing tool or certify any site's accessibility.

1. Identify the trigger

The W3C explanation of Animation from Interactions describes a Level AAA criterion: interaction-triggered motion animation can be disabled unless essential to the information or functionality. It distinguishes this from automatically initiated movement addressed by Pause, Stop, Hide. Avoiding unnecessary animation, providing a disabling control and respecting reduced-motion preferences are possible approaches.

Start with an action inventory rather than a list of decorative effects. Record what happens after a filter change, an expanded result, a chart selection or a scroll. The trigger helps a reviewer repeat the observation and identify the component responsible.

2. Define the unchanged task

Write a short acceptance statement before proposing a repair. For example: after choosing another comparison period, the researcher can identify the selected period, read the corresponding results and continue from the same control.

This statement prevents a superficial fix that removes movement by hiding the results themselves. The reduced-motion version should still communicate the updated state and preserve the working path through the interface.

3. Review a fictional sliding comparison

Imagine a fictional dashboard that moves the old comparison card offscreen and brings the new card in from the opposite side. The researcher has requested a new date range, not a spatial demonstration. The reviewer proposes showing the updated card without the travel animation.

They test the same date-range action again under the supported reduced-motion setting. They check the displayed period, values, source links and keyboard position. A still image of the final card cannot show whether the transition actually stopped, so the evidence record includes the observed interaction.

If the new card appears but the interface remains stuck waiting for an animation to finish, the proposed repair has introduced a functional defect. The task-level acceptance statement catches that problem.

4. Check more than the first component

A shared interface can contain several independently implemented effects. Test a representative set of the actions in the inventory, including components that load later. Record the browser, operating-system preference and any application setting used.

Do not infer that all movement is disabled because one panel behaves differently. Likewise, a search through source code can locate a reduced-motion rule, but does not prove that the observed interaction follows it. Keep implementation evidence and behavioral evidence separate.

5. Copy this motion-review card

If an effect is described as essential, record the concrete information or function that depends on it. A general preference for a modern appearance is not a task explanation.

6. Report a bounded conclusion

A useful result names the interactions checked and explains how their non-moving alternatives behaved. It does not turn a few successful tests into a whole-site conformance claim. Keep untested components visible in the follow-up record so the next reviewer can extend the work without repeating it.

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.