JAWS and our inline edit - what does it do when activated?

[Allison Bloodworth]

Hey guys,

I've done a lot of work on the Inline Edit pattern and I think it's  
close to ready to go. Our working strategy right now is to not use too  
much technical (e.g. which HTML tags to use) information in most of  
the pattern, but it seems that is very helpful information to include  
in the Accessibility Considerations section. However, as I'm trying to  
write this section I'm realizing I really don't have enough  
information to do it properly. I'm thinking it might be better have  
someone with technical knowledge of the Inline Edit component at least  
start writing it, and then I can edit it.

I am trying to write all the patterns in a non-prescriptive fashion,  
so I don't think we should tell people they must implement inline edit  
in exactly the same way we did, but I like to include information on  
how we did it as a potential solution (hopefully reading the rest of  
the pattern gives examples of this). So for instance, in addition to  
the questions we asked Justin below, I need to know whether we  
implemented text that can be inline edited as an HTML button, as that  
may be something we'd like to suggest as a possible solution.

Who do you think would make most sense to help out with this?

Cheers,
Allison

On Mar 24, 2009, at 10:21 AM, Allison Bloodworth wrote:

> Thanks so much for checking into this Justin. Yes, this covers what  
> we are looking for. I'm trying to re-write the Accessibility  
> Considerations portion of the Inline Edit Design pattern to be  
> somewhat specific in terms of what markup *could* be used ( I won't  
> say you have to use it -- it is a pattern and not a prescription  
> after all ) and I'd like to be able to talk about what we've done as  
> an example. As Jonathan points out, this is also a good time to make  
> sure we've addressed all these accessibility considerations in the  
> component too.
>
> Cheers,
> Allison
>
> On Mar 24, 2009, at 10:16 AM, Justin wrote:
>
>> Hi Jonathan,
>>
>> I'll have to double check it. We talked a bit about it with  
>> Everett, not sure if it was on list or in person. It would have  
>> been some time in December.
>>
>> I'm pretty sure the field announces itself as a button when it is  
>> reached, can't remember what it says on save though.
>>
>> - Justin
>>
>> On 24-Mar-09, at 12:43 PM, Jonathan Hung <jhung.utoronto at gmail.com>  
>> wrote:
>>
>>> Hi Justin,
>>>
>>> Can you tell me what JAWS says / does after you have activated an  
>>> inline edit field? What we are trying to determine is if a user  
>>> who is using a screen reader is receiving sufficient feedback  
>>> informing them that they are now in "edit mode". If not, we should  
>>> figure out what the best practice should be and include it in the  
>>> design pattern.
>>>
>>> Interestingly enough, how would we instruct a screen reader user  
>>> on how to save their edits? We need to somehow tell them that  
>>> hitting Tab / Enter key would save.
>>>
>>> Allison, does that cover what we're trying to figure out?
>>>
>>> - Jonathan.
>>>
>>>
>>> ---
>>> Jonathan Hung / jhung.utoronto at gmail.com
>>> Fluid Project - ATRC at University of Toronto
>>> Tel: (416) 946-3002
>
> Allison Bloodworth
> Senior User Interaction Designer
> Educational Technology Services
> University of California, Berkeley
> (415) 377-8243
> abloodworth at berkeley.edu
>
>
>
>

Allison Bloodworth
Senior User Interaction Designer
Educational Technology Services
University of California, Berkeley
(415) 377-8243
abloodworth at berkeley.edu




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090325/f59f482a/attachment.html>