You're still not understanding a word I'm saying -- you seem to keep thinking I'm talking about headings for the display:none, when I'm talking about a accesskeys/.skipto/.jumpto menu, which has ABSOLUTELY NOTHING TO DO WITH HEADINGS/HEADERS other than their being what screen readers use INSTEAD...
Ok, for example, code from 99% of what I've been writing the past two years
See how ol.jumpto links to the id's that are pretty much "next to" the start headings for a section anyways? .jumpto is the type of hidden accessibility menu being talked about here, which is NOT for screen readers. I don't mind them being hidden on screen readers BECAUSE I have proper heading tags in a logical order in the document.
title="Top of Page"
>Top of Page</a>
title="Bottom of Page"
>Bottom of Page</a>
<li class="home"><a href="/" class="current">Home</a></li>
<li class="news"><a href="/news">News</a></li>
<li class="links"><a href="/links">Links</a></li>
<h3>News Item Title</h3>
<p>Some news item</p>
<!-- .subSection --></div>
<!-- news items repeat ad-nasueum -->
<!-- #content --></div>
<p>Couple things you want to feature here</p>
<p>Quick about blurb here</p>
<!-- #sideBar --></div>
Usual disclaimer garbage text nobody actually reads
<!-- #footer --></div>
<!-- #pageWrapper --></div>
That's all I'm saying here. .jumpto/.skipto accessibility menus are for IN PAGE LINKS -- like to ID's or NAMES.
horizontal rules in my code are for non-screen/tv/projection users
.jumpto menu is for accesskeys and CSS off users on small screen
like blazer, or for small display like Opera Mobile and Mini's
"small screen" mode.
Which I think is where you got confused on the ID part. You do know href="#content" or href="#footer" will point at id="content" and id="footer" respectively, right?
Or are you still doing the 1997 style empty anchor nonsense for that? (Which there's ZERO reason to do once we stopped caring about Nyetscape 4)