Skip links trigger "content not in landmark" violation

Feature Requests / Improvements
1

Small accessibility request regarding the default skip links.

They’re currently output directly inside <body> with no landmark wrapper, which triggers the “Content is not within a landmark element” violation in axe-core, WAVE, and Lighthouse audits.

The standard fix is to wrap them in a labelled nav:

<nav aria-label="Skip links">
  <a class="skip-link" href="#brx-content">Skip to main content</a>
  <a class="skip-link" href="#brx-footer">Skip to footer</a>
</nav>

Could this be adjusted in core, or alternatively could a filter like bricks/skip_links/html be exposed so we can customise the output? Currently there’s no clean way to wrap them without output buffering the whole wp_body_open hook.

Thanks

2

That is not correct as it is not a violation. Based off the requirements from WebAIM it is setup correctly in Bricks.