Maria et al, One of the big challenges is the fact that many assistive technologies, like screen readers, are still catching up in terms of their ability to communicate what is happening on RIA screens to users (e.g., partial content updates VS full page reloads). Also, keep in mind that a component of what makes a Web 2.0 application "rich," is the visual experience that it delivers, which in itself can pose challenges on the design/development side, when you are trying to figure out a non-visual means of communicating the same thing, such as when using a slider or gauge widget. Finally, while unintentional, Web 2.0 apps seem to lean toward mouse-driven interactions which do not always have keyboard equivalents available (e.g., fly-out menus, drag and drop).
Coincidental to this conversation, I have just set-up a group on LinkedIn for those who either already build Web 2.0 applications that take accessibility into account during development/testing or for those who are interested in learning more about what it takes to make these apps as accessible as possible. Part of what will hopefully make this group useful is that users with disabilities themselves are being encouraged to join in on the conversations. The URL for the group is http://www.linkedin.com/e/gis/1605077 Happy '09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=36539 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... disc...@ixda.org Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
