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

Page Contents after H1 in DOM #92

Open
shawna-slh opened this issue Mar 18, 2022 · 1 comment
Open

Page Contents after H1 in DOM #92

shawna-slh opened this issue Mar 18, 2022 · 1 comment

Comments

@shawna-slh
Copy link
Contributor

shawna-slh commented Mar 18, 2022

Currently it's before h1. Consider if we want it after the h1. Semantically it makes sense after the h1. However, screen reader users don't really need it, so maybe leave it before the h1 so Skip to content bypasses it?

@shawna-slh shawna-slh added this to the Phase 2 (or later) milestone Mar 18, 2022
@mcking65
Copy link

mcking65 commented May 2, 2022

Please leave the page contents outside of the main content. It is in the side bar for people who can see, and it should be in the sidebar (out of the way) for people who cannot see.

The ideal reading order and attention management for people who use a screen reader is basically the same as it is for anyone else. Make the title of the page the most obvious heading (make it an H1). Make the content that goes with that title the most prominent feature of the page, i.e., it immediately follows the H1 in the reading order.

That is, the ideal reading order for page title and main content for most types of pages is:

<main>
  <H1>Page Title</h1>
<p>Hellow world! this is the wonderful content you are dying to read. So, enjoy without delay.</p>
</main>

If you are going to have a TOC for the page, it should be before or after the main element. Before is probably better in most circumstances; visual positioning and logical tab sequence are also factors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants