Inline Edit Solution for FLUID-2652

[Justin Obara]

Hi Everett,

I understand what you mean about being too familiar with the solution, but thanks for your thoughts. We'll be sure to put any user testing info up on the wiki and/or mention it on list. 

Thanks
Justin

On 2010-10-18, at 9:32 AM, E.J. Zufelt wrote:

> Hi justin,
> 
> Since I am highly familiar with the slution I can't test it with any degree of credibility.  I would love to hear about any usability testing should some be conducted in the future.  I believe that this interaction will be more easily understood than the prior one, but only real users will show this to be true or false.
> 
> Thanks,
> Everett Zufelt
> Accessibility Consultant & Web Developer
> 
> Web
> http://zufelt.ca
> Phone (toll free U.S. & Canada)
> 1-877-ZUFELT-8 (1-877-983-3588)
> 
> Follow me on Twitter
> http://twitter.com/ezufelt
> View my LinkedIn Profile
> http://www.linkedin.com/in/ezufelt
> 
> 
> 
> On 2010-10-18, at 9:09 AM, Justin Obara wrote:
> 
>> Hi Everett, 
>> 
>> I do not believe that we've had a chance to do any actual user testing with this latest solution yet; although the designers  may have plans for it. If you have a chance to try it out we'd love the feedback. 
>> 
>> Thanks
>> Justin
>> 
>> On 2010-10-17, at 8:01 PM, E.J. Zufelt wrote:
>> 
>>> Curious if anyone has been able to do any usability testing with real users to see if this is indeed a better solution than what we had before?
>>> 
>>> 
>>> Everett Zufelt
>>> Accessibility Consultant & Web Developer
>>> 
>>> Web
>>> http://zufelt.ca
>>> Phone (toll free U.S. & Canada)
>>> 1-877-ZUFELT-8 (1-877-983-3588)
>>> 
>>> Follow me on Twitter
>>> http://twitter.com/ezufelt
>>> View my LinkedIn Profile
>>> http://www.linkedin.com/in/ezufelt
>>> 
>>> 
>>> 
>>> On 2010-10-17, at 7:56 PM, Lam, Mike wrote:
>>> 
>>>> Hi everyone,
>>>> 
>>>> We've made a number of changes to address the Inline Edit screen reader accessibility issue initially filed in FLUID-2652.   
>>>> 
>>>> Here is a summary of the changes that we've made:
>>>> -  Implemented an explicit save button at the end of the container.  
>>>> -  Added a tooltip to both the save button and edit field in display mode.
>>>> -  Added a tooltip on the edit field only upon edit mode via mouse or keyboard.
>>>> -  Removed the edit field from the tab order.   The tab order inclusion can give visual users the impression that the inline edit is not working with the keyboard as two tabs are required to remove focus from the component.
>>>> -  Unit tests to verify our additions and modifications.
>>>> 
>>>> Feedback is always welcome!
>>>> 
>>>> Mike.
>>>> 
>>>> ---
>>>> Mike Lam / mlam at ocad.ca
>>>> Inclusive Software Developer and Designer
>>>> Inclusive Design Research Centre, OCADU
>>>> _______________________________________________________
>>>> fluid-work mailing list - fluid-work at fluidproject.org
>>>> To unsubscribe, change settings or access archives,
>>>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>> 
>>> _______________________________________________________
>>> fluid-work mailing list - fluid-work at fluidproject.org
>>> To unsubscribe, change settings or access archives,
>>> see http://fluidproject.org/mailman/listinfo/fluid-work
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20101018/d3f92acc/attachment.htm>