>For example, you can click on a paragraph, an un-ordered list or an >image in the 'content view' but I cannot find any ARIA Roles that cover >their 'role' within the UI. They generate events, they 'trigger' actions >and they should be navigable, but they are not buttons in the >traditional sense of the word. You need to explain a little more what happens when you click or what is the behavior when you click to us, more than they generate events or trigger actions - most all UI widget do that. For example, if clicking on the paragraph generate an event that updates the contents in another panel - such as a table on contents link take you to the corresponding page, then it seems to me to behave like a simple link - so code it as a link. If you have invented a new UI widget, then that would require extending the ARIA roles in my opinion. If you were doing this "thing" in a Windows desktop app, what would it be? Regards, Phill Jenkins IBM Research - Human Ability & Accessibility Center http://www.ibm.com/ableReceived on Monday, 10 March 2008 15:40:19 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 10 March 2008 15:40:20 GMT