I got the API url's from the wrong site. I'm using GWT 2.0 although I didn't take a deep look at the changes from 1.7
Yes, I also mixed Accessibility stuff with Validation stuff in the mail, my apologizes. I'd like my site to pass the validation but that's not a priority. My priority list is accessibility > usability > validation. Thanks for your responses 2010/3/25 Thomas Broyer <[email protected]> > > > On Mar 24, 11:05 am, enTropy Fragment <[email protected]> wrote: > > Hi! > > > > I am developing a web page that should be accesible. While working with > GWT > > I have discovered it is more focused in RIA than in creating standard and > > good code. It is so open and powerfull that it still makes sense (to me) > to > > keep working with it so I just wanted to share with you the best > practices I > > found and the problems I could not solve yet to create a completely > > acessible, valid and standard web. Would be nice to make this list grow > as > > there is almost no info about this on the Internet as far as I've found. > > > > - *Tables* - Almost all GWT Panels end up transformed in html tables, > > this shouldn't happen > > - Affects to: All Panels that extend > > *CellPanel< > http://www.asquare.net/gwt/javadoc/1.0.21/src-html/com/google/gwt/use...> > > Er, are you *really* looking at the javadoc and source for of GWT > 1.0.21 ??? > How about reading up-to-date things instead? e.g. http://gwt.google.com/ > > > *(this includes > > DockPanel< > http://www.asquare.net/gwt/javadoc/1.0.21/com/google/gwt/user/client/...> > > , HorizontalPanel< > http://www.asquare.net/gwt/javadoc/1.0.21/com/google/gwt/user/client/...> > > , VerticalPanel< > http://www.asquare.net/gwt/javadoc/1.0.21/com/google/gwt/user/client/...> > > ) > > AFAIK, at the time they were written that was the "easiest" solution > to have a reliable rendering in all/most browsers without resorting to > too much hacks. At that time, GWT wasn't at all "accessible" (it's > slightly better now, as some widgets now set the appropriate ARIA > role, such as PushButton, ToggleButton and CustomButton) > > > - Solution I found: Use other panels, for instance > > *FlowPanel*< > http://www.asquare.net/gwt/javadoc/1.0.21/src-html/com/google/gwt/use.. > .>(wich > > becomes an html div) + some css for each panel > > Yes, or layout panels as pointed by Kozura. > > > - *Missing html elements* - There are some elements that are quite > > important for creating an accessible web > > - Affects to: Ordered / Unordered lists. All the headings (tags > <h*>) > > - Solution I found: Either implement them or use > > *HTML*< > http://www.asquare.net/gwt/javadoc/1.0.21/src-html/com/google/gwt/use...> > > instead > > I'd rather use an HTMLPanel and/or UiBinder. But they're not required > for proper accessibility. AFAIK, Google Reader and GMail (among > others) are pretty "accessible" and they don't use lists and titles. > Appropriate ARIA roles and properties might be enough. > > > - *Missing TAG option* for > > *Image*< > http://www.asquare.net/gwt/javadoc/1.0.21/src-html/com/google/gwt/use...>- > > This is a mandatory attribute for html images. setTitle claims to be > the way > > but in the end it becomes a "title="something"" instead of > tag="something" > > so it doesn't work > > - Affects to: > > *Image< > http://www.asquare.net/gwt/javadoc/1.0.21/src-html/com/google/gwt/use...> > > * > > - Solution I found: none > > (supposing you mean "alt" rather than "tag") it's been added recently > though unfortunately was forgotten in the recent releases (will be in > the next one): > > http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/client/ui/Image.java#541 > > > - GWT adds script tags without a *type attribute*, wich prevents the > web > > pass the validation tests > > Which script elements are you talking about? > And the type attribute is no longer required in HTML (starting with > HTML5), as all browsers default to interpreting the script as > JavaScript in this case. > ...and validation is orthogonal to accessibility. > > > - GWT uses a *tabindex attribute* for the history iframe. This > attribute > > is not valid for html4.01 transitional so the web won't validate again > > same as above. validity != accessibility != usability. You don't want > your users to be able to "tab" to the hidden iframe, would you? > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
