Hi ben,
>But that's the very least of the problems here, since the same company
>who maintain VoiceOver also maintain the accessibility API and the
>main browser on VoiceOver's platform, so they are free to make changes
>to the rest of the stack to support VoiceOver.
Indeed
just didn't want arguments to be based on false assumptions.
While it is true they are "free to make changes to the rest of the stack to
support VoiceOver." assuming they will, without clear indications from them
is not useful.
regards
steve
On 2 February 2012 11:05, Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com
> wrote:
> On Thu, Feb 2, 2012 at 10:39 AM, Steve Faulkner
> <faulkner.steve@gmail.com> wrote:
> >> Apple Accessibility API), AT could query the DOM to find the referenced
> >> description elements and map them
> >> back to the accessibility tree.
> >
> > my understanding is that VoicOver does not query the DOM directly at
> all, by
> > design.
>
> Indeed.
>
> But that's the very least of the problems here, since the same company
> who maintain VoiceOver also maintain the accessibility API and the
> main browser on VoiceOver's platform, so they are free to make changes
> to the rest of the stack to support VoiceOver.
>
> --
> 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