Sticky header may hide focused elements — WCAG 2.2 violation

WCAG 2.2 (the Web Content Accessibility Guidelines, now mandatory under the EU Accessibility Act since June 2025) requires that when a keyboard user tabs to a button or input field, that element is fully visible and not hidden behind a sticky header or footer. This site appears to have a sticky header without the scroll adjustment needed to prevent this. Keyboard users — including people who cannot use a mouse — may find that input fields or buttons disappear under your fixed navigation bar when they tab to them. This is both an accessibility barrier and a legal compliance risk in the EU. Ask your developer to add scroll-margin-top to your main content elements, set to a value equal to or greater than the height of your sticky header. This is a small CSS change that ensures focused items scroll into full view.

Why this matters

Keyboard users — including people who cannot use a mouse — may find that input fields or buttons disappear under your fixed navigation bar when they tab to them. This is both an accessibility barrier and a legal compliance risk in the EU.

How to fix it

Ask your developer to add scroll-margin-top to your main content elements, set to a value equal to or greater than the height of your sticky header. This is a small CSS change that ensures focused items scroll into full view.