The default font-size in browsers sits at 16px, and Alvaro Montoro has suggested raising it to 1.25rem as a quick improvement to almost any project. Sebastian Laube pushes back on taking that step automatically: on a smartphone a bigger base size consumes too much room, and the sudden increase would likely irritate many readers. His own compromise is a 1.2rem base starting at a set viewport width — but he notes this needs care too, since the transition leaves grey areas where media queries unexpectedly fall back into a different range.
Reading the disagreement
The two positions are not actually in conflict. A default of 16px does feel small to some readers, but adopting a blog post's recommendation wholesale is a different matter from testing it. A font-size bump may well be the right call, provided it follows from relative sizing and from what the people actually using the interface report — not from a single source.
The question underneath it
Laube ends on the more interesting problem, quoting:
Should browsers perhaps use a larger font size on large screens from the outset if the user does not specify otherwise? Or do we need an information campaign to make them aware that they should check their system settings or set a different default font size in the browser?
There is no obvious answer. Where the breakpoint lies — the viewport width at which 16px becomes either too small or too large — is hard to pin down, and so is the question of whether 16px is a sound default at every viewport at all. An alternative would be for user agents to apply a fluid type implementation, shipping a default font scale and a range of sizes rather than a single fixed value.



