© 2007 IBM Corporation IBM Emerging Technologies Enabling an Accessible Web 2.0 Becky Gibson Web...

© 2007 IBM Corporation

IBM Emerging Technologies

Enabling an Accessible Web 2.0

Becky GibsonWeb Accessibility Architect

2


Enabling an Accessible Web 2.0 | May 2007 © 2007 IBM Corporation

Web 2.0 Overview Web 2.0 Accessibility Concerns Addressing Web 2.0 Accessibility

– Technologies

– Tooling

– Testing Demo Summary

Agenda

3



What is Web 2.0?

Dynamic– Incremental updates, multimedia

Interactive– Maps, web services

Collaborative– Wikis, blogs

– Crowdsourcing – http://www.istockphoto.com

– Collective intelligence

– Amazon Mechanical Turk - http://www.mturk.com/mturk/welcome– Digg - http://www.digg.com/news– del.icio.us - http://del.icio.us/

“Thus, mastery of architectures of participation to create real value will be essential to success in the Web of the future.” Dion Hinchcliffe

4



Google Maps

5



iStockPhoto

6



Web 2.0 Technologies

JavaScript CSS – Cascading Style Sheets Ajax – Asynchronous JavaScript and XML Multimedia

Change in Web Technology Usage

0

10

20

30

40

50

60

70

2001 2002 2003 2004 2005 2006 2007

% U

sa

ge

JavaScript

CSS

Iframes

Frames

7



Yahoo! – February 29, 2000

8



Yahoo! – May 2, 2007

9



AOL – February 29, 2000

10



AOL – May 2, 2007

11



Web 2.0 Accessibility Concerns

Rich Interface controls– Reliance on Mouse

– Lack of Semantics Incremental Updates via Ajax

– Unexpected / Unaware

– Unable to locate Changes in focus Excessive Navigation Multimedia

– Lack of captioning

– Interaction issues

12



Addressing Web 2.0 Accessibility

Updated Web Technologies– Accessible Rich Internet Applications (ARIA)

– IAccessible2 Development Tools

– Integrated Development Environments

– Toolkits Testing Tools

– Rule-based Accessibility Validation Environment (RAVEN)

– Functional Web Accessibility Evaluator (FAE) Assistive Technologies

13



Updated Web Technologies - ARIA

Allows creation of rich user interface components Full keyboard navigation Non-intrusive notification of updated content

14



Need for ARIA

Navigation– All components must be keyboard Accessible

– Remove reliance on tab key navigation

Notification of updated content

Assistive Technology (AT) Support– AT work via platform accessibility APIs

– Only basic HTML elements are supported– Scripted Web content is not supported

– Assistive Technology needs to:– Know active roles of scripted user interface components– Monitor states of scripted user interface components

15



ARIA Overview

Add role semantics to scripted user interface (UI) elements Update state information dynamically Make items focusable via tabindex attribute Add keyboard event handling

– Mimic the keyboard behavior of the rich client UI

– Minimize tab key navigation Add live region information and notification behavior* Extensible via RDF in future

*Live region support coming in Firefox 3

16



ARIA Support

Support for HTML and XHTML Implemented in Firefox 1.5 and later versions Supported by Window-Eyes and Jaws

– Window-Eyes 5.5 or later

– Partial support in JAWS 7.1, more in JAWS 8.0

17



ARIA Demo

Available at http://www.weba11y.com/AjaxDemo/sample.html

18



Updated Web Technologies – Accessibility APIs

Each platform has Accessibility API to communicate with AT– Accessibility ToolKit (ATK) for GNOME

– Java Accessibility API

– Microsoft Active Accessibility (MSAA) for Windows

– UI Automation for Vista MSAA created many years ago

– No access to advanced functionality

– ATs rely on off-screen models and private application APIs

19



Updated Web Technologies – IAccessible2

Extends MSAA to add missing functionality–rich text, tables, relations

–ARIA Live Regions Harmonizes with newer APIs of Java and Linux Interface donated to The Linux Foundation as

Open Standard Will be implemented in Firefox 3 Being integrated into Eclipse

20



Development Tools

Web Toolkits– Dojo

– Scriptaculous

– Prototype

– Google Web Toolkit (GWT)

– Yahoo! User Interface (YUI)

– More….. Integrated Development Environments

– Rational Web Developer

– Ajax Toolkit Framework

– More…..

21



Dojo

Open Source JavaScript Toolkit– “Easy” Ajax

– Data Binding

– Full event system

– Browser abstraction layer

– User Interface Widgets

– Dual Licensed– Academic Free License v2.1 – BSD License

22



Dojo 1.0 Core Widgets (Dijit)

Fully Accessible via ARIA Techniques Internationalized Standard Look and Feel Developer Documentation

– API– User Manual

Supported Browsers– Firefox 2.0– IE 6+– Safari (latest)

Data Binding– Tree, Grid, Select

23



Dojo Demo

24



Accessibility Testing Tools

Test against published standards Many tools evaluate the “over the wire” HTML

– Bobby from Watchfire

– WebKing from Parasoft

– More … Difficult to evaluate server side technologies Issues with dynamic Web 2.0 content Need more interactive solutions

25



RAVEN Rule-based Accessibility Validation ENvironment

Set of Eclipse plug-ins Originally developed for validating Java GUIs

– Java AWT and Swing

– Eclipse SWT Integrates accessibility testing into development environment Operates via an XML based set of rules Supports Validation of Dynamic HTML

– Uses IAccessible2 Being updated to support ARIA

26



Summary

Web 2.0 is dynamic and constantly evolving Accessibility of Web 2.0 is possible through

– Updated Technologies

– Toolkits and Development Environments

– Testing Tools

© 2007 IBM Corporation IBM Emerging Technologies Enabling an Accessible Web 2.0 Becky Gibson Web...

Documents

Transcript of © 2007 IBM Corporation IBM Emerging Technologies Enabling an Accessible Web 2.0 Becky Gibson Web...