Related to accessibility issues.
Details
Wed, Aug 27
Mon, Aug 25
Thu, Aug 21
In the meantime pinentry has been updated also for VSD 3.4.
Backported for VSD 3.4
Wed, Aug 20
the issue is the same in Gpg4win-5.0.0-beta357:
Tue, Aug 19
Looks good to me on GnuPG-VS-Desktop-3.3.90.8-Beta-Standard.msi (3.3.3 betaversion)
Mon, Aug 18
This task is not really actionable. Moreover, it proposes a technical solution instead of just stating the problem that needs to be solved. There may be better solutions, e.g. in the Notepad I decided to move the focus to the message widget that contains the result to make the screen reader read the result.
After studying the logs created by NVDA and its source code I strongly suspect that the problem needs to be fixed in NVDA. NVDA tries to avoid repeating the text of common ancestors of the old and the new focus object, but it fails to detect the Create OpenPGP Certificate dialog as common ancestor of the text edit field in this dialog and the Error (child) window.
Wed, Aug 13
Fixed by adding a patch for Qt 6 (and a patch for Qt 5 in gpg4win-4-branch for VSD 3.4).
Mon, Aug 11
Logging all
Thu, Aug 7
works in vsd3.3.3, tested with VS-Desktop-3.3.90.8-Beta
Fixed and backported for VSD 3.4
Wed, Aug 6
Solved by focusing the result message after the notepad operation is complete. I think that's an acceptable compromise for ensuring that users of assistive tools are informed about the result even if the focus is moved to a different UI element (which, in general, should be avoided because users can get lost).
Tue, Aug 5
Mon, Aug 4
The gold rule of tab order is that tab order follows the usual reading direction, i.e. line by line from left to right. If you press Enter after entering the password in the first input field then the focus should jump to the second input field.
Looks good to me on gpg4win-5.0.0-beta357 @ win10: