NVDA does not read Formula tags in PDF #12715
Labels
app/adobe/acrobat
p3
https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Milestone
Comments
|
This is still an issue in Acrobat 2023.003.20244 - 64 bit. |
|
I am experiencing the same problem. Is there any suggested workaround until this is fixed. |
5 tasks
michaelDCurran
added
the
p3
My only suggestion would be to use a different tag - a Figure, if it's a screenshot of a formula, or a Span, for example - and then provide Alt text starting with some wording to indicate that it's a formula. |
|
There is #16067 that will solve this issue soon from NVDA's side. |
seanbudd
pushed a commit
that referenced
this issue
Jan 22, 2024
Fixes #12715 Summary of the issue: Authors of PDFs can provide alternative text on formular nodes via the 'alt' attribute. However, NvDA ignores this and replaces it with a single space, with the assumption that the formula will contain an inner mathml tree structure. The idea of embedding a full mathml tree structure with in formula nodes was never standardized, and only a few experimental PDFs actually exist. However, it is becoming common for authors to place alt text (perhaps a simple english representation of math) on formula nodes. Description of user facing changes In Adobe Reader, alternative text for formulas will be reported if provided by the author. Description of development approach Adobe Acrobat vbuf backend: Don't replace content in formula tags with a space, rather only do this for math nodes. this ensures NvDA still exposes alt text on formulas. this approach still allows for supporting embedded mathml trees if they exist as a direct child of the formula.
Nael-Sayegh
pushed a commit
to Nael-Sayegh/nvda
that referenced
this issue
Feb 15, 2024
…16067) Fixes nvaccess#12715 Summary of the issue: Authors of PDFs can provide alternative text on formular nodes via the 'alt' attribute. However, NvDA ignores this and replaces it with a single space, with the assumption that the formula will contain an inner mathml tree structure. The idea of embedding a full mathml tree structure with in formula nodes was never standardized, and only a few experimental PDFs actually exist. However, it is becoming common for authors to place alt text (perhaps a simple english representation of math) on formula nodes. Description of user facing changes In Adobe Reader, alternative text for formulas will be reported if provided by the author. Description of development approach Adobe Acrobat vbuf backend: Don't replace content in formula tags with a space, rather only do this for math nodes. this ensures NvDA still exposes alt text on formulas. this approach still allows for supporting embedded mathml trees if they exist as a direct child of the formula.
SaschaCowley
pushed a commit
to SaschaCowley/nvda
that referenced
this issue
Feb 27, 2024
…16067) Fixes nvaccess#12715 Summary of the issue: Authors of PDFs can provide alternative text on formular nodes via the 'alt' attribute. However, NvDA ignores this and replaces it with a single space, with the assumption that the formula will contain an inner mathml tree structure. The idea of embedding a full mathml tree structure with in formula nodes was never standardized, and only a few experimental PDFs actually exist. However, it is becoming common for authors to place alt text (perhaps a simple english representation of math) on formula nodes. Description of user facing changes In Adobe Reader, alternative text for formulas will be reported if provided by the author. Description of development approach Adobe Acrobat vbuf backend: Don't replace content in formula tags with a space, rather only do this for math nodes. this ensures NvDA still exposes alt text on formulas. this approach still allows for supporting embedded mathml trees if they exist as a direct child of the formula.
Adriani90
pushed a commit
to Adriani90/nvda
that referenced
this issue
Mar 13, 2024
…16067) Fixes nvaccess#12715 Summary of the issue: Authors of PDFs can provide alternative text on formular nodes via the 'alt' attribute. However, NvDA ignores this and replaces it with a single space, with the assumption that the formula will contain an inner mathml tree structure. The idea of embedding a full mathml tree structure with in formula nodes was never standardized, and only a few experimental PDFs actually exist. However, it is becoming common for authors to place alt text (perhaps a simple english representation of math) on formula nodes. Description of user facing changes In Adobe Reader, alternative text for formulas will be reported if provided by the author. Description of development approach Adobe Acrobat vbuf backend: Don't replace content in formula tags with a space, rather only do this for math nodes. this ensures NvDA still exposes alt text on formulas. this approach still allows for supporting embedded mathml trees if they exist as a direct child of the formula.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
Actual behavior:
NVDA reads "Heading level one" and then the text followed by "here is a formula" (the text in the paragraph tag after the H1.
And then NVDA stops reading. The Formula tag is not announced, the Alt text assigned to the Formula tag is not read.
Expected behavior:
NVDA should announce the Formula tag (similar to how it says "Graphic" for a Figure tag) and then read the Alt text that's been assigned to the Formula tag.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2021.1beta5
Windows version:
Version 10.0.19042 Build 19042
Name and version of other software in use when reproducing the issue:
Adobe Acrobat Pro DC version 2021.005.20060
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
I have not tried with other versions of NVDA but I have heard similar complaints from other users. I do not, however, have access to which versions of NVDA they are using.
If add-ons are disabled, is your problem still occurring?
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
After running the COM Registration Fixing Tool NVDA worked even worse and wouldn't read the PDF at all, beyond the title of the document (in the document's Properties).
Testing a Formula tag.pdf
The text was updated successfully, but these errors were encountered: