Open leahbannon opened 10 years ago
Note: re: heading priorities, I believe the latest HTML5 standards have moved to one h1 per section (ie, this is the most important heading in this section rather than this page), and now you rarely see anything below h1 (doesn't come up much). What I don't know: Is the one-h1-per-section still correct for accessibility stuff, or have accessibility tools not caught up with the latest HTML5 web standard stuff?
I couldn't find any information beyond the usual 'h1' for page title and h2 for section headings in terms of accessibility. It's probably fine to use h1 tags as section headings as long as an h1 tag isn't used under a lower priority tag (h2, h3 etc) and all visual headings are marked as headings.
Sounds reasonable. We can go with that :)
9.2A- The FBOpen text at the top of the screen appears to be the header for the site, but it is not tagged as such. It should be marked with an
<h1>
tag as it is the highest priority for the page. h1 should be used for the page name, h2 should be used for section headings, side nav, main content, etc, and h3 for headings in each of those sections, and down the line as needed. Heading tags are the most commonly used element for navigating around a page quickly for screen reader users. They use them to jump to appropriate sections and to find what they are looking for.