Accessibility: Best Practice – Banner Landmark Must Not Be In Another Landmark

For each element on the page that uses the role=”banner” ARIA landmark, ensure that it is not contained within another ARIA landmark.

HMTL5 specification allows multiple instances of an equivalent header landmark value, however it is appropriate in most web designs to have only one banner landmark whether it is specified using ARIA or HTML5 and that they are not nested within other landmarks.

How to Analyse in the SEO Spider

To populate this filter ‘Accessibility’ must be enabled via ‘Config > Spider > Extraction’ and ‘JavaScript rendering’ mode via ‘Config > Spider > Rendering’.

View URLs with this issue in the ‘Accessibility’ tab and ‘Banner Landmark Must Not Be In Another Landmark’ filter.

Use the lower ‘Accessibility Details’ tab to click on the issue on the left-hand side, and see details of the location on the page of the violation on the right-hand side.

Bulk export the pages and details of the accessibility violations via ‘Bulk Export > Accessibility > All Violations’.

What Triggers This Issue

Please view the Deque University website further reading link below for ruleset triggers.

How To Fix

Ensure the banner landmark is at top level.