-
Enhancement
-
Resolution: Duplicate
-
P4
-
None
Hello.
I am a blind user of the computer.
We are able to use computers with screenreaders that talk to some accessibility interfaces that programs use to expose some data about their state.
In the java environment, we can use the javax.swing programs, but javax.swing has generic accessibility support, it does not have anything that connects to the native platform accessibility provider like msaa/uia on windows, it requires a bridge.
On the other hand, java fx is not accessible at all.
I would propose adding accessibility features to javafx.
I mean so that the controls can be made accessible, so that all builtin ones are by default accessible out of the box, and so that javafx links to the native platform accessibility thing.
On mac, i don't know what it is, on linux, it's atk or at-spi2 (more direct via dbus), on windows it's uia/msaa/something.
It would be really useful if it would not require any distinct bridge cause remembering to install any is annoying.
I am a blind user of the computer.
We are able to use computers with screenreaders that talk to some accessibility interfaces that programs use to expose some data about their state.
In the java environment, we can use the javax.swing programs, but javax.swing has generic accessibility support, it does not have anything that connects to the native platform accessibility provider like msaa/uia on windows, it requires a bridge.
On the other hand, java fx is not accessible at all.
I would propose adding accessibility features to javafx.
I mean so that the controls can be made accessible, so that all builtin ones are by default accessible out of the box, and so that javafx links to the native platform accessibility thing.
On mac, i don't know what it is, on linux, it's atk or at-spi2 (more direct via dbus), on windows it's uia/msaa/something.
It would be really useful if it would not require any distinct bridge cause remembering to install any is annoying.