enhancing screen reader ux of inline edit

[Alison Benjamin]

Hello

A little bit of background, I have flip-flopped a bit over what ARIA role an
inline edit should have. ARIA role of button for the inline edit is actually
best... because having the view and edit mode be the same makes the screen
reader suggest that you can edit in view mode (when you can't). Anyway,
Laurie and I must have missed this problem when I suggested the role being a
textbox.  Thanks Justin for pointing this out! Now that's settled, so

-following the advice of dojo, I added a title="editable button" to the
class that contains the inline edit selector
-worked with two different JAWS configurations to test
    Config manager > set options > HTML options > links: "use title" and
...> links: "use screen text"

Results:
- FF3 reads titles, IE8 does not (??)
- NVDA & FF3 reads titles.

details:
FF3/JAWS 10
-Navigating with arrow keys, user hears:
"Blockquote. The quick brown fox jumped over the lazy dogs [BUTTON] and then
dot dot dot. "
- tabbing and shift tabbing to the inline edit reads the title I give,
"editable button"

IE8/JAWS 10
-Navigating with arrow keys, user hears:
"Blockquote. The quick brown fox jumped over the lazy dogs [BUTTON] and then
dot dot dot.
- shift tabbing and tabbing to inline edit reads "over the lazy dogs
[BUTTON]"." i.e.: regardless of JAWS' configuration, the title added is not
read. ???

Next steps:
- user testing
- enhance Fluid's inline edit demos with titles so they're UX test-ready &
close FLUID-2652.
- What is a meaningful title attribute for an inline edit? Some
possibilities: "Editable button". "Editable text". I'll be asking this to
the testers.
- update API so end users account for need for titles?
- graceful degredation for browsers/ATs that don't support ARIA?

Any other suggestions or issues? Justin did I miss anything?

Thanks,
Alison
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20091201/2ae2eae5/attachment.html>