Unable to Add a Turn Between Notes

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

There is currently no way to anchor a turn or other ornament between two notes. This means for all users it will not play correctly. But for screen readers there are a number of other issues around this.

1. The blind user can't shift the ornament into position for correct engraving using Shift arrow without risking it inadvertently ending up over the next note without realising.
2. there is no way for a screen reader to know the difference between a turn or other ornament placed above a note or one that someone has dragged between two notes.
3. When exporting to xml and on to Braille conversion there is no difference between the ornament placed above the note or one moved over graphically. These are handled differently in the Braille.
   Suggestion: Could there be another entry in the palette to select "Turn after the note" and the current one become "Turn above a note". Or if two notes are selected it adds the different turn between rather than above the first and plays differently. The screen reader would need to also read out "turn after " and "Turn above".

Steps to reproduce

1. Add a turn from the palette above any note.
2. Use Alt Right arrow to move on to the turn.
3. Press Shift + right arrow a couple of times to move the turn along between the notes. Note no feedback from screen reader.
4. Use alt left and then Alt right arrow to move off the turn and back on and note that the wording is no different than before the turn was moved.
5. Note also that the turn is spoken twice (as are most other ornaments) when arrowing, Alt arrowing and adding from the palette.
6. Move the focus to before the turn in the score and press space to play. Note the turn is performed as if it is above the note. I'm sure it is instantly obvious to all without steps that moving it has only moved it visually and for printing and has had no actual effect on the score.

Screenshots/Screen recordings

No response

MuseScore Version

4.1

Regression

I don't know

Operating system

Windows 10 with NVDA

Additional context

No response

Start by reproducing the turn behavior in MuseScore 4.1 using the palette, keyboard navigation, NVDA, playback, and XML export described in the issue. Investigate how turns are represented when moved between notes and how they are announced; done should distinguish above-note and between-note turns for screen readers, playback, and XML/Braille conversion.