Colquhoun.AI
← All guides

Research Guides

Test a Research Task Without Requiring Device Rotation

· Colquhoun.shop editorial

A research page may fit a phone screen yet block the reader with a message asking them to rotate the device. That is a different problem from small text or a wide table: the page makes a particular device position a condition of access.

This worksheet reviews orientation restrictions in an authorized website or prototype. It is not a certification of Colquhoun.shop, and it does not imply that a visual mobile test has been performed on this site.

1. Separate an author restriction from a user preference

W3C's Orientation guidance says content should not restrict viewing and operation to one display orientation unless that orientation is essential. It distinguishes author-imposed restrictions from a user's device-level orientation lock, and notes that some people use devices mounted in a fixed position. W3C: Understanding Orientation

Record which kind of behavior you observed. A device staying in the user's chosen orientation does not establish that the website forced it. Conversely, a blocking page overlay may impose a restriction even when the underlying device can rotate normally.

2. Choose a complete reading task

Test a bounded activity such as opening a guide, expanding its method notes and following a citation. Include the intermediate states rather than checking only the initial screenshot. An article might appear normally while a later panel introduces a rotation requirement.

Use non-private test content and avoid submissions with external consequences. Record the device, browser and relevant display settings so another reviewer can distinguish page behavior from the test environment.

3. Investigate a rotate-to-continue message

In an invented research dashboard, a comparison table displays a full-screen message in portrait orientation: “Rotate to view your results.” The reviewer cannot dismiss it or reach the source notes.

The team initially explains that the table looks better in landscape. The reviewer asks a narrower question: does the information fundamentally require that orientation, or is the restriction a presentation choice? They record the evidence and ask the responsible designer to assess alternatives instead of treating preference as necessity.

A proposed repair could preserve the comparison in another usable presentation. The acceptance check should still cover the same information and actions. Removing the message while leaving the results inaccessible would not finish the task.

4. Review both starting states and transitions

Start the task separately in each orientation. Then, where the test device supports it and the user settings permit it, change orientation partway through the task. Note any lost selection, reset form or unexpectedly hidden panel.

Keep those observations distinct. A loss of state during a transition may be a usability defect without being the same issue as an orientation restriction. Precise labels help the implementer reproduce and fix the correct problem.

Also record limitations of emulation. A resized desktop viewport can reveal layout behavior, but it is not evidence that physical device rotation or platform orientation controls were tested.

5. Copy this orientation review card

Keep screenshots paired with the step that produced them. A single attractive screen does not establish that the reader can finish the journey.

Report which tasks and environments worked, which restrictions remain and what was not tested. The goal is a research experience people can use in their chosen orientation, not a blanket claim of mobile accessibility based on one layout check.

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.