Pages should have headers in order, with one H1 on top. Under the H1 you can have multiple H2 - H6's, but they should be nested correctly.
Good: H1 H2 H2 H3 H4 H3 H4 H2 H3 H4 Bad: H2 H1 H4 H1 H4 H3 H2 There is an accessibility aspect to this too. If the text is visually not what you want, then change it for that instance. Header tags shouldn't be used for styling. Greg -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tom Livingston Sent: Thursday, December 19, 2013 2:00 PM To: CSS Discussion Group Subject: [css-d] Visual styling vs. source order List, Hopefully this is related to CSS enough for this list... Visually, the layout I'm looking at has a smaller line of copy, I'd call it a subhead, above a larger line of copy, what I would consider the headline. Is it wrong to have an H2 before an h1, which would lend itself to the visual look as well as the importance of the lines of copy, or should they be in a h1 then h2 source order and somehow arrange them with css to match the layout. And if the latter is more correct, what's the best way to just swap their visual order? The layout is just the two lines, centered horizontally, below a nav bar. I guess this is as much a semantics question as much of a CSS question. TIA -- Tom Livingston | Senior Front End Developer | Media Logic | ph: 518.456.3015x231 | fx: 518.456.4279 | mlinc.com ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
