Accessibility checking

Rocket Validator looks for accesibility violations on your pages using the axe-core accessibility engine, hosted on our own servers and integrated into our web crawler. You don't need to buy an additional license, everything's already included in your Pro account at Rocket Validator.

WCAG: Best Practice: Page must not have more than one banner landmark

Ensures the page has at most one banner landmark.

Landmarks allow blind users to navigate and find content quickly. Missing landmarks require screen reader users to sort through too much extra information to find anything.

JAWS, NVDA, and VoiceOver support the ability to navigate to sections of a web page using ARIA landmarks. Landmarks provide a more elegant solution to the problem of providing a way for users to skip to the main content of the web page. There is no visible alteration to the web design, making it unobtrusive and invisible. Of course, the fact that this technique is invisible is fine for blind screen reader users, but not so fine for sighted keyboard users or screen enlarger users with low vision. In this sense, HTML 5 regions and ARIA landmarks cannot yet replace the old-fashioned "skip navigation" links. Browsers still do not have a built-in way to notify users that HTML 5 regions or ARIA landmarks are present. Screen reader users are the only ones who can take advantage of them. There is a Firefox ARIA landmark extension available, which adds the ability to navigate by landmarks in Firefox, but this is not a native feature of the browser.

Learn more about this accessibility rule at Deque University >>

Validate accessibility and HTML5 on large sites, starting at $24/week. Start here