@miki @marco Ah, so it’s because the controls are being rendered inside the “sandbox” of a graphical output instead of native system controls being used? (Sorry for the layperson speak)

That’s disappointing, and seems like a big software design hurdle to shift from now, if they decide to do the right thing and support accessibility.

@miki Also, I wonder if this highlights the feat that @mitchellh has done with Ghostty, using native controls on different platforms. I hope that means Ghostty is able to support accessibility!

@mitchellh Glad to hear it is being addressed on macOS, and sad to hear the situation on Linux. I think I’ve seen @aral raising a stink over accessibility limitations over there.

Please prioritize shipping these 🙏🏻