You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Search for the entry called "exactly {space:.1f} pt" with control+F dialog
Press tab until you reach the "Source text" edit field
Actual behaviour
You need to press 3 times tab:
after the first tab press, NVDA reports panel and a pane focused; using NVDA's object navigation, we can see that this pane contains a static text "line spacing value" corresponding to the context information provided by pgettext in the source code.
after the second tab press, NVDA reports panel and a pane is focused; using NVDA's object navigation, we can see that this panel contains a static text "Python format" which informs us that the string to translate is a Python formatted string.
after the third tab press, you finally reach the source text edit field.
Expected behaviour
First tab should directly jump to the source text edit field.
Panes should not accept focus if they do not contain focusable objects. Static text should not be focusable.
Versions
poedit: 3.5.2
Windows 10 22H2 (AMD64) build 19045.5131
The text was updated successfully, but these errors were encountered:
Issue described with the use of NVDA screen reader. But the issue is broader than only screen reader users.
Steps to reproduce
Actual behaviour
You need to press 3 times tab:
pgettext
in the source code.Expected behaviour
First tab should directly jump to the source text edit field.
Panes should not accept focus if they do not contain focusable objects. Static text should not be focusable.
Versions
The text was updated successfully, but these errors were encountered: