Re: [whatwg] Clarify how to indicate document hierarchy

At 19:52 + UTC, on 2007-03-15, Spartanicus wrote: [...] > [...] I felt obliged to write something on the subject > myself. Part 1 is about heading usage: > http://codewallop.110mb.com/goodpractice/headingology.htm NIce. I've linked to it from

Re: [whatwg] Clarify how to indicate document hierarchy

Spartanicus <[EMAIL PROTECTED]> wrote: >I'd much rather see different authors writing their own best authoring >guidelines using their own argumentation and have these compete for >adoption amongst peers. Having said that I felt obliged to write something on the subject myself. Part 1 is about he

Re: [whatwg] Clarify how to indicate document hierarchy

Le 14 févr. 2007 à 08:12, Ian Hickson a écrit : On Mon, 12 Feb 2007, Spartanicus wrote: My preference would be to have a page on the WhatWG site that links to such authoring guidelines accompanied with a warning that they are not necessarily endorsed by the group. The spec itself could then

Re: [whatwg] Clarify how to indicate document hierarchy

On Mon, 12 Feb 2007, Spartanicus wrote: > > I'd much rather see different authors writing their own best authoring > guidelines using their own argumentation and have these compete for > adoption amongst peers. IMO some of the benefits of this are: > > * More dynamic and creative usage of the l

Re: [whatwg] Clarify how to indicate document hierarchy

Benjamin Hawkes-Lewis <[EMAIL PROTECTED]> wrote: >Of course, just because the HTML4 spec goes in for this stuff doesn't >itself mean it's a good idea. What I'd hate to see happen is that we'd end up with best authoring guidelines incorporated into the HTML 5 spec were those guidelines end up bein

Re: [whatwg] Clarify how to indicate document hierarchy

Spartanicus wrote: IMO a spec should primarily describe the building blocks, i.e. the available elements and if needed illustrate their usage with minimal context. How to use those elements to build a page or site is up to authors. It depends on variables such UA features and support, UA market s

Re: [whatwg] Clarify how to indicate document hierarchy

Sorry, Evolution cut me off. Example 3 was from: http://www.w3.org/TR/html401/struct/tables.html#h-11.2.1 Of course, just because the HTML4 spec goes in for this stuff doesn't itself mean it's a good idea. -- Benjamin Hawkes-Lewis

Re: [whatwg] Clarify how to indicate document hierarchy

Spartanicus wrote: > I see no guidance of the type you requested in the HTML4 spec. Example 1: > Since users often consult documents out of context, authors should > provide context-rich titles. Thus, instead of a title such as > "Introduction", which doesn't provide much contextual background,

Re: [whatwg] Clarify how to indicate document hierarchy

Benjamin Hawkes-Lewis <[EMAIL PROTECTED]> wrote: >> IIRC no current AT AU facilitates navigating for example from one to the >> next , they only allow navigating to the next or previous header. > >Even being able to skip from heading to heading is vast improvement, but >I'm delighted to say you'r

Re: [whatwg] Clarify how to indicate document hierarchy

Spartanicus wrote: > You need to input something and post the result for that to work. This is true. :) Let's try that again... SimpleBits quiz: http://tinyurl.com/237rgp and SimpleBits quiz conclusion: http://tinyurl.com/3clao2 > IIRC no current AT AU facilitates navigating for example from o

Re: [whatwg] Clarify how to indicate document hierarchy

On Mon, 12 Feb 2007 11:17:32 +0100, Spartanicus <[EMAIL PROTECTED]> wrote: WHATWG's specifications should establish clear guidelines about how document hierarchy can be indicated. Should a specification also be an authoring course? I think it's appropriate for HTML5 to define how authors sho

Re: [whatwg] Clarify how to indicate document hierarchy

Benjamin Hawkes-Lewis <[EMAIL PROTECTED]> wrote: >SimpleBits quiz: http://tinyurl.com/create.php You need to input something and post the result for that to work. >After text fallbacks, heading elements are arguably the single most >important accessibility feature HTML offers. They allow assist

[whatwg] Clarify how to indicate document hierarchy

Some web documents are standalone, but many if not most belong to a hierarchy of documents. There has long been confusion about the correct way to indicate the document hierarchy from within a given document. How should elements be written? How should site logos be marked up? Should elements be