On 19 Aug 2010, at 11:51, Rob Crowther wrote:
Patrick H. Lauke wrote:
On 19/08/2010 10:13, David Storey wrote:
So the section or article elements could be taken out of context
and
displayed elsewhere but retain their <h1> headings.
You could, but I still use the h1 to h2 inside the sections
because no
browser uses the sectioning algorithm for thing like styling.
I think Firefox 4.0 will, this will also be the first version of
Firefox to have the HTML5 parser enabled by default. Styling is
especially fun because it's not just sections you have to worry
about, several other elements also create a new sectioning context.
Life will be made easier by the new any() selector:
maybe, but any is not backwards compatible so not really an option to
use any time soon, and is (AFAICT) a Mozilla only extension that is
not in any specification. As it isn't even in any spec, even if it
does get accepted by the CSS working group, it will take ages to be
specced up, refined and included in the other browsers.
This is why I just stick to using the appropriate h* element for the
section level that stick to h1, as it is more backwards compatible and
solves all the head scratching.
/* Level 0 */
h1 {
font-size: 30px;
}
/* Level 1 */
:-moz-any(section, article, aside, nav) h1 {
font-size: 25px;
}
/* Level 2 */
:-moz-any(section, article, aside, nav)
:-moz-any(section, article, aside, nav) h1 {
font-size: 20px;
}
/* Level 3 */
:-moz-any(section, article, aside, nav)
:-moz-any(section, article, aside, nav)
:-moz-any(section, article, aside, nav) h1 {
font-size: 15px;
}
https://developer.mozilla.org/en/CSS/:-moz-any
Also worth pointing out that, to my knowledge, no AT/screen reader
currently supports it either, so this may cause some issues for
these users at present.
Similarly the native semantics of elements like header and nav don't
yet have any impact on screen readers which support the similar ARIA
roles (unless NVDA added support?) so you should add them even when
there's duplication:
http://www.w3.org/TR/html5/content-models.html#annotations-for-assistive-technology-products-aria
Rob
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************
David Storey
Chief Web Opener / Product Manager, Opera Dragonfly
W3C WG: Mobile Web Best Practices / SVG Interest Group
Opera Software ASA, Oslo, Norway
Mobile: +47 94 22 02 32 / E-Mail/XMPP: dsto...@opera.com / Twitter:
dstorey
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************
