@zersiax @pixelate I'm really sorry that you all are running into that.
A couple of questions. Which distribution/version are you running? When you say that Orca is crashing, do you mean that it aborts and needs to be restarted, or is it only failing to read your app but responding to other applications? I think the latter would probably mean that WebKit isn't able to connect to the accessibility bus, so possibly an environment variable isn't being set/transferred properly (I assume it is inside a flatpak?) The former might mean a crash in AT-SPI. https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/219 is the one crash that I've seen reported recently, and I *think* that I fixed it in at-spi2-core 2.60.0 / 2.58.4 / 2.56.8. If you are, in fact, seeing a crash where Orca is aborting, then I would need to either be able to reproduce it or see a stack trace (if you don't know how to retrieve one, then I'll try to help).
@zersiax @pixelate I was looking through the commit log the other day and noticed one accessibility-related crash fix post-2.52.1 [1], but I don't know if it is your crash (I know of others). You could of course try filing a bug on bugs.webkit.org if you can get a stacktrace, but I don't think that the Linux accessibility code has been getting a lot of attention lately, and I have several other things on my list of things to do and don't have a lot of time to spend on it either right now. Sorry for not being more helpful.
@MikeGorse @pixelate @zersiax Oh I wanted to just cherrypick this fix on the top of the latest release and test if it fixes this particular case but it does not apply, actually there are more changes to accessibility since last release.
I will try if I can build webkit easily and verify this.
Here is history of commits inside the accessibility folder just out of curiosity: github.com/WebKit/WebKit/commi…