Menu

Our comparison tables cut off the competitor's column on a 320px phone, and the rounded corner is why you cannot scroll to it
📰

Our comparison tables cut off the competitor's column on a 320px phone, and the rounded corner is why you cannot scroll to it

DEV Community: css·Daniel Pertu·19 days ago
#IBSCD3BX
#devtocss#devto#dev#table#column
Reading 0:00
15s threshold

WCAG 1.4.10 asks that content reflow to 320 CSS pixels without needing to scroll in two directions. 320 is a small phone at default zoom, or a normal phone at 400% zoom, which is the case the criterion is really about.

I had never tested our site at 320. So I drove Chrome over the DevTools protocol, set the device metrics to 320, 360, 390 and 430 by 844, loaded six representative pages at each width, and for every element inside main , header and footer compared its bounding rectangle against the viewport.

The good half

The pages that make up most of the site pass cleanly. A guide , a question page , a free tool : at all four widths, document.documentElement.scrollWidth equals clientWidth . No element sticks out, nothing scrolls sideways, the body copy wraps into a 288px column at 320 and reads fine.

That is not a compliment to anybody's craft. Those pages are a heading, paragraphs and a labelled list rendered by one component, and a column of text is the easiest thing in the world to reflow.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.