> 
> For example, an article could have a header and footer:
> 
>       <section>
>               <article>
>                       <header>
>                               <h2>Article title</h2>
>                               <p>August 12, 2010</p>
>                       </header>
>                       <p> Article copy here. Article copy here. Article
> copy here. Article copy here.</p>
>                       <footer>
>                               <p>By: Dan Freeman</p>
>                       </footer>
>               </article>
>       </section>
> 
> Using ID's would not help you replicate this.  You'd have to structure it
> like this:
> 
>       <div class="section">
>               <div class="article">
>                       <div class="header">
>                               <h2>Article title</h2>
>                               <p>August 12, 2010</p>
>                       </div>
>                       <p> Article copy here. Article copy here. Article
> copy here. Article copy here.</p>
>                       <div class="footer">
>                               <p>By: Dan Freeman</p>
>                       </div>
>               </div>
>       </div>
> 
This example doesn't look very semantic to me :-) Is there a tag that can 
replace or substitute the use of headings?

I am curious if and how HTML5 section and header tags could help solve the 
Section Headings (SC 2.4.10) in WCAG 2.0 and WCAG 1.0 Checkpoint 3.5. 

I had issue with WCAG 1.0 Checkpoint 3.5, thought it was just a rather 
impractical guideline for that a web page can be in many forms not just a page 
of content consists of navigations, block of callout content that must go after 
the main content (which is usually where H1 located). A page could have only 
one H1 and that semantically it must be the first heading in a document, this 
makes the SC 2.4.10 in impractical.

I thought WCAG 2.0 would change it, and show warning instead of error if a page 
has no proper nested headings, it didn't so I thought perhaps HTML5 tags could 
help solve the SC 2.4.10 that very few sites able to comply. Not even these two 
quality sites that advocate, preach the accessibility.

http://webaim.org
http://www.w3.org/WAI/

tee

*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************

Reply via email to