Nested Headings (1.3.1, 2.4.10 or neither)

Hi all

We've been having an interesting discussion as to whether the use of incorrectly nested headings is a failure of 1.3.1, 2.4.10 , both or neither.

In 1.3.1. we can see that in order to programmatically determine the relationship between a heading and the content that it should be programmatically-associated, such as using html heading tags (H1-6) and one of the techniques is H42, Using H1-h6 to identify headings.

Technique G141: organizing a page using headings is another techniques and it says that "authors should use headings that are properly nested...".

I can't see anywhere if it is actually a failure to have headings incorrectly nested, or whether it is more a case of not using 'best practice'.

2.4.10 also relates to section headings and shows the only sufficient technique (listed) as G141 again.

To settle this debate, would you consider it a failure if headings (coded as H1-6) were used to show sections of content, but were not correctly nested?



Regards

Vivienne L. Conway, B.IT(Hons), MACS CT, AALIA(CS)
PhD Candidate & Sessional Lecturer, Edith Cowan University, Perth, W.A.
Director, Web Key IT Pty Ltd.
v.conway@ecu.edu.au<mailto:v.conway@ecu.edu.au>
v.conway@webkeyit.com<mailto:v.conway@webkeyit.com>
Mob: 0415 383 673

This email is confidential and intended only for the use of the individual or entity named above. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify me immediately by return email or telephone and destroy the original message.

________________________________
This e-mail is confidential. If you are not the intended recipient you must not disclose or use the information contained within. If you have received it in error please return it to the sender via reply e-mail and delete any record of it from your system. The information contained within is not the opinion of Edith Cowan University in general and the University accepts no liability for the accuracy of the information provided.

CRICOS IPC 00279B