seanbudd
commented
5 months ago Welcome @CoolColin ,
We are unable to process this issue as it stands.
- To be able to reproduce this issue, we need a sample to test with.
- Please reproduce this issue and provide a log file of the behaviour. Ensure your log level is set to debug in general preferences.
- This is very likely a problem with the implementation of the application, as a starting point please submit feedback to the authors to let them know about the problem.
Kind Regards, NV Access Software Developers
Steps to reproduce:
Open a XFA PDF form that has had extended rights added. It must also have JavaScript validation. Populate a validated field incorrectly in order to throw the dialogue. Once accepted and the user is returned to the form all fields after that will simply read "& Signature text frame".
Actual behavior:
It seem that when a NVDA user is attempting to populate a XFA PDF form with extended rights added, the form field properties are not in fact reading back to the user correctly. It seems to pick up their label or custom SR text fine until a validation error is thrown. After that point all fields are being identified in the same manner. "& Signature Text frame".
This will continue throughout the rest of the form at this point and the user is unable to understand what any field is in fact for.
Expected behavior:
The user expects to have the individual form fields identifying values read correctly. First Name should announce as "First Name, edit" no matter if a validation dialogue has been presented to the user or not.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
NVDA 2024 installed directly.
NVDA version:
The version is NVDA 2024
Windows version:
Windows 11 notebook
Name and version of other software in use when reproducing the issue:
Designer 6.5 and Adobe Reader Continuous Release Version 2024.002.20687
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.
Yes. Same behaviour occurs now with NVDA 2023 also
If NVDA add-ons are disabled, is your problem still occurring?
I have no add-ons
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes