1. web 2.0 & universal desig n

2. Introduction From then to now Layers of change Accessible for whom? Web 2.0 and accessibility What is Universal Design? Looking to the future

3. 1. From then to now

4. 1989 - a vintage year Ted Henson releases JAWS (Job Access With Speech) Tim Berners-Lee’s original proposal for the web

5. Universality and accessibility "The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.” Tim Berners-Lee

6. WCAG 1 May, 1999 – WCAG 1 released Adopted widely

7. The modern web Inclusive/open Collaborative Interactive/Rich user experience New jargon (web 2.0, mashups) Rapid growth in online communities

8. Back to the future The accessibility message is slipping - we seem to be going backwards Hostility towards legislation of accessibility - “How dare they tell us we have to do this” Arguments in the web community - such as the Target, Flickr and CAPTCHA

9. 2. Layers of change

10. The PDF story 1993 – release of PDF 1 Moving to the Web Early PDF not accessible Accessibility gradually improves

11. The Flash story Demand for the “TV experience” 1996 - Macromedia release Flash 1 Poor accessibility 2002 - Flash MX and Player 6 released 2002 - JAWS 4.5 released (with MSAA support)

12. The AJAX story 2005 - Jesse James Garret introduces AJAX What is AJAX? AJAX inaccessible under WCAG1 2006 - JAWS 7.1 released with some support for AJAX 2008 - JAWS 8 released - better support

13. Stimulus and process Initial stimulus for PDF and Flash Improvements filter down Reflected in guidelines Process slow AJAX - process quick

14. About Pace layering Stuart Brand introduces “Pace Layering” in his book “How Buildings Learn” At the core level change happens slowly At the surface level change happens rapidly Change often causes tension and friction between layers

15. Pace layering - key elements Changes that happen at one layer filter down Differing rates of change cause friction between layers The different rates of change are beneficial "The fast parts learn, propose, and absorb shocks; the slow parts remember, integrate, and constrain. The fast parts get all the attention. The slow parts have all the power.” Steward Brand, The Long Now Foundation

16. Pace layering and the web When considering the question of Web 2.0 accessibility, we decided to take a Pace Layering look at the development of the web.

17. Pace layering and the web

18. AJAX and pace layering

23. Image replacement

25. 3. Accessibility for whom?

26. Web accessibility 1.0 Vision impairment to where?

27. Is Flash a valid tool? high impact visual websites can be accessible can also be used to present complex ideas in simple ways ideal for cognitive and learning difficulties –http://www.trans-active.org.uk/teenz/transit/index.htm –http://www.starfall.com/ very few websites in this area - why?

28. Dissin’ Flash Text and non-text alternatives Who’s afraid of Flash

29. Is Second Life accessible? Not for screen reader users How about people with other disabilities? Video

30. 4. Web 2.0 and accessibility

31. Web 2.0 accessibility Are we more inclusive than before? Is it getting easier?

32. Are we more inclusive? The web has become more inclusive in publishing - blogging, flickr, youtube, facebook, myspace But what about accessing this new content?

33. Is it getting easier? Should users or applications be responsible for accessibility? Ideally tools/applications should carry the burden Flickr default alt

34. 5. What is universal design?

35. The right model? Universality & Accessibility camps One-web?

36. One site doesn’t fit all Different disabilities – different audiences Text only Different presentation - same CONTENT Different content - same CONCEPT One site does not fit all

37. Ghettos or narrow- casting Ghettoisation Is “text-only” the way to go? The brain machine Narrow-casting

38. 6. Looking to the future

39. W3C and WAI Limited opportunities for participation WCAG 2 Last Call Draft (April 2006) What about people with cognitive and learning difficulties Baseline hostility – why?

40. Pace layering done right

45. Core driven change

47. ? ?

48. HTML5 Baseline

49. 7. Conclusion

50. Thank you