Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

audit-avt1-homepage: content not within landmark #943

Closed
andreancardona opened this issue Jul 26, 2020 · 0 comments · Fixed by #944
Closed

audit-avt1-homepage: content not within landmark #943

andreancardona opened this issue Jul 26, 2020 · 0 comments · Fixed by #944
Assignees

Comments

@andreancardona
Copy link
Contributor

andreancardona commented Jul 26, 2020

Environment:

Operating system: Mac
Browser: Chrome
AVT 1️⃣
Page: Homepage

Detailed Description:

  • Content is not within a landmark element
  • Affects 21 total errors produced
    • If this issue needs to be broken up into other issues please do so and reference this issue in docs.

What to do:

  • Enclose the content within an HTML5 sectioning element with an implicit landmark role (e.g. Content);
  • OR use the "role" attribute on an enclosing element to specify an appropriate WAI-ARIA landmark value (e.g. <div role="contentinfo">...</div>).

Why is this important?

Landmark roles provide programmatic access to sections of a web page, making it easy for the user to understand the structure of the page and easily navigate to different sections. They also enable users to skip over blocks of content that are repeated on multiple pages.

@andreancardona andreancardona self-assigned this Jul 26, 2020
@andreancardona andreancardona changed the title fix: (audit-avt1-homepage) - more than one banner role audit-avt1-homepage: more than one banner role Jul 26, 2020
@andreancardona andreancardona changed the title audit-avt1-homepage: more than one banner role audit-avt1-homepage: content not within landmark Jul 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant