Comment 1 by briang1 on 2012-07-21 21:41
There have been reports of this ever since the latest flash version came out. Are you sure its not Flash that is the issue? I understand that when some flash object do odd things you may need to manually edit a cfg file. I hope son kind person will elaborate here.
I also see some beta versions of the flash plug in and active x are available already.

Comment 2 by ateu (in reply to comment 1) on 2012-07-22 00:31
Replying to briang1:

There have been reports of this ever since the latest flash version came out. Are you sure its not Flash that is the issue? I understand that when some flash object do odd things you may need to manually edit a cfg file. I hope son kind person will elaborate here.

I also see some beta versions of the flash plug in and active x are available already.

No, I've tested with Intenet Explorer and there is no any problem. Even using google chrome it's possible interact with flash if accessible.

Comment 3 by jteh on 2012-07-22 23:52
What Flash version? Please provide the info that appears when you press NVDA+f1 while focused in the Flash object. Also, note that you need to have the ActiveX version of Flash installed as well.

Comment 4 by ateu (in reply to comment 3) on 2012-07-23 01:39
Replying to jteh:

What Flash version?

11.3.300.265

Please provide the info that appears when you press NVDA+f1 while focused in the Flash object.
Developer info for navigator object:
name: None
role: ROLE_PANE
states: STATE_FOCUSABLE, STATE_FOCUSED
Python object: <NVDAObjects.IAccessible.IAccessible object at 0x052B2BB0>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: None
location: (161, 462, 440, 262)
value: None
appModule: <'appModuleHandler' (appName u'plugin-container', process ID 5752) at address 52cdbf0>
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 394132
windowClassName: u'GeckoPluginWindow'
windowControlID: 0
windowStyle: 1442840576
windowThreadID: 5424
windowText: u''
IAccessibleObject: <POINTER(IAccessible) ptr=0x7afa7f8 at 52cc6c0>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=394132, objectID=-4, childID=0
IAccessible accRole: ROLE_SYSTEM_CLIENT
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (22:28:07):
Developer info for navigator object:
name: None
role: ROLE_EDITABLETEXT
states: STATE_MULTILINE, STATE_READONLY, STATE_FOCUSED, STATE_FOCUSABLE
Python object: <NVDAObjects.Dynamic_IAccessibleRichEdit50WindowNVDAObject object at 0x052E66B0>
Python class mro: (<class 'NVDAObjects.Dynamic_IAccessibleRichEdit50WindowNVDAObject'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.edit.RichEdit50'>, <class 'NVDAObjects.window.edit.RichEdit'>, <class 'NVDAObjects.window.edit.Edit'>, <class 'NVDAObjects.behaviors.EditableTextWithAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: None
location: (2, 40, 1338, 674)
value: u'INFO - nvda (21:29:32):\rStarting NVDA\rINFO - core.main (21:29:33):\rConfig dir: C:\Users\MARLIN\AppDa' (truncated)
appModule: <'nvda' (appName 'nvda', process ID 2564) at address 50f1950>
TextInfo: <class 'NVDAObjects.window.edit.EditTextInfo'>
windowHandle: 459670
windowClassName: u'RICHEDIT50W'
windowControlID: -251
windowStyle: 1377900612
windowThreadID: 2568
windowText: u'INFO - nvda (21:29:32):\r\nStarting NVDA\r\nINFO - core.main (21:29:33):\r\nConfig dir: C:\Users\MARLIN\Ap' (truncated)
IAccessibleObject: <POINTER(IAccessible) ptr=0x7afa6f0 at 51cce90>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=459670, objectID=-4, childID=0
IAccessible accRole: ROLE_SYSTEM_TEXT
IAccessible accState: STATE_SYSTEM_READONLY, STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048644)
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (22:28:16):
Developer info for navigator object:
name: None
role: ROLE_PANE
states: STATE_FOCUSABLE, STATE_FOCUSED
Python object: <NVDAObjects.IAccessible.IAccessible object at 0x052E6790>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: None
location: (161, 462, 440, 262)
value: None
appModule: <'appModuleHandler' (appName u'plugin-container', process ID 5752) at address 52cdbf0>
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 394132
windowClassName: u'GeckoPluginWindow'
windowControlID: 0
windowStyle: 1442840576
windowThreadID: 5424
windowText: u''
IAccessibleObject: <POINTER(IAccessible) ptr=0x7afa850 at 52cc3a0>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=394132, objectID=-4, childID=0
IAccessible accRole: ROLE_SYSTEM_CLIENT
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)

