You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no documentation that I can find (or is it not visible to assistive technologies?) how accessibility with external tools is implemented? Specifically, how does a screen reader or other tool interact with a Java program ran through the CheerpJ JVM? Documentation states it implements a "full Java SE runtime", but I see no mention of how it exposes the Java Accessibility API, i.e. the equivalent to Java Access Bridge. The Accessible interface and related support seems implemented and works from Java code, but it is unclear how this is exposed to assistive technologies.
The text was updated successfully, but these errors were encountered:
CheerpJ provides the full Java SE runtime API, including the Accessibility API, as you have correctly pointed out.
The information coming from the Accessibility API is currently not interpreted and converted by CheerpJ to corresponding browser functionalities. This is unfortunate, but we cannot currently dedicate resources to implemented this feature.
CheerpJ is currently undergoing a full re-engineering in preparation for the next major release (CheerpJ 3.0), we may consider implementing this feature as part of this effort.
We’ll update this issue if there’s any movement on this front.
There is no documentation that I can find (or is it not visible to assistive technologies?) how accessibility with external tools is implemented? Specifically, how does a screen reader or other tool interact with a Java program ran through the CheerpJ JVM? Documentation states it implements a "full Java SE runtime", but I see no mention of how it exposes the Java Accessibility API, i.e. the equivalent to Java Access Bridge. The Accessible interface and related support seems implemented and works from Java code, but it is unclear how this is exposed to assistive technologies.
The text was updated successfully, but these errors were encountered: