My favorites | Sign in
Google
Project hosting will be READ-ONLY Wednesday at 8am PST due to brief network maintenance.
                
New issue | Search
for
| Advanced search | Search tips
Issue 289: Add ARIA accessibility support
15 people starred this issue and may be notified of changes. Back to list
 
Reported by jon918, Oct 27, 2006
GWT Release: Any

Detailed description: The OOTB widgets should be section 508 compliant. IBM
is currently <a
href="http://dojotoolkit.org/pipermail/dojo-contributors/2006-August/003582.html"
>contributing accessibility support</a> to the Dojo toolkit. Will google
follow suit for the GWT?

Workaround if you have one:
We can develop this ourselves, but it would be nice to see this as part of
the framework (eventually!)

Links to the relevant GWT Developer Forum posts:

http://groups.google.com/group/Google-Web-Toolkit/browse_frm/thread/303e68fc3b77de52/5b44056e9ba6c6fc?lnk=gst&q=508&rnum=1#5b44056e9ba6c6fc
Comment 1 by gwt.team.vli, Nov 01, 2006

It seems unlikely that the current GWT rendering of widgets could be made accessible
according to WAI guidelines due to the frequent use of tables for layout. However,
one area to investigate is providing alternate set of "accessible" implementations of
standard GWT widgets that render a WAI compatible representation of the UI tree. Then
either the user could opt to "switch to accessible mode" or perhaps some kind of
browser detection could be used for accessible user agents. The rendered GWT
application might look ugly if viewed by a regular user, but might be much more
usable by screen readers.

I think the goal should not be to make any GWT application automatically accessible,
but to enable developers to write accessible applications if they wish. Since this
can be done today with desktop GUI widget libraries like MFC and Swing, it can
probably be done with GWT with changes. But there's no way around the fact that it's
a lot of work. Robert Hanson lays out a workaround technique which is essentially to
write a WAI compliant page/app first, and then wrap it in GWT.


Owner: gwt.team.ecc
Labels: -Type-Defect Type-Enhancement
Comment 2 by gwt.team.ecc, Nov 01, 2006
We would like to do more with accessibility in general; it is a very hard problem
with no perfect solutions. As we progress on tackling this problem, posts will be
added here.

Status: LongTerm
Comment 3 by jon918, Nov 02, 2006
Thanks for your comments -- I think you have triaged this issue appropriately. It is
worth noting that if you deal with the government or government contractors this can
often be the differentiator between one product and the next. I think the
requirements are only going to get more stringent. I think you guys should look at
what is going on with dojo to see what can be applied to GWT. I don't know all the
details, beyond that it looks like they are adding additional semantics to their tags
to allow screenreaders to know what to do with them -- something like "this <div> is
actually a tree node".
Comment 4 by gwt.team.ecc, Nov 15, 2006
(No comment was entered for this change.)
Owner: gwt.team.jgw
Comment 5 by gwt.team.morrildl, Feb 01, 2007
(No comment was entered for this change.)
Labels: -Priority-Medium Priority-Low Category-Other
Comment 6 by ispeters, Jun 01, 2007
Perhaps some accessibility features could be added to GWT in the nearer term. 
Firefox 1.5 and up supports certain screen readers by adding namespace-scoped
attributes to relevant nodes in a document.  See here for more details:
http://developer.mozilla.org/en/docs/ARIA:_Accessible_Rich_Internet_Applications
Comment 7 by gwt.team.jgw, Oct 26, 2007
I'm rescoping this issue slightly to deal specifically with the ARIA accessibility
standard. This is specifically designed for Ajax applications, and should work fine
with GWT. Plus Rajeev's already working on it :)
Summary: Add ARIA accessibility support
Status: Started
Owner: gwt.team.rdayal
Labels: -Priority-Low -Category-Other Priority-High Category-UI Milestone-1_5_RC
Comment 8 by gwt.team.jgw, Feb 20, 2008
(No comment was entered for this change.)
Status: ReviewPending
Comment 9 by jgw+personal@google.com, Apr 14, 2008
(No comment was entered for this change.)
Owner: rda...@google.com
Comment 10 by jgw+personal@google.com, Apr 17, 2008
(No comment was entered for this change.)
Status: FixedNotReleased
Comment 11 by scottb+legacy@google.com, Aug 13, 2008
1_5_RC has been released.
Status: Fixed
Sign in to add a comment