RE: Which ARIA Roles do you use to mark-up clickable regions within a content view?

Phill wrote:

> You need to explain a little more what happens when you
> click or what is the behavior when you click


I did indicate in the previous e-mail that:

>> There are regions within the 'content view' that, 
>> when clicked, reveal (using embedded XForms actions) 
>> dialog boxes that allow data related to those view 
>> components to be updated.

When I click on the region within the view, a dialog box is revealed.
Therefore, it's behaviour is to make a change to the UI by exposes a
part of the UI that was not previously visible. It will indirectly cause
content to be updated as the XForms processor will get values for the
controls within that dialog. So, I guess you could look at it as a link,
but it seems to me to be a rather tenuous link (no pun intended).


 

Regards

Philip Fennell
>XSLT Developer (Content Management Culture)
>
>BBC Future Media & Technology
>Media Village, 201 Wood Lane London W12 7TP
>BC4 C4, Broadcast Centre
>
>T:     0208 0085318
>


 

________________________________

From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On
Behalf Of Phill Jenkins
Sent: 10 March 2008 15:40
To: w3c-wai-ig@w3.org
Subject: Re: Which ARIA Roles do you use to mark-up clickable regions
within a content view?



>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/able



http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

Received on Monday, 10 March 2008 15:58:24 UTC