X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

NPAPI Plugin & IA2 accessibility Support - how can the plugin controls contribute to IA2?

Kuphostiwe

We have an NPAPI Plugin which is embedding a Windows Application inside Firefox using the plugin container. The application we are embedding is being modified to support IA2 interface for it's various controls. When we embed this in IE (using BHO), it all works fine and JAWS works fine. But when we embed this in Firefox, as we hover over our application inside the FF tab, all we see is "Embedded Object", so basically FF is intercepting the messages and not letting the underlying window get hold of it and return appropriately. Even clicking inside out application doesn't help. Is there a way to tell Firefox that my add-on support IA2 so let it take care of it's own things?

We have an NPAPI Plugin which is embedding a Windows Application inside Firefox using the plugin container. The application we are embedding is being modified to support IA2 interface for it's various controls. When we embed this in IE (using BHO), it all works fine and JAWS works fine. But when we embed this in Firefox, as we hover over our application inside the FF tab, all we see is "Embedded Object", so basically FF is intercepting the messages and not letting the underlying window get hold of it and return appropriately. Even clicking inside out application doesn't help. Is there a way to tell Firefox that my add-on support IA2 so let it take care of it's own things?

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Google Update
  • Shockwave Flash 11.9 r900
  • Next Generation Java Plug-in 10.45.2 for Mozilla browsers
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Notes embedded control plugin for Mozilla
  • Google Talk Plugin Video Accelerator version:0.1.44.29
  • Version 4.9.1.16010
  • GEPlugin
  • Adobe PDF Plug-In For Firefox and Netscape 11.0.05
  • 5.1.20913.0
  • Unity Player 4.2.1f4
  • IBM DOLS Plugin 9.0.1
  • VLC media player Web Plugin 2.0.6
  • IE Tab 2 Plug-in for Mozilla/Firefox
  • Mozilla Plug-in
  • Next Generation Java Plug-in 1.6.0 for Mozilla browsers
  • NVIDIA 3D Vision Streaming plugin for Mozilla browsers
  • NVIDIA 3D Vision plugin for Mozilla browsers
  • VMware Remote Console and Client Integration Plug-in

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0

Eminye Imininingwane

guigs 1072 izisombululo 11697 izimpendulo
Kuphostiwe

If I understand this correctly, it looks like there is an API that is used to properly pass the DOM objects from the embedded application to the extension interface.

References

Hopefully this points you in the right direction, because of the platform access that NAPI plugins use it looks like this may be causing the issue? The MDN community and stackoverflow.com will have a better expertise on the subject as well.

If I understand this correctly, it looks like there is an API that is used to properly pass the DOM objects from the embedded application to the extension interface. References *Plugins [https://developer.mozilla.org/en-US/Add-ons/Plugins?redirectlocale=en-US&redirectslug=Plugins] *Embedded element plug in display :[https://developer.mozilla.org/en-US/Add-ons/Plugins/Gecko_Plugin_API_Reference/Plug-in_Basics?redirectlocale=en-US&redirectslug=Gecko_Plugin_API_Reference%2FPlug-in_Basics#Using_the_embed_Element_for_Plug-in_Display] *Accessibility apis for Firefox is implemented using msaa and ia2 [http://dev.bowdenweb.com/a11y/accessibility-apis.html] * IA2 roles MDN: [https://developer.mozilla.org/en-US/docs/Web/Accessibility/AT-APIs/IA2/Roles] * [https://developer.mozilla.org/en-US/docs/Web/Accessibility/AT-APIs/IA2/Attrs?redirectlocale=en-US&redirectslug=Accessibility%2FAT-APIs%2FIA2%2FAttrs] * [https://developer.mozilla.org/en-US/docs/Web/Accessibility/AT-APIs/IA2/Attrs?redirectlocale=en-US&redirectslug=Accessibility%2FAT-APIs%2FIA2%2FAttrs] Hopefully this points you in the right direction, because of the platform access that NAPI plugins use it looks like this may be causing the issue? The MDN community and stackoverflow.com will have a better expertise on the subject as well.