Also, note that you need to have the ActiveX version of Flash installed as well.
It's already installed in my system.

Comment 5 by jteh on 2012-07-23 04:48
I'm not sure how you tested with Chrome, as Chrome uses its own in-built version of Flash which is not accessible.

Flash 11.3's new protected mode for Firefox is the cause of this problem. There is definitely a change we need to make in NVDA, but from what i can tell, Flash's accessibility implementation is now somewhat broken as well, so I'm not sure we can entirely fix this. I'm still investigating.
Changes:
Changed title from "NVDA not Interacting with Embedded Objects in Gecko Browsers" to "Unable to browse Flash content in Firefox with Flash protected mode enabled"

Comment 6 by ateu (in reply to comment 5) on 2012-07-23 09:11
Replying to jteh:

I'm not sure how you tested with Chrome, as Chrome uses its own in-built version of Flash which is not accessible.

Flash 11.3's new protected mode for Firefox is the cause of this problem. There is definitely a change we need to make in NVDA, but from what i can tell, Flash's accessibility implementation is now somewhat broken as well, so I'm not sure we can entirely fix this. I'm still investigating.

Yes, You are right.
I use an older version, chrome 17. I also use Coolnovo, a chrome based browser, which uses chrome 17.
After chrome 18, it's not really possible interact with flash.
Thanks

Comment 7 by briang1 on 2012-07-23 09:28
So rather than edit th cfg so protected mode is off, could one just reinstall an older version of the flash plug in instead and disable updates till the issue is clearer? If so which version?

Comment 8 by jteh (in reply to comment 7) on 2012-07-23 09:49
Replying to briang1:

So rather than edit th cfg so protected mode is off, could one just reinstall an older version of the flash plug in instead and disable updates till the issue is clearer?

In theory, yes. However, I can't recommend this due to potential security problems. 11.3 may include security fixes other than protected mode.

If so which version?

11.2, I guess. Protected mode for Firefox is new to 11.3.

Comment 9 by jteh on 2012-07-24 01:48
82297a1 allows browse mode to be used when Firefox Flash in protected mode gets focus. Unfortunately, pressing enter on the embedded object isn't enough to give it focus due to a bug in Flash, so this isn't a complete fix. I'm still investigating and will file bugs with Adobe/Mozilla as appropriate.

Comment 10 by jteh on 2012-07-24 06:25
AdobeBug:3287506 covers the focus problem.

Also, there's another weird issue where an invisible edit field gets focus whenever the Flash plugin launches. This is covered by AdobeBug:3223393.

Comment 11 by elliott94 (in reply to comment 3) on 2012-07-24 11:19
Replying to jteh:

Also, note that you need to have the ActiveX version of Flash installed as well.

Doesn't this come included with the main plug-in installer for Firefox, or is this for IE only?

Comment 12 by briang1 on 2012-07-24 12:17
Not really, theey are seperate downloads although if the updater is active it tends to update both for you. I prefer to control what Its installing which is why I hate the current non msi installer as its totally inaccessible in xp!

Comment 13 by jteh on 2012-07-25 07:17
Mozilla are also tracking this: MozillaBug:777247 and MozillaBug:766009.

Comment 14 by elliott94 (in reply to comment 12) on 2012-07-25 09:23
Replying to briang1:

Not really, theey are seperate downloads although if the updater is active it tends to update both for you. I prefer to control what Its installing which is why I hate the current non msi installer as its totally inaccessible in xp!

In that case, what's the difference between the plug-in and ActiveX control? I'm confused. :)

Comment 15 by jteh (in reply to comment 14) on 2012-07-25 23:30
Replying to elliott94:

In that case, what's the difference between the plug-in and ActiveX control?

The plug-in is for Mozilla and other browsers. ActiveX is for IE. However, the plug-in unfortunately doesn't register a component that is needed to access some of the accessibility interfaces, whereas ActiveX does.

Comment 16 by elliott94 (in reply to comment 15) on 2012-08-01 21:44
Replying to jteh:

The plug-in is for Mozilla and other browsers. ActiveX is for IE. However, the plug-in unfortunately doesn't register a component that is needed to access some of the accessibility interfaces, whereas ActiveX does.

Interesting; can registering these components potentially make Flash objects more accessible?

Do you think it'd be an idea to file another bug with Adobe about this?

