- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Wed, 14 Mar 2012 18:12:31 +0100
- To: Steve Faulkner <faulkner.steve@gmail.com>
- Cc: John Foliot <john@foliot.ca>, Richard Schwerdtfeger <schwer@us.ibm.com>, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Charles McCathieNevile <chaals@opera.com>, W3C WAI-XTECH <wai-xtech@w3.org>, HTMLAccessibility Task Force <public-html-a11y@w3.org>
Steve Faulkner, Wed, 14 Mar 2012 16:37:50 +0000: > I say this is limited as it suffers from the limitations of the AT > implementations i.e. only opens the URL in a new window. Fair point. But in Webkit, until it fixes its 'skip to links' bug, it might be better, in that browser, to open in a new window rather than trying to move the focus to e.g. another node in the same browser context ... ?! >> Absolutely! What I continue to question is why we are hell-bent on pushing > this into the realm of the Accessibility APIs? > > i guess what you mean is why push it into the realm of AAPI support only, > without other general UI support. +1 For being hell-bent on proper support in a11y APIs: It's what brings credibility to the project of supporting it in the general UI. [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=16186 -- leif halvard silli
Received on Wednesday, 14 March 2012 17:13:09 UTC