E-mail List Archives
Re: Multiple H1 tags in an HTML5 web page
From: Jared Smith
Date: Mar 10, 2014 12:17PM
- Next message: Elizabeth J. Pyatt: "Re: Can Word and Adobe ACrobat on a Mac make accessible/tagged PDF files?"
- Previous message: Bourne, Sarah (ITD): "CSUN costs and justifications"
- Next message in Thread: Greg Gamble: "Re: Multiple H1 tags in an HTML5 web page"
- Previous message in Thread: Greg Gamble: "Re: Multiple H1 tags in an HTML5 web page"
- View all messages in this Thread
Greg Gamble wrote:
> Those answers tell me that the use of multiple H1's is the way to go.
That's not how I would interpret the survey response. The survey asked
about having the site name/logo and the document title both be <h1>s.
Just 1/2 of respondents thought this optimal. This is quite different
from your scenario where each section has its own H1.
What you presented would be acceptable in HTML5, and would present an
appropriate outline if the outlining mechanism were implemented. But
because it's not, your heading structure is not optimal for most
documents. It's not "inaccessible", but most users expect one first
level heading for a document and sub-headings representing each
sub-section. Having <h1>s for each section could cause confusion.
Jared
- Next message: Elizabeth J. Pyatt: "Re: Can Word and Adobe ACrobat on a Mac make accessible/tagged PDF files?"
- Previous message: Bourne, Sarah (ITD): "CSUN costs and justifications"
- Next message in Thread: Greg Gamble: "Re: Multiple H1 tags in an HTML5 web page"
- Previous message in Thread: Greg Gamble: "Re: Multiple H1 tags in an HTML5 web page"
- View all messages in this Thread