FW: [Bug 10873] Provide a method of explicitly setting a tooltip for an element

Let's discuss Thursday.

-----Original Message-----
From: John Foliot [mailto:jfoliot@stanford.edu] 
Sent: Saturday, October 02, 2010 1:27 PM
To: jimallan@tsbvi.edu; Kelly Ford
Cc: 'Maciej Stachowiak'
Subject: FW: [Bug 10873] Provide a method of explicitly setting a tooltip for an element

UAAG friends,

Please note Maciej's comments below:

> 
> --- Comment #6 from Maciej Stachowiak <mjs@apple.com> 2010-10-02
> 
> Seems to me UAAG 4.1.1 already applies, since it explicitly applies to
> all
> functionality. It would be helpful if the Implementing UAAG 2.0 draft
> could
> give examples of how to offer access to tooltips using the keyboard. It
> seems
> to me this is important for @title even if a new feature is also added.
> 
> http://www.w3.org/TR/2010/WD-IMPLEMENTING-UAAG20-20100617/#gl-keyboard-
> access
> 
> However, UAAG 4.1.1 does not strike me as "device agnostic". It
> specifically
> requires access via the keyboard. This is surely not appropriate for
> devices
> without a physical keyboard, for example the iPhone. iOS has been
> praised for
> its accessibility support, through voice and touch:
> <http://behindthecurtain.us/2010/06/12/my-first-week-with-the-iphone/>.
> Interaction using a virtual onscreen keyboard would be much worse.
> 
> That being said, tooltips themselves do not work very well for any
> users on
> touchscreen devices, since there is no concept of hover. So it is
> probably not
> good for device-independence to further encourage their use.
> 

The full discussion can also be found at:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10873

Received on Tuesday, 5 October 2010 15:07:09 UTC