Inline Edit Suggestions

[Michael S Elledge]

Hi everyone--

Everette's message inspired me to try out the inline edit example with 
JAWS 9 and Firefox 3. Here are some things I noticed:

Behavior seems consistent and makes sense, i.e., turn on forms mode to 
edit, press up or down arrow to read preceding text and form field, use 
back button or delete key to delete letters, press enter to save change, 
with the following exceptions:

1) Pressing "home" when forms mode is on should take you to the 
beginning of the editable text, likewise "end" should take you to the 
end of the editable text. Similarly, there should be some way to 
highlight the full line of editable text.
2) Focus moves to each editable area as you tab through the page, but 
prior content is sometimes read (first field "over the gazy slog" read 
for the next three fields until "brown fox jumped over" is reached.)
3)Text within the editable "button" fields is read when forms mode is 
turned on, then followed by the heading and column headings in Example 5 
("over the lazy dogs Example 5. High contrast themed inline edit 
scenarios subject from date delete?"
4) Example 2 is highlighted differently than the other edit fields when 
it receives focus (assume that's correct, and not a bug)
5) Editable fields are not identified when page is being read (with "Say 
All", ins + F9), but when tabbed to are read as "over the lazy dog button".
6) Can a different term than "button" be used to describe editable 
field, such as "editable field"?
7) Tables lack column headers so cells not associated with headings 
(easy fix). This would be good to repair so we can see how inline edit 
behaves within a properly constructed table.

Hope this is helpful as well. Let me know if you have any questions.

Mike

Justin wrote:
> 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
>
> _______________________________________________________
> 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 --------------
A non-text attachment was scrubbed...
Name: elledge.vcf
Type: text/x-vcard
Size: 313 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20081210/b1960680/attachment.vcf>