Tabbing can go to unselected Radio buttons

Issue type

Accessibility issue (e.g. for keyboard-only or screen reader users)

Description with steps to reproduce

In the New Score wizard, sub-dialogs for Time signature, it is possible to press Tab and land on unselected options. The norm is that in a group of radio buttons, the selected item in a group always receives focus when pressing Tab.

Steps:

1. From the File menu select New, or press Ctrl+N.
   The New Score wizard appears.
2. Choose instruments or select a template, then press Next to move to the second page. (NB: See other issue about Tab skipping over the Next button and users pressing Done not realising there is another page with further options.)
3. In the second page, press the Time signature button to open the sub-dialog.
   The Time signature sub-dialog appears.
4. Tab around to confirm default behaviour: 4/4 radio button checked, and the options for the numeric time signatures.
5. From the 4/4 radio button, Arrow Down to Common time and press Space.
   The Common time radio button is now selected - see other issue this is not reflected by speech or braille.
6. Now press Tab.
   Expected behaviour, nothing - except see other report about having OK/Close button as Esc is generally used to leave without saving changes.

Actual behaviour: Focus returns to the unselected 4/4 radio button and further pressing Tab does nothing. This gives the impression that the user is now stuck, potentially causing confusion. the only way out seems to be Esc making the user think they have not succeeded in editing that box.

Supporting files, videos and screenshots

N/A

What is the latest version of MuseScore Studio where this issue is present?

4.5.2

Regression

I was unable to check

Operating system

Windows 11 with NVDA

Additional context

No response

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible