Keyboard navigation with tab does not work on items with plural forms

[CyrilleB79]

Hello

In a .po file, I have to translate a string plural form. When I have selected this string, I can tab until the translation field (singular). But once I am done with this field, I cannot tab forward or shift+tab back to the other focusable items of the UI. This issue does not occur when translating a single string with no plural form.

Could you please have a look? Are you able to confirm this issue? (else, I'll provide more detailed steps) Thanks.

Steps to reproduce the issue

During these steps, only use the keyboard:

1. In poedit, open a .po file containing a string with plural form. Use the file in this zip file.
2. In the list of strings to translate, search for a string having a plural form, e.g. "category {categories}"
3. Press 4 times Tab (through "Original text "singular" edit field", original text "plural" edit field, and "need work" button) to reach the translation "singular" edit field.
4. Press shift+tab to try to move back the focus to the "Need work" button.
   or
5. Press Tab to try to move to next GUI control (in my case should be the translations list, but maybe it depends on the enabled/disabled UI panels)

Note: the names of the GUI controls may not be exact since I am using French localization of the GUI.

Actual result

At step 4 and 5, the focus remains stuck in the translation edit field.

Expected result

• At step 4, the focus should go back to the "Need work" button
• Or at step 5, the focus should jump to the next GUI control in Tab order (in my case, the translations list)

Configuration

• poedit version Version 3.3.1 (6711), free version, French localization
• Windows 10 21H2 (AMD64) build 19044.2965, French localization

[vslavik]

(else, I'll provide more detailed steps)

Please do (as GitHub asked you to when you created this issue). You don't even spell out basics like Poedit version or your OS...

[CyrilleB79]

@vslavik, I have updated the initial description of my issue. Sorry for the initial lack of information.

Note that I do not seem to be asked for specific information when opening the issue in GitHub. I have finally found the SUPPORT.md file in the repo. Did I miss something? For better discoverability of these instructions, you may want to:

• Add a link to SUPPORT.md in the repo's README.md (which is the homepage of the repo).
• Use a GitHub issue template indicating the various information to provide and a link to the SUPORT.md file

[florianionascu7]

Hello! I'm here to confirm what Cyrille said. Please fix this accessibility bug.

[CyrilleB79]

@vslavik, sorry for disturbing. But is there a chance to have this issue fixed in a near future? Do you plan to work on this yourself or do you rather expect a volunteer contributor to work on it?

Or are you still expecting inputs from the reporter (i.e. myself)? If yes, let me know what please.