The spec says:
> People should use this role for static tables of contents. This  
> includes tables of contents built with lists, including nested  
> lists. Dynamic tables of contents, however, would be a tree.

but then goes on to inherit states and properties for live regions.

Also, directory requires link as child elements. Suppose a document  
has a table of contents made of nested <ol> or <ul> lists. In that  
case, HTML doesn't provide the native table of contents semantic  
(perhaps it should?). However, HTML does provide the link semantic  
natively. Moreover, the links will be descendants but not children.

Therefore, requiring a role=link child seems excessive.

Henri Sivonen

Received on Wednesday, 26 March 2008 16:53:43 UTC