Re: plugin accessibility
Re: plugin accessibility
- Subject: Re: plugin accessibility
- From: David Bolter <email@hidden>
- Date: Sat, 15 Aug 2009 14:11:01 -0400
Thanks for the link. Unfortunately I'm particularly interested in how
plugins are inserted into the heirarchy (if they are), and especially
how this is implemented for OOP plugins (probably wrapping and
remoting). I'll investigate.
If anyone on this list is has done or is currently implementing this I'd
like to chat. Note: I'll likely be pinging Jonas at Google soon too;
note:
http://sites.google.com/a/chromium.org/dev/developers/design-documents/accessibility#TOC-Synchronous-IPC-for-Accessibility
cheers,
David
On 8/15/09 1:51 PM, Christiaan Hofman wrote:
On Aug 15, 2009, at 7:40 PM, David Bolter wrote:
Hi Christiaan,
Thanks for your reply. I was hoping this would be a good way to start
a discussion about OOP plugin accessibility but maybe this list isn't
the right place?
I probably didn't look at the right docs... can you point me to the
one with all the answers? :)
cheers,
David
<http://developer.apple.com/documentation/Cocoa/Conceptual/Accessibility/cocoaAXOverview/cocoaAXOverview.html>
explains how accessibility is implemented in Cocoa. From that it
should be clear that "safari" or "plugin" are totally irrelevant to
the discussion. It only matters stuff is inserted in the hierarchy,
which is more a question of what they do then what they are.
Christiaan
On 8/14/09 5:05 PM, Christiaan Hofman wrote:
On Aug 14, 2009, at 8:37 PM, David Bolter wrote:
Hi all.
Does Safari have any plugin accessibility support?
Yes.
If so, what about for out of process plugins?
cheers,
David
No.
If the answers aren't very useful that's because you're asking the
wrong questions (just a friendly advice, the docs have all the
answers).
Christiaan
_______________________________________________
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