W3C home > Mailing lists > Public > public-html@w3.org > April 2011

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

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Tue, 26 Apr 2011 09:50:41 +0100
Message-ID: <BANLkTim81jPh6b3z==wYR6ztOY-NR2cJpQ@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, Michael Cooper <cooper@w3.org>, Joseph Scheuhammer <clown@alum.mit.edu>, W3C WAI-XTECH <wai-xtech@w3.org>, HTMLwg <public-html@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, David Bolter <dbolter@mozilla.com>
hi all,

 I would suggest that people who are interested should have  a look at and
contribute their feedback to the wiki page:

Verbose Descriptor Requirements Feedback
http://www.w3.org/WAI/PF/HTML/wiki/Talk:Verbose_desc_reqs

lest we end up with an alternative mechanism to longdesc that has the same
or similar problems.

regards
stevef

On 26 April 2011 08:22, Steve Faulkner <faulkner.steve@gmail.com> wrote:

> 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
>



-- 
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 08:51:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:28 GMT