You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by mwhapples on 2013-10-12 23:37
If you create a word document with an embedded object and set the alt text of the embedded object to contain a character which needs escaping when in an attribute in XML (eg. quote mark " ), NVDA will not see that embedded object as it will get an XML parse error.
Steps to reproduce:
Create a new word document.
Insert an embedded object (in my case I used MathType to put in an equation).
Set the alt text of the embedded object to contain double quotes (eg. a " b).
move the word cursor over the embedded object and observe what NVDA presents in speech and Braille.
Expected: NVDA will announce the embedded object and speak and Braille the alt text.
Actual: NVDA does not announce anything, including not announcing the presence of the embedded object.
Using NVDA 2013.2 and tested with Word 2007 and 2010.
The text was updated successfully, but these errors were encountered:
Comment 1 by mwhapples on 2013-10-12 23:42
I forgot to mention that I have tried this with other screen readers and they work as expected. Also examining the word document's XML inside the docx shows that word has escaped this character in the underlying file, so the word document is valid XML.
Reported by mwhapples on 2013-10-12 23:37
If you create a word document with an embedded object and set the alt text of the embedded object to contain a character which needs escaping when in an attribute in XML (eg. quote mark " ), NVDA will not see that embedded object as it will get an XML parse error.
Steps to reproduce:
Expected: NVDA will announce the embedded object and speak and Braille the alt text.
Actual: NVDA does not announce anything, including not announcing the presence of the embedded object.
Using NVDA 2013.2 and tested with Word 2007 and 2010.
The text was updated successfully, but these errors were encountered: