A live-score article can fit a phone screen until an embedded scoreboard or a long team name forces the entire page sideways. Test the article at the narrowest supported layout with the actual widget and headlines in place. A blank template will miss the very elements that cause the problem.
W3C’s reflow guidance tests vertically scrolling content at an equivalent width of 320 CSS pixels. Content and functionality should remain available without scrolling in two directions, with an exception for parts whose meaning or use requires two dimensions. A scoreboard table may need its own scroll area. The story, score summary and navigation around it should still fit.
Illustrative example. A football article embeds a full league table. At high zoom, the table extends past the viewport and pushes the paragraphs off screen. Keep the table in its own labelled scroll area, and put the result and its relevance in ordinary text above it. Verify that the last column can be reached with a keyboard and that a reader can continue down to the article.
Test the actual publisher template at normal size and at high zoom. Record which element causes overflow and where it first appears. Give the editor a prose fallback if the embed cannot be repaired before publication. Review sports publisher options and the placement process before committing to a widget-heavy brief.
Publisher inventory · How placements work · Free article video