On 17 août, 23:15, 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?
I'm not an accessibility expert, but isn't aria-hidden redundant with elt.style.display='none' ? isn't aria-disabled redundant with elt.disabled? isn't aria-checked redundant with elt.aria-checked? The same as AT already "infers" role from the HTML element (i.e. you don't need role=checkbox on an <input type=checkbox>,you get it "for free") See HTML5 which AFAIK specs the same as I'm saying (I'm not so sure for aria-hidden, and it might not be an exact match to display:none as set by UIObject.setVisible(), and in this case GWT would be right to not set aria-hidden there, leaving it to the developers): http://www.w3.org/TR/html5/content-models.html#annotations-for-assistive-technology-products-aria See also the Accessibility class to help you in setting ARIA role and states: http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/user/client/ui/Accessibility.html -- 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.
