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

Copying this from the IRC discussion, for consideration (though it is a 
lot of work, potentially?)

(7:05:39 PM) patrickhlauke: if i was a radical, i'd say the title of 
guideline 4.1 should be "ensure full access" (with all available input 
modalities)
[...]
(7:06:44 PM) patrickhlauke: and then split into the various prominent 
modalities, with explanation (e.g. what is keyboard, with definition of 
kbd-like modalities)



On 05/10/2010 15:46, Jim Allan wrote:
> any ideas, comments
>
>
> ---------- Forwarded message ----------
> From: John Foliot<jfoliot@stanford.edu>
> Date: Sat, Oct 2, 2010 at 3:27 PM
> Subject: FW: [Bug 10873] Provide a method of explicitly setting a
> tooltip for an element
> To: jimallan@tsbvi.edu, Kelly Ford<Kelly.Ford@microsoft.com>
> Cc: Maciej Stachowiak<mjs@apple.com>
>
>
> 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
>
>
>


-- 
Patrick H. Lauke

Web Evangelist
Developer Relations Team
Opera - http://www.opera.com

Received on Thursday, 7 October 2010 18:11:56 UTC