Reported by jteh on 2009-11-16 23:46
There are two accessibility implementations in Adobe Acrobat/Reader: static PDF (probably the majority of PDFs) and XFA PDF. For the static PDF implementation, the unique ID is specified as the IAccessible child ID (which is what NVDA does). For the XFA PDF implementation, the unique ID is specified as the IAccessible object ID. NVDA has problems with these PDFs for this reason.
Tasks:
- The !AdobeAcrobat vbuf backend must handle events for positive obj IDs and update the appropriate node.
getNVDAObjectFromIdentifier() in the !AdobeAcrobat buffer needs to specify the unique ID as the obj ID when working with an XFA PDF.
- There doesn't seem to be any elegant way to detect an XFA PDF.
- We will need to use the non-existence of the read-only state on the document and page objects to determine that this is an XFA PDF.
- Similarly, the !AcrobatNode NVDAObject must correctly set the event parameters on the object for XFA PDFs.
Reported by jteh on 2009-11-16 23:46
There are two accessibility implementations in Adobe Acrobat/Reader: static PDF (probably the majority of PDFs) and XFA PDF. For the static PDF implementation, the unique ID is specified as the IAccessible child ID (which is what NVDA does). For the XFA PDF implementation, the unique ID is specified as the IAccessible object ID. NVDA has problems with these PDFs for this reason.
Tasks:
getNVDAObjectFromIdentifier()in the !AdobeAcrobat buffer needs to specify the unique ID as the obj ID when working with an XFA PDF.