STEM students - Beware, VoiceOver broke navigation in MathML content

Dear applevis community,
The following message is to make you aware of the worst bug in voiceover for STEM students. I've already mentioned this briefly in the macos sequoia beta topic.
If this bug was only on the macos 15 beta I wouldn't have worried too much, although macos accessibility team has already lost trust of many blind users of macos, but this is beyond the point.
I am a college student studying (as of writing) calculus 1, in Canada. I only asked my readaptation centre to adapt the graphs in braille, as the textbook is online and mathml/mathjax content is something I'm very comfortable with - well at least I was, on mac, and still am on windows.
We use Webwork like many other colleges and institutions to do the assignments. Webwork uses mathjax to render math content. Mathjax has the coolest feature ever, it allows us to copy whatever math content is under the cursor in latex format. I am sure you can understand why I like this feature so much as a blind user.
Anyways. So since June I've been reporting and trying the sequoia beta to prevent/prepare (this time) any horrible surprise voiceover could have for us in the stable releases like sonoma and its horrible caps lock mess (which was only partially resolved because sighted users complained as well). The scope of this bug and message is only about math content on the web with safari and chrome, not (yet) in native macos apps.
So basically how voiceover (generally used to work) with such content is the following: on a given mathml element, it would read it in its entirety with the prefix or suffix "math". Then the user would interact with the content, once, twice or 7 times (yes absolutely), and hopefully it could at some point try to navigate by small segments easier to digest. If that was mathjax on the webpage, the user could also do vo shift m, copy as sub menu, right arrow, and choose either mathml or latex (there is a 3rd option anotation but I don't know what it does as it's always been disabled for me). It works more or less the exact same way in safari and chrome, be it mathjax or mathml. Now, many could argue that the way voiceover was used to handel the navigation was already very very confusing to begin with, in versions like 14.5 and below. And you would be right.
BUT! Dear applevis, I was shocked to learn that, now, you can't navigate at all within math content on the web. When trying to interact voiceover says "text", and when you try to go further down within it and do vo left or right arrow at any given level, the cursor jumps at some random place close (or) not to the math content you're currently viewing. Now apparently apple needed to be in 2023 to finally include nemeth code for equation which was in ios for ages, in sonoma. This still seems to work, but I don't know for you but reading long equations, or reading anything at all, is way faster with speech, although I know numeth code so that isn't much of a problem, for me at least.
If this was only on sequoia, as I said earlier, I could have tollerated it in the beta cycle, it's a beta after all. But I don't know when it started, probably in the summer when I wasn't opening math related pages everyday, but this has slipped on sonoma 14.6.1, so even partitioning your disk won't prevent you to be hurt by voiceover neglect on macos.
Some other characteristics of the bug is that each time there are brackets [] or parentheses (), such as argument of a function or priority of operation in algebra, voiceover would read these once, then restart the reading just before, reread a second time, then continue, and so on... Furthermore, on safari, when there is a mathml table, aI noticed that on webwork with mathjax, it's impossible to navigate that menu after vo shift m and click copy as latex, I had to use chrome for that.
To Apple, suffize it to say that you've lost the remaining trust I was still giving to you. I thought I knew purchasing a good device when I bought my mac as your ios accessibility team is is so damn good, but I know better now. Your accessibility team on macos is now just a marketing bs, and blind users have an abusive relationship with their very expensive devices, despite countless feedback reported. On applevis, I am sure that there are more bugs discussed under macos and mac apps than under apple beta softwares, which tells a lot. I have 0 loyalty or trust on you from now on, and I doubt you'll ever regain that back.
I feel tired about all the accessibility bugs in macos. In my one year and 1.5 months with the mac I never felt as disabled than I did in this last year at college. Yesterday in that math class when I discovered this I had no other choice but change activity and tell the teacher that I'll be doing this exercises home on my windows laptop. I never felt so uncomfortable. Thanks to God though all of my teachers are very understanding.
Now because it's so damn difficult to coppy a feedback report I'll only post the feedback number, FB14922654. There is plenty of mathml content online and you can easily reproduce this bug, I was able to see it on my friend's macbook air m2. I have the base model m2pro 14inch.
Of course, ios voiceover is still as good as it was with math content.
Thanks all.