- From: David Woolley <david@djwhome.demon.co.uk>
- Date: Fri, 2 Sep 2005 23:16:24 +0100 (BST)
- To: www-html@w3.org
> One of the main motivations for @role came from work by various > accessibility experts. The idea was to be able to tell some processor more > about what some part of a document was there for. Although initially That's the purpose of markup, or at least that is the SGML concept of markup. That you need an overlay on the markup is basically the consequence of HTML being treated more like presentation language. As I've said before, I think that the real way of doing this is to separate out navigation and use link elements to find it, but that would require more semantic browsers, when people have learned to use browsers to reproduce physical appearence. > intended to help voice systems to provide a better experience for users, it > element (a <p> or <section> for example), or it might be in some element > from another language that has been embedded into XHTML 2, such as an SVG You have that problem when it isn't XML already, and that wasn't a problem for the original HTML concept because the resource, whether HTML or not, would have been separate from the navigation.
Received on Friday, 2 September 2005 22:28:16 UTC