Fwd: aria-transforms?

Meant to reply to the discussion list.


Begin forwarded message:

> From: James Craig <jcraig@apple.com>
> Date: December 20, 2008 8:39:56 AM PST
> To: David Bolter <david.bolter@utoronto.ca>
> Subject: Re: aria-transforms?
>

> In your example below, there isn't a reason for the role change. It  
> can just be a textbox whose style (and perhaps its aria-readonly  
> property) changes when it is focused or clicked, no? I don't think  
> there is a need for it to be a button prior to that event.
>
> Do you have any examples where there may need to be a functional  
> change rather than just a stylistic one? If it's just appearance  
> changes you're after, I'd say leave that to CSS, perhaps even to the  
> new CSS transition proposal.
>
> Example:
>
> [role="textbox"] {
>  border-color: #fff;
>  border-color: rgba(0,0,0,0);
>  transition: border-color 1s liner;
>  /* currently needs -moz or -webkit prefix */
> }
> [role="textbox"][aria-readonly="false"] {
>  border-color: #000;
>  border-color: rgba(0,0,0,1);
> }
>
>
>
> On Dec 20, 2008, at 7:26 AM, David Bolter <david.bolter@utoronto.ca>  
> wrote:
>
>>
>> Hi all,
>>
>> This might be an ARIA 2.0 thing.
>>
>> I'm just throwing this out there. Maybe it is my Saturday morning  
>> coffee
>> talking but I got to thinking about DHTML inline edits, and I started
>> thinking of ways we might come up with a more general solution for
>> things that appear to transform themselves.
>>
>> aria-transforms=[aria role(s)]
>>
>> So in the case of an inline edit, one could mark the span like this:
>>
>> <span role="button" aria-transforms="textbox">change this text</span>
>>
>> Thoughts?  Is it the coffee?  I was also thinking about an
>> aria-hastextbox, akin to a haspopup, but that is a less general  
>> solution
>> IMO.
>>
>> cheers,
>> David
>>