26
edits
NPAPI:NativeAccessibility: Difference between revisions
Jump to navigation
Jump to search
no edit summary
BradTaylor (talk | contribs) |
BradTaylor (talk | contribs) No edit summary |
||
| Line 33: | Line 33: | ||
'''NPAPI Native Accessibility Support for Linux''' | '''NPAPI Native Accessibility Support for Linux''' | ||
* Last modified: | * Last modified: Oct 8, 2009 | ||
* Author: Brad Taylor, Novell, Inc. | * Author: Brad Taylor, Novell, Inc. | ||
* Contributors: | * Contributors: | ||
Plugins have the need to provide accessibility support to the browser so they can be accessed by assistive technologies like screen readers and testing tools. Most common web browsers already provide an accessible implementation of DOM content, but thus far, can only export a blank (and therefore useless) object when it comes across a plugin. | Plugins have the need to provide accessibility support to the browser so they can be accessed by assistive technologies like screen readers and testing tools. Most common web browsers already provide an accessible implementation of DOM content, but thus far, can only export a blank (and therefore useless) object when it comes across a plugin. | ||
''NOTE'': This approach should be extensible to other accessibility frameworks, e.g.: windowless Windows plugins or OS X Accessibility. | |||
==== In Process Plugins ==== | ==== In Process Plugins ==== | ||
| Line 62: | Line 64: | ||
''NOTE'': The proposed addition to ATK is not yet available, and slated for completion in Q1 2010. | ''NOTE'': The proposed addition to ATK is not yet available, and slated for completion in Q1 2010. | ||