The top and the start side (which follows writing direction) are granted higher rank by default

What it is

Two modules, matched on weight, colour and size: one at the top-start of a left-to-right UI, one at the bottom-end. After a short presentation the top-start one is more often treated as “the more important block.” Mirror the UI for right-to-left and the advantage follows the start side; it is not nailed to the geometric top left. Top, and the side where writing starts, carry a default rank bonus. It is a prior left by reading habit, not a physical law of coordinates. Gutenberg-style zone stories are at best a coarse description of that prior, not a map of every page.

Why it happens

On a new viewport, eye and attention go first to the habitual page origin: upper start for horizontal scripts, then unfold through the content. Objects met earlier get a little more encoding, so “appeared first” is read as “matters more.” The bonus is weak and only visible when other weights are close. It is not “above always beats below”: a lower module on the start side can still be visited before decoration on the opposite top, because unfolding follows reading direction rather than sliding down a diagonal. Vertically, the top of the first screen is often treated as a title slot — layout convention stacked on the reading prior. On a full-bleed canvas with no “header” concept, the top bonus thins.

Studying it

Take a pair of modules that differ only in position, lock every other visual attribute, and measure first fixation and importance ratings in LTR and RTL shells. Independent variables are quadrant and script direction; the dependent is whether the share chosen as “more important” flips with the start side. LTR bias to top-start and RTL bias to the mirrored corner is the prior. Do not use materials with a large image or high saturation; those overwrite position. Report desktop and phone apart: a single mobile column crushes left/right and leaves mostly up/down.

Where it stops holding

A strong task (“find the price”) sends people to a remembered slot and the prior yields. Bottom navigation pins primary actions to the thumb arc; importance there is bound to reach, and the top bonus does not run the action hierarchy. Games and map canvases have no reading-page origin. Vertical type starts at the top-end or bottom-end; copying horizontal top-left reverses it. Writing the prior as “the important thing must sit top-left” fails outright in RTL and in products whose actions live in a bottom bar.

Applying it

• When other cues are deliberately tied (two identical entries), put the one you want treated as primary at that language’s top-start, not at geometric (0, 0) and done.
• When mirroring for another script, the start-side module flips with the origin. Do not lock “main entry” to pixel coordinate (0, 0).
• Do not ask this bonus to outrun a large image or a saturated button. It cannot.
• Check: two identical cards, quadrant swapped, five seconds, “which looks like the main feature.” LTR should lean top-start; RTL readers should flip. If they do not, mirroring may have flipped containers without flipping content origin. Then enlarge one card slightly and see whether the position advantage vanishes at once — that calibrates how weak this prior is, so real pages do not bet the farm on position.

Related

• Same group: F3.09.2 Positional rank can be overwritten by stronger visual weight · F3.09.3 The same position does not mean the same rank under every layout mode · F3.09.4 Rank that relies on position alone, with no other visual cue, is easy to miss
• Nearby: F3.04.3 Scan patterns change with reading direction and content type · F1.14 Semantic conventions of position
• Search terms: reading direction · start side · positional hierarchy · Gutenberg diagram