Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

Handle complexities for footer/contentinfo landmark #6

Open
1 task
MelSumner opened this issue May 25, 2017 · 2 comments
Open
1 task

Handle complexities for footer/contentinfo landmark #6

MelSumner opened this issue May 25, 2017 · 2 comments
Labels
help wanted

Comments

@MelSumner
Copy link
Member

MelSumner commented May 25, 2017 •
edited
Loading

The HTML5 footer element is not considered a contentinfo landmark when it is descendant of any of following elements:

  • article

  • aside

  • main

  • nav

  • section

  • To make this better for Ember applications, we should ensure that the contentinfo landmark is used appropriately. There may be some conversation/thought needed around how opinionated this addon wants to be regarding footer HTML element use.
@jenweber
Copy link
Contributor

It seems that there are similar rules for banners https://www.w3.org/TR/wai-aria-practices/examples/landmarks/banner.html

@MelSumner
Copy link
Member Author

@jenweber yes, you're correct. I might have it do some checking about what the parent element is and leave it at that.

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MelSumner @jenweber