What's unexpected about that observation is that they have actually completely separated the presentation layer from the business logic because such a thing was required to have "Code with Me" and their "projector" project wherein one could use IJ from a browser https://jetbrains.github.io/projector-client/mkdocs/latest/a...
But, I am fully talking out of school because I don't know what the actual, no kidding, accessibility hurdles one faces when trying to do work in such a setup, nor what concessions VS Code has made to fix those problems
My major issue is that the IDE doesn't use the same hotkeys or similar interface to VS Code. This isn't necessarily a problem, but the fact that it's so different means the learning curve is absolutely brutal so it's not worth the effort for me to look at it. If there was a basic getting started tutorial that walked you through building a simple program, finding and fixing compilation errors, performing basic debugging etc, that was written from the perspective of a screen reader user that would be incredibly helpful. Something like this may exist, but if it does I haven't found it.
But, I am fully talking out of school because I don't know what the actual, no kidding, accessibility hurdles one faces when trying to do work in such a setup, nor what concessions VS Code has made to fix those problems
But I do know that YouTrack has a dedicated categorization for accessibility reports and I am sure they would welcome hearing about how they could win back those audiences https://youtrack.jetbrains.com/issues?q=%23%7BUI.%20Accessib...