Re: False aria-describedby expectations in ARIA Authoring Practices (longdesc)

Hi Jonas,

> https://bugzilla.mozilla.org/show_bug.cgi?id=652635

Thanks!

from looking at the code its unclear to me how the URL is exposed to
AT, is it exposed via the acc description as other describedby content
is, if not how?


>> I don't believe I proposed any such thing.

then i don't see why there would be any push back on providing correct
practical guidance for authors, not guidance based on some future
possible implementation of a feature.


regards
stevef

On 25 April 2011 21:43, Jonas Sicking <jonas@sicking.cc> wrote:
> On Mon, Apr 25, 2011 at 1:14 PM, Steve Faulkner
> <faulkner.steve@gmail.com> wrote:
>> Hi Jonas
>>
>> "By modifying the code that reads from the DOM and exposes the relevant information to AT."
>>
>> Can you provide the code or a link to the patch?
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=652635
>
>> You wrote:
>> "Possibly, but wouldn't we be building a better world by leaning on browser vendors to fix their aria implementations, rather than leaningon aria authors to tell them to "dumb down" their aria usage."
>>
>> Providing authoring guidance on what works leads to better practical outcomes for users. Leading developers to code to fictional features does not.
>
> I don't believe I proposed any such thing.
>
> / Jonas
>



-- 
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 Tuesday, 26 April 2011 07:26:32 UTC