We’re only seeing this on development builds. It does seem like it mostly happens early at the start of the client, so it is possible the windows message is coming through before the accessibility system has initialized.
I’ll try to add some additional logging so we can see what the order of operations here might be.