Sticky header detected — verify scroll-padding-top is set in your external stylesheet
Your site has a header that stays fixed at the top of the screen as visitors scroll. The accessibility standard WCAG 2.2 requires that when a user tabs to a form field or link, that element isn't hidden behind this fixed header — but we couldn't fully verify this from the page code alone. If a focused element slides under the sticky header, keyboard-only users and screen-reader users lose track of where they are on the page — a direct accessibility failure. This is worth a quick manual check to confirm everything is visible. Ask your developer to check that a CSS property called "scroll-padding-top" is set to at least the height of your sticky header. Tab through your forms and links on a desktop browser to confirm no focused element disappears behind the header.
Why this matters
If a focused element slides under the sticky header, keyboard-only users and screen-reader users lose track of where they are on the page — a direct accessibility failure. This is worth a quick manual check to confirm everything is visible.
How to fix it
Ask your developer to check that a CSS property called "scroll-padding-top" is set to at least the height of your sticky header. Tab through your forms and links on a desktop browser to confirm no focused element disappears behind the header.