Grouping and regions cut the scan path

What it is

Group scanning (also called container scanning) walks a few large regions first, then the controls inside the chosen region. The path changes from “through every button” to “region, then control.” Regions are not visual styling. They rewrite scan topology so one choice skips an entire irrelevant stretch.

Why it happens

Flat scanning grows linearly with stops. After a hierarchy, cost is roughly “number of groups plus items in the target group.” If navigation, main content, and a toolbar are three enterable containers, a button in main content no longer pays for twenty header icons.

The group has to exist as a container in the accessibility tree, and the scanner has to treat that container as one cell. Card chrome, whitespace, and shadows are invisible to the scanner. One group for the whole page is no grouping. A group every two buttons turns “pick a group” into another long queue. Cuts that work follow tasks: first “which kind,” then “which action.”

Studying it

Run the same UI in two scan structures: flat item scan versus container hierarchy. Measure steps to the same target and the cost of backing out of a wrong group.

Independent variables: container depth, group size, whether group labels are spoken by the scanner. Dependent variables: step count, wrong-group entries, time to leave a group and pick another.

Platforms differ. Some scanners cluster by view hierarchy; others mostly walk focusable controls. Report which scanner was used. iOS auto-grouping is not Android’s default.

Where it stops holding

A five-control dialog is faster flat; grouping is an extra step. If every newly inserted chat bubble becomes its own group, the group queue outgrows the old item queue. A custom canvas that exposes no region nodes cannot be entered as “this block”; grouping stays visual only. Skip links for keyboard users are the same idea on another channel, but skip counts are not scan steps.

Applying it

• Cut the page into a few regions the scanner can enter and leave: primary navigation, main content, footer tools—not fifty buttons in one chain.
• Give each region a speakable name so choosing a group is not a guess.
• Verify: does Switch Control walk regions first and only then the interior? If the highlight ticks from the logo through ads and share icons before any body button, grouping does not exist for scanning.

Related

• Same group: J3.08.1 Sequential scanning makes path length the cost of every action · J3.08.2 The number of focusable items decides whether scanning stays usable
• Nearby: J3.03 Skip to Main Content · J2.14 Headings and Landmarks · J5.05 Switch and Eye-gaze Input
• Search terms: group scanning · container scanning · switch access regions