That project (and other refactored modules) consist of code already present in gwt-user.jar, and is part of a larger effort to migrate away from JSNI and Generator to provide compatibility with J2CL. If you are continuing to use the GWT compiler, there is no direct impact right now, and no important push to migrate. The limiting work here is related to i18n, and is currently blocked by a lack of resources/time/funding to investigate how to improve closure-compiler's ability to optimize some GWT/J2CL code. From my own perspective, interest has somewhat waned in J2CL, so while I continue to be interested in completing this effort, improving GWT itself (newer Java language/sdk support, better optimized output, etc) is currently a higher priority for me and most of the users I interact with.
All of the same classes can be found in gwt-user.jar, see https://www.gwtproject.org/javadoc/latest/com/google/gwt/aria/client/package-summary.html and https://www.gwtproject.org/doc/latest/DevGuideA11y for more information. On Monday, March 24, 2025 at 11:25:58 AM UTC-5 Lonzak wrote: > The *European Accessibility Act* and its national counterparts are > immanent. So I would be interested in the measures you are taking to ensure > accessibility of your GWT UI. > > I just stumbled over the gwt ARIA project which seems a good starting > point: > > https://mvnrepository.com/artifact/org.gwtproject.aria/gwt-aria > > However the project is still RC2 (since 3 years) - any plans for a final > release? Or has it been surpassed by something else? > > Thanks for you input > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/2a02a341-bb09-492f-8411-ca1f2d7530a8n%40googlegroups.com.