Comment 17 by jteh (in reply to comment 16) on 2012-08-01 22:23
Replying to elliott94:

the plug-in unfortunately doesn't register a component that is needed to access some of the accessibility interfaces, whereas ActiveX does.

Interesting; can registering these components potentially make Flash objects more accessible?

No. If they aren't registered, NVDA simply won't enable browse mode for Flash at all.

Do you think it'd be an idea to file another bug with Adobe about this?

Possibly, though the chances of it being fixed are low, as NVDA is probably the only screen reader affected by this. In technical terms, other screen readers access this interface in-process, whereas we access it out-of-process.

Comment 18 by briang1 on 2012-08-02 09:21
So then, if one gives the advice to keep the IE flash up to date even if you do not use IE, then will this make things better?

I still think its an anomoly in their coding that they really need to sort out. It might matter in some, as yet not encountered situation later.

Comment 19 by jteh (in reply to comment 10) on 2012-08-09 01:20
Replying to jteh:

Also, there's another weird issue where an invisible edit field gets focus whenever the Flash plugin launches. This is covered by AdobeBug:3223393.

This one is fixed in Flash 11.4.400.252.

Comment 20 by elliott94 (in reply to comment 17) on 2012-08-09 09:19
Replying to jteh:

Replying to elliott94:

the plug-in unfortunately doesn't register a component that is needed to access some of the accessibility interfaces, whereas ActiveX does.

Interesting; can registering these components potentially make Flash objects more accessible?

No. If they aren't registered, NVDA simply won't enable browse mode for Flash at all.

Interesting; I've never installed the IE plug-in (I assume the ActiveX control is installed at the same time), but in Firefox Flash objects seem to work without any issues - I can hit enter on an embedded object and I can interact with it, etc. Would this not work if the control wasn't installed?

Comment 22 by elliott94 on 2012-08-28 15:17
Has anyone got any more information about comment:20? I'm just interested as to how I'm able to interact with Flash objects in Browse Mode if only the Flash plug-in for Firefox is installed.

Comment 23 by jteh (in reply to comment 22) on 2012-08-28 22:49
Replying to elliott94:

Has anyone got any more information about comment:20? I'm just interested as to how I'm able to interact with Flash objects in Browse Mode if only the Flash plug-in for Firefox is installed.

For the most part, this is just academic; if it works, great. It's possible they fixed this issue, though I doubt it. I also know Windows sometimes comes with its own Flash ActiveX, and depending on the version of Windows, this might register the required stuff.

Comment 24 by elliott94 (in reply to comment 23) on 2012-08-30 11:14
Replying to jteh:

Replying to elliott94:

Has anyone got any more information about comment:20? I'm just interested as to how I'm able to interact with Flash objects in Browse Mode if only the Flash plug-in for Firefox is installed.

For the most part, this is just academic; if it works, great. It's possible they fixed this issue, though I doubt it. I also know Windows sometimes comes with its own Flash ActiveX, and depending on the version of Windows, this might register the required stuff.

That'd explain it. I've only ever installed the Firefox plug-in on my machine, so I guess it's possible that Windows 7 automatically registers the correct control.

Comment 25 by ateu on 2012-11-10 22:05
Today, using not google chrome, but chromium 25.0.1323.0 which do not come with flash bundled, I used the new version of flash 11.5 and NVDA 2012.2.1 and after clicking in the flash object, the buttons gain focus correctly.
However, using firefox and seamonkey, the problem persists.
Can you explain me why this is diferent?

Comment 26 by jteh (in reply to comment 25) on 2013-01-31 04:29
Replying to ateu:

Today, using not google chrome, but chromium 25.0.1323.0 which do not come with flash bundled, I used the new version of flash 11.5 and NVDA 2012.2.1 and after clicking in the flash object, the buttons gain focus correctly.

However, using firefox and seamonkey, the problem persists.

The Flash plugin probably doesn't enable protected mode unless it's running in Firefox.

Comment 27 by jteh on 2013-01-31 04:39
Unfortunately, Adobe don't seem to be inclined to fix this despite several requests. 53bc0c0 works around this by forcing focus when incorrect focus is detected. I thought I'd tried this work around before and it didn't work, but perhaps I didn't test correctly or it works better in newer versions of Flash.
Changes:
Milestone changed from None to 2013.1
State: closed

Comment 28 by ateu on 2013-01-31 09:53
From my tests, It has been fixed.
Thanks.