Inline Edit Suggestions

[Justin]

Hi Everett,

I have filed the issue you mentioned, in your  first point, as a bug.

http://issues.fluidproject.org/browse/FLUID-1953

Thank you
Justin

On 10-Dec-08, at 7:18 AM, E.J. Zufelt wrote:

> Good morning,
>
> After having tested the inline edit example ( http://build.fluidproject.org/fluid/fluid-components/html/InlineEdit.html 
>  ) with JAWS 10, I have the following feedback.
>
> 1. After I press enter to submit changes to the editable text the  
> edit control remains visible to JAWS.  It was mentioned on irc  
> yesterday that this could be because the edit control is being  
> hidden with visible:hidden. I have tested this and it is correct.   
> The edit control needs to be hidden with display:none.
>
> I have made an example to demonstrate at ( http://zufelt.ca/aria/examples/InputExample.html 
>  ).  JAWS detects the first two edit controls on my example page,  
> but not the third.
>
> 2. I think that role:button is a bit misleading to screen-reader  
> users.  I think that a better way of classifying editable text would  
> be role:textbox property:readonly.  Someone might have to help me  
> out here because when I created a div with these attributes (see  
> bottom of my example page) JAWS 10 identified it as an editable  
> textbox and did not place any of the original text within it.
>
> Looking forward to your feedback,
> Everett
> Adaptive Technology Resource Centre, University of Toronto
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work