-
Notifications
You must be signed in to change notification settings - Fork 3
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
where in H1 for standalone-resource__type-of-guidance ? #99
Comments
@shawna-slh Which element are you asking about? Is it the link that follows the H1?
If so, I wonder why that link is present at all. It feels like a distraction to me. There is a breadcrumb that tells the user exactly where they are. It would be extremely helpful to screen reader users if the breadcrumb were immediately before the main content in the reading order. Visually, I hope it is near by. Breadcrumbs are awesome for providing a strong sense of where the user is in the site. The fact that the breadcrumb is essentially describing the location of the main content is made much more clear when it is the element just before the main content. The reading order I think would be most beneficial is:
|
I don't see the breadcrumb. That is, I have “banner blindness” to it. Enough that I was about to say the other day that the WAI site doesn’t have breadcrumbs… even though I helped design it and use it many times a day! For some resources, it’s pretty important to know that this is a sub-page of. For example, we have a page on Images in the tutorials, a page on Images in the Developer Curricula, a page on Images in the Content Author Curricula. Curricula does have it in the h1:
|
Thanks for the input! I linked to that from the overall structure and semantics issue: w3c/wai-website#295 The breadcrumb is related to site navigation. The Page Contents list is specific to that page content. So it seems to that the Page Contents should be with the main content? Anyway, we don't have resources to address it today. Hopefully soon! |
Probably we should move it to after the main h1, so the H1 is front loaded and easier for screen readers to skip the repetitive info if they are using the resource a lot.
/me looks at design pattern elsewhere on the WAI site, e.g., https://www.w3.org/WAI/media/av/planning/
hummm, there it's not even in the h1...
The text was updated successfully, but these errors were encountered: