Comment 1 by briang1 on 2013-11-09 09:13
This effect is also seen in IE8 in XP on this page, but not in Firefox. I suspect that they put the service message in quickly just above this heading and slightly upset some browsers when they did so.
IO - inputCore.InputManager.executeGesture (09:04:01):
Input: kb(desktop):shift+e
IO - speech.speak (09:04:01):
Speaking ('en_GB'), u'out of list', u'main landmark ', u'Books without Barriers - Accessible books, magazines and periodicals', u'heading level 1 Alt+1'
IO - inputCore.InputManager.executeGesture (09:04:07):
Input: kb(desktop):downArrow
IO - speech.speak (09:04:08):
Speaking ('en_GB'), u'heading level 3', u'Readers with print disabilities in the United Kingdom have access to a', u' rapidly expanding collection '
IO - inputCore.InputManager.executeGesture (09:04:11):
Input: kb(desktop):upArrow
IO - speech.speak (09:04:11):
Speaking ('en_GB'), u'heading level 1 Alt+1', u'Books without Barriers - Accessible books, magazines and periodicals'
IO - speech.speak (09:04:11):
Speaking ('en_GB'), u'focus mode'
IO - inputCore.InputManager.executeGesture (09:04:28):
Input: kb(desktop):NVDA+f1
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (09:04:28):
Developer info for navigator object:
name: u'Books without Barriers - Accessible books, magazines and periodicals'
role: ROLE_EDITABLETEXT
states: STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.IAccessible.MSHTML.MSHTML object at 0x03E5F210>
Python class mro: (<class 'NVDAObjects.IAccessible.MSHTML.MSHTML'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: None
location: (231, 460, 577, 217)
value: ''
appModule: <'appModuleHandler' (appName u'iexplore', process ID 1404) at address 3d283d0>
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 393998
windowClassName: u'Internet Explorer_Server'
windowControlID: 0
windowStyle: 1442840576
windowThreadID: 2552
windowText: u''
displayText: u'Bookshare will be unavailable from 5:00 to 11:00 PM PT on Friday, NovembeeBBerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrreeBBeeerrsrr' (truncated)
IAccessibleObject: <POINTER(IAccessible) ptr=0x1bbc80 at 3d1c940>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=393998, objectID=28, childID=0
IAccessible accName: u'Books without Barriers - Accessible books, magazines and periodicals'
IAccessible accRole: ROLE_SYSTEM_TEXT
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)
IAccessible accDescription: None
IAccessible accValue: None
MSHTML node has ancestor IAccessible: False
MSHTML nodeName: u'H1'

It is probably the case this affects all versions of IE.

Comment 2 by mdcurran on 2013-11-10 22:41
The heading in question has a tabindex of "-1", as well as an accesskey. I assume the tabindex was put there as otherwize Internet Explorer ignores accesskey.
Indirectly, NVDA does not expect that headings can be focusable, and therefore falls back to MSAA information if they are focusable, but Internet Explorer exposes information equivalent to an edit field.
We should probably handle this case better. But it should also be asked whether its useful, or in deed correct, to have accesskeys on headings, especially if a prerequisite is that the heading is focusable.

The provided example does not work anymore in IE 11. @michaelDCurran, in #3633 (comment) it sounded as if you knew what the problem was and was going to address it. Is this still the case or something that still needs to be fixed?

Closing as worksforme as bookshare.org no longer has the strange heading and this was the only case reported.