According to DEV Community, a scroll-snap layout can snap to the right section and still look broken when the section heading ends up hidden under a fixed header. The snap rule is usually not the problem. The scrolling container simply does not know that part of its visible area is taken up by a header that stays in place.
The fix the article describes is to set scroll-padding-top on the scroll container, using the height of the fixed header. This changes the area the browser treats as the usable viewing region, known as the snapport. When a section snaps to the start, the browser then lines it up with the edge below the header. Each section can keep its existing scroll-snap-align: start, and the container can keep mandatory vertical snapping.
The article argues that this separation is the point. Child alignment says where a target aligns. Scroll padding says what part of the container is usable for viewing. Adding spacing to every section may seem to work, but it changes the geometry of the content and repeats a container-level concern in every target. When one header is shared by all targets, the article says the scroller should own the offset.
For testing, the article suggests checking geometry, not just a scroll position. After snapping, the top edge of the heading should sit at or below the bottom edge of the header. The original snap type and child alignment should also still be in place.
The article also notes limits. The first target starts at scroll position zero, so top padding cannot create extra scroll space above it, and it may still sit under the fixed header. If targets need different offsets, child-level scroll-margin is the better tool. If a design needs arbitrary, pixel-perfect positioning instead of moving between snap targets, the article says to reconsider whether scroll snap suits it.
Why it matters
Fixed headers and full-page snapping sections are common on landing pages and product tours. A heading hidden under the header is easy to miss in casual testing, yet visitors notice it straight away. It can make a polished page feel faulty.
Putting the offset in one place also keeps the stylesheet simpler. If the header height changes later, there is one value to update rather than a spacing rule in every section. The article's edge cases are a useful reminder to check the first section by hand.
Source: DEV Community. This brief summarises their reporting; read the original for the full detail.