Semantic Order is inconsistent

[ABausG]

Bug report

The Semantic Order of elements is inconsisten.
Our setup is with a custom topBar and a trailingNavElement

By default it merges all Elements (Label from TopBar, trailingNavElement) Into the same semantic node as the "Bottom Sheet"
We'd like to keep the Title in that (works nicely) and are using a Semantics(contrainer: true, child: trailingAction) as the trailingNavElement which works as expected.
However this is where the inconsistencies are coming in when it comes to the order that elements are read out:

Some of our Modals perform the Screen Reader Order as desired:

1. ModalBarrier
2. BottomSheet. Title
3. trailingNavElement
4. Content

While others perform a different/wrong order:

1. Modal Barrier
2. BottomSheet. Title
3. Content
4. trailingNavElement

I am not sure why that is as the content/way we show the modals are identical and I could not yet find a way of recreating ones that would do it either way.

Steps to reproduce

As mentioned I can't find a reliable way of reproducing it as it is seemingly random when it decides to use which order (however it is consistent in which modals it has an issue)

It happens for both SliverWoltModalSheetPage and WoltModalSheetPage

Expected behavior

The Order is consistent and it reads out first all Navigation/Top Bar Elements regardless of them being merged or not

---

Additional context

Add any other context about the problem here.

---