RF-07 · Exempt content
Do not raise tickets against these three
Exempt content
1.4.10 allows a two-axis layout where the content genuinely needs one. Three kinds qualify, and all three are here so a tester can recognise a legitimate exception rather than file a ticket against it. The tab row is itself part of the test: the labels have to stay reachable and readable at every width.
Still check
The exemption covers the table, the map and the player themselves. Everything around them, including these tab labels and the captions, still has to reflow.
Exempt · No ticket
Click a label to switch. Each panel carries its own reasoning.
Expected results matrix
A table keeps its meaning only if a row can be read across against its column heading, so it is allowed to scroll sideways. The correct technique is the one used here: the scroll belongs to the table's own frame, not to the page. Everything outside the frame still reflows.
Case
At 400% zoom
At 320px
Expected
RF-01
B: text over the subject
B: text past the frame edge
B fails
RF-02
B: paragraph ends mid-sentence
B: long filename scrolls sideways
B fails
RF-03
B: third column off screen
B: row never stacks
B fails
RF-04
B: boxes print over each other
B: overlap plus stage clipping
B fails
The full matrix for all seven cases is on the results log.
