Re: plugin accessibility
Re: plugin accessibility
- Subject: Re: plugin accessibility
- From: Michael Ash <email@hidden>
- Date: Sun, 16 Aug 2009 16:12:45 -0400
On Aug 16, 2009, at 3:55 PM, David Bolter wrote:
I'm not writing a plugin, I'm trying to make sure we take the right
approach in providing browser support for people who want to have
their plugin's accessible object tree inserted (as a child) into the
main accessible object tree. Maybe this makes no sense for Cocoa
a11y but I'm still not sure. This is a request currently coming from
Linux:
https://wiki.mozilla.org/Plugins:NativeAccessibility
... but it affects a standard API: NPAPI.
I have to agree with Christiaan here: you've done a terrible job of
explaining what you were really after before this point. Now that I
finally see, clearly and concisely, an explanation of what you're
after, it completely changes everything you asked previously. Again,
human communications difficulties, but your previous posts look like
they were written with the assumption that we already knew what you
were talking about!
Anyway, as for your actual question, now that we finally know what it
is, I see two pieces to it:
1) You're curious about how Safari does it, if it does it, so you can
imitate it. WebKit is open source, so go look. If you want to ask the
developers, WebKit has several mailing lists:
http://webkit.org/contact.html
2) You're looking for advice on how to implement this. Well, the short
answer is, it's your app and your plugin API, so design something
suitable. Accessibility just queries your app, so design it to respond
to queries in such a way that it can pass them on to plugins when
appropriate. There's nothing really Accessibility-specific about this
idea.
Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden