My guess is the GWT team is fairly small, and not many people are screaming for full ARIA support.
If this was a critical feature to me, I'd probably start by reviewing the open issues for ARIA or ACCESSIBILITY: http://code.google.com/p/google-web-toolkit/issues/list?q=ARIA http://code.google.com/p/google-web-toolkit/issues/detail?id=4756 ...then vote for the ones you care about, enter new bug reports for problems you've noticed that don't seem to be covered already, and (if you're in a position to work on this), consider fixing issues that concern you and submitting them to the GWT team. http://code.google.com/webtoolkit/makinggwtbetter.html On Aug 17, 2:15 pm, Thad <[email protected]> wrote: > I'm disappointed with what I see, or rather DON'T see, in GWT 2.1.0M2 > regarding ARIA support. Granted the ARIA specification is moving very > fast, but there are many simple things that seem like no-brainers: > Why doesn't UIObject.setVisible() set the aria-hidden state? Why > doesn't FocusWidget.setEnabled() set the aria-disabled state? Why > doesn't CheckBox.setValue() set the aria-checked state? Are these > settings honestly not needed by common assistive technologies? > > What's being done? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
