Aria-practices: Landmarks section should include advice that all content should be in a landmark.

[jnurthen]

Migrating old tracker issues
https://www.w3.org/WAI/ARIA/track/issues/505

[carmacleod]

All perceivable content. Wrapper divs and hidden things don't count. :)

[jnurthen]

Also Skip to main content link need not be in a landmark - as if you are using landmarks to navigate there is no need to have it.

[ZoeBijl]

Skip links should also be in a landmark. Usually the closest is the header element.

---

@carmacleod wrote:
All _perceivable_ content. Wrapper divs and hidden things don't count. :)

All content is perceivable no? A wrapper-div wouldn’t count as it itself isn’t content. I would think it’s fine to leave out some hidden things such as <script>-tags.

[jnurthen]

Skip links should also be in a landmark. Usually the closest is the header element.

@MichielBijl Why? Who does this help? If someone is navigating by landmarks they can already do the functionality provided by the skip link. If someone is not navigating by landmarks then it doesn't matter if they are in a landmark or not.
Am I missing a use case where having a skip link within a landmark actually makes the page better for anybody?

[ZoeBijl]

@jnurthen, I would like to invite @stevefaulkner to the conversation. This is something I learned from him.

That said, there’s some text in our own document that tells us the same thing:

Including all content on a page in one of its landmark regions and giving each landmark region a semantically meaningful role is one of the most effective ways of ensuring assistive technology users will not overlook information that is relevant to their needs.