With GWT, you can basically create any html structure you would like it to have by yourself. So it's not that hard to generate an accessibility act compliant webapplication.
What we did is hire an accessibility expert and have him define a fully compliant html with accompanying css.
His design encompassed all components that we are using (like table's, panels, li, tabpanels, popups, buttons etc etc..)
Our team then used GWT to have the components we need generate the html according to the designed html structure.
This also enabled us to use the same css as was defined. So now we can also outsource the css maintenance.
There were a few tuning issues (as expected), but now we (nearly) have a fully accessibility act compliant UI.
This was a little under 4 man month project. 2 months to get the accessibility expert up to speed and finish all components.
And 1-2 months to adapt the components we were already using to generating that html.
I'm not sure it is fair to expect the GWT project to generate fully compliant html.
The focus of GWT imo should be on the fact that you develop the UI in java, and have GWT compile java to working javascript.
That to me is the biggest USP and that should work flawlessly (as it always has).
What your application generates in html structure is up to you as user of GWT.
On Mon, Mar 24, 2025 at 9:56 PM <google-web-toolkit@googlegroups.com> wrote:
- GWT and European Accessibility Act - 2 Updates
Lonzak <tvtreeck@nepatec.de>: Mar 24 09:25AM -0700
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
Colin Alworth <colin@colinalworth.com>: Mar 24 09:32AM -0700
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:
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to google-web-toolkit+unsubscribe@googlegroups.com.
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/CABjQu7T6hz2%2B9mLwc2rtyacWb1QMOp6h7tvYz6K3uUcGzNN50Q%40mail.gmail.com.
No comments:
Post a Comment