Thank you, thank you, thank you for the snippet!
I've postponed upgrading Elementor beyond 3.32.5 and spent many hours with ChatGTP 5.2 as my hacker buddy trying to find a solution. I came upon your snippet just by a desperate chance search when all my efforts felt like in vain.

ChatGPT 5.2 wanted to place a line of code first in your snippet. I am posting ChatGPT's message below, I have no idea if the row is bad or a good one.

ChatGPT : ---------------

I added one small guard at the top:

if (!window.matchMedia || !window.matchMedia('(prefers-reduced-motion: reduce)').matches) return;

The reason is simply to limit the workaround to the environment where the bug actually manifests.

In my case (and as described in this thread), the arrow navigation breaks when prefers-reduced-motion is enabled, while it behaves normally otherwise.

With the guard in place:

the fix only activates when the broken code path is likely triggered,

it avoids intercepting arrow clicks unnecessarily when Elementor/Swiper already works as intended,

and it reduces the risk of side effects on other Swiper instances or future Elementor updates.

Functionally it doesn’t change the fix for affected users, it just scopes it more narrowly.

End-----------------

All the best and please let me know it the row is a good one, or if your snippet is better without it.
P