My question isn't about how to nest headings properly
E823 - 1 instance(s): Heading elements must be ordered properly. For
example, in HTML H2 elements should follow H1 elements, H3 elements
should follow H2 elements, etc. Developers should not skip levels
(e.g., H1 directly to H3). Do not use headings to create font
effects. See
http://www.w3.org/TR/WCAG10-HTML-TECHS/#document-headers (displayed
in new window).
I am curious how much benefit it goes to accessibility. What ill
effect it has on assistive user agents if headings are not nested
properly.
Semantically, I fully understand the need for proper order of
heading elements, but in real world practice, I have yet noticing
any site that follow this to the letter, and it's more than a
challenge for a complicated columned layout that designer tends to
use h3 for every bold text title.
Hi Tee,
At the University of Illinois, we use a tool called the Functional
Accessibility Evaluator (FAE - http://fae.cita.uiuc.edu) that checks
for proper header nesting. My understanding is that misuse or
improperly nested headings will be confusing to screen reader users
when they may be lead to thinking they missed a section head or
something.
I agree this issue can become a real challenge in terms of source order.
-Tim
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
