Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NVDA does not handle all characters which can be in alt text of embedded objects in word documents #3579

Closed
nvaccessAuto opened this issue Oct 12, 2013 · 5 comments
Closed

NVDA does not handle all characters which can be in alt text of embedded objects in word documents #3579

nvaccessAuto opened this issue Oct 12, 2013 · 5 comments
Labels
bug
Milestone
2013.3

Comments

@nvaccessAuto
Copy link

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:

  1. Create a new word document.
  2. Insert an embedded object (in my case I used MathType to put in an equation).
  3. Set the alt text of the embedded object to contain double quotes (eg. a " b).
  4. 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.
@nvaccessAuto
Copy link
Author

Attachment nvda.log added by mwhapples on 2013-10-12 23:40
Description:
Log from NVDA which shows NVDA has a XML parse error.

@nvaccessAuto
Copy link
Author

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.

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2013-10-13 05:43
Changes:
Milestone changed from None to next

@nvaccessAuto
Copy link
Author

Comment 3 by Michael Curran <mick@... on 2013-10-14 23:19
In [1cab6f8]:

nvdaHelper winword support: make sure to encode alt text of graphics/objects appropriate for xml attribute values. Fixes #3579

Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 4 by mdcurran on 2013-10-14 23:21
Changes:
Milestone changed from next to 2013.3

@nvaccessAuto nvaccessAuto added this to the 2013.3 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
2013.3
Development

No branches or pull requests
1 participant
@nvaccessAuto