Sue - I can completely understand why you might think that things might need to be nested as a child of the Hx tag, but hopefully this might help to provide extra clarity from a new perspective. I like to think of the tree like boxes. Everything goes inside the Document box. Then, if for organizational sanity, I want to have articles, sections or parts, I can put those inside the Document box. Let's say I decided I have a document and I decide to use sections to divide my content. Then inside the section I will have things like headings, paragraphs, figures lists forms and links all ordered neatly in the order I want them to be read and each containing the text I want them to read. I would never open the box for headings and put my form in it because it already if filled with the heading text. Nor would I put a heading INSIDE my paragraph. It would be "in front" of, or "on top" of the paragraph. When you can think of it that way, it makes a lot more logical sense. In addition to reading in a linear fashion, it is common for blind people to jump to specific content to navigate a document. With JAWS you can pull up the "list of lists" (ins+F3) and then pull up all sorts of things like the headings in a document. As a matter of fact, blind people use this so much that JAWS has build in default shortcuts for Headings lists (ins+F6), Form Lists (ins+F5), Link Lists (ins+F7). Tags are the structure in which non-sighted people navigate multi-part documents on a regular basis and that is why it is so key that we use the tag structure in a way that gives them the most flexibility in digesting what is on the page. Giving them multiple ways to access the content answers the "Robust" in the P.O.U.R. principals of accessibility. Hopefully that helps in addition to Bevi's (always insightful) comments. -Dax
... View more