A mobile navigation link that is visually easy to read can still be physically hostile. Fingers do not tap glyphs; they tap boxes. That is the reason the 44 by 44 control standard exists, and it is also the reason a fix that only changes the apparent style is not enough. The rendered box has to be measured, because the browser is not laying out intentions. It is laying out line boxes, inline formatting contexts, font metrics and margins.
The tempting patch is familiar: add padding until the link looks comfortable. That works until it changes the rhythm of the menu, pushes the close button, creates a scroll tail on one viewport, or makes the footer inherit a rule it was never designed to carry. On a static site with no build system and copied nav/footer fragments, the risk is worse. A global rule that fixes one navigation surface can leak into every page at once.
The safer patch is not necessarily larger. In this case the target floor was expressed directly on the link box: make the link an inline-flex box, align its contents, and set the minimum block and inline size. That sounds mechanical, but the important part came afterward. The box did not become 44 pixels tall. It became larger, because the line-height already produced a taller inline-level box, so the floor never engaged on the normal labels. The fix passed because the browser had already made the target big enough, not because the declared minimum did visible work on the current text.
That distinction matters. If the team only checks the final number, it learns that the patch works. If it checks why the number appears, it learns when the patch will still work after the label changes. Short labels and smaller test fonts are the counterfactual. With the floors on, those cases clamp to the minimum target; with the floors off, they collapse. That is the evidence that the CSS is not dead weight. It is dormant safety.
The same pass also explains a previous surprise. A related footer change had shifted rhythm by a little over a pixel because the minimum size did bind there, and centering text inside the extra box moved the synthesized baseline. In the nav panel the minimum does not bind, so the baseline stays where it was and the list height remains unchanged. Same mechanism, opposite outcome. Without the measurement, both would be hand-waved as luck.
This is the practical rule: accessibility fixes are not decoration. They are layout changes whose blast radius has to be bounded. Measure the target, the neighboring rhythm, the scroll extent and the smallest viewport. Then keep the counterfactual that proves the rule has teeth. A green screenshot is not enough; screenshots are good at showing the thing you already expected to see.
The nice result is that the right one-line fix can remain one line. Rigor does not always make the patch bigger. It makes the claim smaller and stronger: this box is tappable, this rhythm did not move, this viewport did not gain scroll, and here is the mutation that proves the guard would fail without the rule.
Notes
This post is part of the recovered daily-publisher backlog after the site publication service drifted and stopped producing dated blog results. It is intentionally written as an engineering note, not as a legal, financial, or store-policy guarantee.
Keep reading: all posts on the WizusLabs Engineering blog.