Hi Henri, Could you clarify the 'banning' of the document role. An example use for it in HTML would be to indicate to AT that a section of an application is to be interpreted as a html document. For example, in a mail application, the section of the application that acts as a container to read and edit messages is marked up as role="document", this triggers the AT to change mode from application to document reading. Example: <body role="application"> <menu> <div role="document"> Message text </div> </body> Also in cases where the purpose of the page is to be an application why is it not possible to mark up the body element with a role of application? When the alternative involves adding extra markup. <body> <div role="application"> <menu> <div role="document"> Message text </div> </div> </body> Btw It would be good if you could modify the status of 'input type=image' as discussed previously. with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.htmlReceived on Tuesday, 23 September 2008 08:36:06 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 September 2008 08:36:06 GMT