® IBM Software Group © 2007 IBM Corporation Accessible Rich Internet Applications and Online Services Rich Schwerdtfeger IBM Distinguished Engineer, Chair W3C WAI PF ARIA Subteam First European e-accessibility Forum

IBM Software Group Web 2.0 Paradigm Shift in online services  Rich desktop-like experience through the browser  AJAX reduces page reloads  Tie UI to back-end services  Content aggregation from various resources (Mashups)  Social Collaboration  Potential for increased usability for all users  Static Documents  New Content = Page Reload  Navigation limited to tab and click  Poor Usability for PWDs News Ltd: “We’re allowing people to digest more information and faster, which I think is vitally important.”

IBM Software Group Online services moving to Rich Internet Applications (RIA)s Reduced server loads Easy upgrades and deployment Ubiquitous access to data Platform neutral desktop-like look and feel

IBM Software Group 4 Restrictive Accessibility legislation inadequate for today’s online services Geos require JavaScript and/or CSS disabled – Decisions based on 1999 browser technology Restrictions on pervasive RIA technology will leave people with disabilities behind New 508/WCAG 2.0 focus on – Interoperability, usability vs. technology exclusion – Harmonization between web and software Source: Security Space Technology Penetration Report Growth of RIA Based Technology vs. static HTML

IBM Software Group The Accessibility Problem is not CSS and JavaScript  Usability problems caused by limited HTML keyboard support  HTML and other markup does not provide adequate markup to support accessible dynamic content  “CSS and JavaScript accessibility problem” occurs when  JavaScript and CSS are used to create new UI constructs (menu, tabpanel, etc.)  HTML is repurposed causing interoperability problems with platform *Accessibility APIs  HTML keyboard focus issues require use of elements which effect tab order  The solution brings usable access of rich desktop applications to the Web *Accessibility API – Application Program Interface – How applications provide accessibility information to assistive technologies

IBM Software Group RIA Repurposed HTML lacks semantics and ability to give focus example: simlated pop-up menu  Accessibility Problems  Can’t get here effectively with the keyboard  Don’t know a menu has been activated  Usability poor as does not behave like a menu  Usability Problem extends beyond accessibility  Alternative content is expensive The “Rich Internet Application Accessibility Problem”

IBM Software Group Dependence on excessive tabbing makes keyboard access unusable  Accessibility/Usability Problems  Portal keyboard usability a problem  To get to Market report you need to tab through every link on the page  Alternatives are a hack to code sections as headers restricting UI or assign access keys  Alternative is inconsistent across web sites  Alternative provides little semantic information  Use of keyboard short cut (Access Key) introduces device dependencies Document Navigation Problem

IBM Software Group W3C Accessible Rich Internet Applications (ARIA) to the rescue Providing for accessible convergence of Rich Web And Rich Desktop ARIA Roadmap – Analysis/Plans to fill accessibility deficiencies – Full interoperability with assistive technologies – Accessible desktop-like look and feel ARIA Specifications – Role *GUI semantics – States GUI semantics – Form properties – AJAX live regions – Relationships – Sort properties – Role navigation landmarks – Fill keyboard gaps in (X)HTML (tabindex) Mapped to Accessibility API for ATVs role =“navigation” role=“main” <div tabindex=“-1” role = “wairole:menuitem” waistate:selected =“true”> *GUI – Graphical User Interface

IBM Software Group Demo

IBM Software Group 10 Where we are and what’s Hot! Making it real for developers and users  Reusable, Accessible Component Libraries ● Producing RIAs (Dojo, Rational JWL, Oracle) ● W3C has HTML implementation technique for XHTML standard  Recent Announcements  IBM *FSG donation of IAccessible2 for Windows with ARIA support  Second W3C Working Drafts of ARIA Specifications  Browser support  Firefox 1.5, partial spec.  Firefox 3.0 to support full spec. (Windows and Linux)  ARIA early ATV adopters support Firefox 1.5,2.0  Window-Eyes, JAWS 1.5/2.0, ZoomText  New Tooling ● University of Illinois Firefox Accessibility Extensions ● Model-based authoring tools ● IBM Research - RAVEN *FSG – Free Standards Group

® IBM Software Group © 2007 IBM Corporation Questions?

IBM Software Group References  W3C Roadmap and Standards   Examples      Tooling in development  U. of Illinois extension  RAVEN  WAI Role Taxonomy extension tool 