Re: Request to re-open issue 131

Hi Sam,

also note that a specific requirement in HTML5 in regards to the title
attribute was something I asked for back in 2008 [1].

In the editors response by way of rejection he suggested 3 1/2 years
ago that display of title would be implemented sooner rather than
later.

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=5807


Exactly how long is long enough to consider that including advice, in
the spec that relies on non existent implementations for results to be
accessible, is a good idea? I though that was one of the complaints
with HTML 4, that it did not match reality.

I certainly consider that counter proponents on this issue should be
required to get testimonials from implementors to say they WILL
implement input device independent access to title attribute content
for all the contexts it is used in the contested spec text and details
of  how that will practically be implemented and within a realistic
timeframe.



regards
stevef


On 11 December 2011 17:18, Steve Faulkner <faulkner.steve@gmail.com> wrote:
> Hi Sam,
>
> Issue is that there is NO IMPLEMENTATION REQUIREMENT SPECIFIED in HTML5 to
> provide input device independent access to title attribute content.
>
> the nearest that the spec gets is this statement
>
> "User agents are encouraged to make it possible to view tooltips
> without the use of a pointing device, since not all users are able to
> use pointing devices." [1]
>
> So how can I bridge the gap when there is  NO IMPLEMENTATION
> REQUIREMENT SPECIFIED?
>
> [1] http://dev.w3.org/html5/spec/Overview.html#the-title-attribute-0
>
> regards
> Stevef
>
> On 11 December 2011 16:27, Sam Ruby <rubys@intertwingly.net> wrote:
>> On 12/10/2011 05:23 PM, Steve Faulkner wrote:
>>>
>>> Hi SAm
>>>
>>> you wrote:
>>>
>>> ">  Is it fair to assume that this information is relevant to Issue 192?"
>>>
>>> I think it is fair to assume that this information is relevant to:
>>>
>>> ISSUE-182: Advice in spec about annotations promotes inacces sible content
>>> http://www.w3.org/html/wg/tracker/issues/182
>>>
>>> ISSUE-190: Replace poor coding example for figure with multiple images
>>> http://www.w3.org/html/wg/tracker/issues/190
>>>
>>> ISSUE-192: title attribute definition does not match reality
>>> http://www.w3.org/html/wg/tracker/issues/192
>>>
>>> and the request to re-open Issue 80 (in regards to title/alt attribute
>>> conformance
>>> http://www.w3.org/html/wg/wiki/ChangeProposals/notitle
>>
>>
>> If you can bridge the gap between "publicly stated that they have no plans
>> to"[1] and "stating that they won't implement what is the W3C Working
>> Draft"[2], then I would say that that would be considered a strong
>> objection.
>>
>>> regards
>>> Stevefss
>>s
>>
>> [1] http://lists.w3.org/Archives/Public/www-archive/2011Dec/0013.html
>> [2] http://lists.w3.org/Archives/Public/www-archive/2011Dec/0012.html
>
>
>
> --
> with regards
>
> Steve Faulkner
> Technical Director - TPG
>
> www.paciellogroup.com | www.HTML5accessibility.com |
> www.twitter.com/stevefaulkner
> HTML5: Techniques for providing useful text alternatives -
> dev.w3.org/html5/alt-techniques/
> Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html



-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html

Received on Sunday, 11 December 2011 18:21:50 UTC