- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Thu, 8 Mar 2012 08:24:18 +1100
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, Richard Schwerdtfeger <schwer@us.ibm.com>, W3C WAI-XTECH <wai-xtech@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
On Thu, Mar 8, 2012 at 7:41 AM, Janina Sajka <janina@rednote.net> wrote: > Leif Halvard Silli writes: >> Leif Halvard Silli, Wed, 7 Mar 2012 20:04:16 +0100: >> > Janina Sajka, Wed, 7 Mar 2012 16:47:51 +0000: >> >> >>> Question: Is there a chance that "we could do" @aria-describedat *now*? >> >>> I am convinced that the chances for a amicable solution would increase >> >>> greatly if one could move from talk to action with regard to >> >>> @aria-describedat. >> >> >> >> You're asking the core question, imho. I wish we could simply say "yes" >> >> and be done with it, >> > >> >> Unfortunately, ARIA-DescribedAt doesn't exist anywhere except on our "To >> >> Do" list. >> > >> > So, the process is the reason we can't say 'use @aria-describedat' ... > > > Heavens, no! > > > Explain to me, if you think the process is at fault, why we should drop > everything currently in process to create a substitute for somethingthat already exists. Please explain this wisdom, because it sounds like folly to me. It is the reason you brought up. So, if you don't mind, could you explain the process that you foresee for the introduction of @aria-describedat and how long it will take before we get such a specification? Regards, Silvia.
Received on Wednesday, 7 March 2012 21:25:26 UTC