- From: Janina Sajka <janina@rednote.net>
- Date: Fri, 24 Feb 2012 10:02:05 -0500
- To: Steve Faulkner <faulkner.steve@gmail.com>
- Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, James Craig <jcraig@apple.com>, Judy Brewer <jbrewer@w3.org>, Andi Snow-Weaver <andisnow@us.ibm.com>
Hi, Steve: Steven Faulkner writes: > Hi all, > > suggest it would be useful for someone with the requisite knowledge of > the various ARIA spec responds on the html wg to Bens questions: > http://lists.w3.org/Archives/Public/public-html/2012Feb/0189.html > Yes, but exactly what should that response be? I will file bugs against the 9 citations I've found being used in the HTML-WG for us to review during the upcoming PF F2F: http://lists.w3.org/Archives/Public/wai-xtech/2012Feb/0052.html Beyond that I suppose I could say that some of these citations reflect old guidance not recently updated. That doesn't seem responsive, particularly. Suggestions? Janina > regards > Stevef > > ---------- Forwarded message ---------- > From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> > Date: 13 February 2012 20:57 > Subject: Re: Split Issue 30? > To: Jonas Sicking <jonas@sicking.cc>, Charles Pritchard > <chuck@jumis.com>, John Foliot <john@foliot.ca>, Sam Ruby > <rubys@intertwingly.net>, public-html@w3.org > > > On Mon, Feb 13, 2012 at 8:22 PM, Janina Sajka <janina@rednote.net> wrote: > > ing aria-describedby for long text descriptions is a dead issue from the > > PF's perspective. > > If this is the PFWG's position, why isn't it reflected in the ARIA > documents maintained by PFWG, for example: > > http://www.w3.org/WAI/PF/aria-practices/#Descriptions_external > > > Attempts so to do overload describedby. That's unacceptable. > > > > Even should it prove there's some way by which browsers might pass > > marked up content to the a11y APIs so that these APIs will not flatten > > that content to straight text > > You mean like the ways the ARIA implementation guide suggests? > > http://www.w3.org/WAI/PF/aria-implementation/#mapping_additional_relations_reverse_relations > > > describedby still does not meet the > > requirements of a long text mechanism. > > > Specifically, describedby is > > intended for content that is to be read automatically as it is > > encountered. > > That seems like critical information about aria-describedby. If that's > the PF's position, why doesn't the formal definition of > aria-describedby say that: > > http://www.w3.org/WAI/PF/aria/states_and_properties#aria-describedby > > See also the other links I already collected, which show that the spec > text around aria-describedby is very different from what you're > describing: > > http://lists.w3.org/Archives/Public/public-html/2012Feb/0010.html > > -- > Benjamin Hawkes-Lewis > > > > -- > 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 -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Chair, Open Accessibility janina@a11y.org Linux Foundation http://a11y.org Chair, Protocols & Formats Web Accessibility Initiative http://www.w3.org/wai/pf World Wide Web Consortium (W3C)
Received on Friday, 24 February 2012 15:02:51 UTC