Web 2.0 = Accessibility 2.0?

1,711 views

Published on

Web 2.0 = Accessibility 2.0? Presentation given at Missouri Power Up conference April 27, 2009 by Jared Smith of WebAIM.

Published in: Technology, Design
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,711
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
54
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide






















































































  • Web 2.0 = Accessibility 2.0?

    1. 1. Web 2.0 = Accessibility 2.0? Missouri Power Up 2009 http://webaim.org/presentations/2009/powerup Jared Smith webaim.org
    2. 2. What is Web 2.0?
    3. 3. static content vs dynamically updated content
    4. 4. new content requires page reloads vs new content now
    5. 5. links and buttons vs full desktop-like interactivity
    6. 6. save data on form submit vs save data anytime
    7. 7. traditional interactions vs non-traditional interactions (drag & drop, etc.)
    8. 8. Real-time content
    9. 9. Simplified interfaces Better visual design Higher usability
    10. 10. “Even if a website is highly usable and provides very useful information presented in a logical arrangement, this may fail to impress a user whose first impression of the site was negative.” Dr. Gitte Lindgaard Carleton University
    11. 11. Visual design is an important aspect of web accessibility!!1!
    12. 12. Reduce barriers to entry Which door is the men’s room?
    13. 13. Reduce barriers to entry
    14. 14. Reduce barriers to entry
    15. 15. ... but more cues are not always better
    16. 16. Advanced technologies and interactions
    17. 17. User-centric applications
    18. 18. Standards Compliance
    19. 19. Community and Social Networking
    20. 20. User-generated content
    21. 21. Mashups
    22. 22. Mashups
    23. 23. Mashups
    24. 24. Mashups
    25. 25. Mashups
    26. 26. Wikimapia
    27. 27. Wikimapia
    28. 28. Tagging of content
    29. 29. Content Aggregation
    30. 30. Content Aggregation
    31. 31. Content Aggregation
    32. 32. Social Media
    33. 33. Accessible Twitter http://accessibletwitter.com/
    34. 34. CAPTCHA
    35. 35. CAPTCHA Completely Automated Public Turing test to Confuse the Hell out of your Audience
    36. 36. Optimizing Tweets for Accessibility Use @replies, #hashtags, and dm’s • @username replies to that user - though others can still see it. • #hashtag provides a searchable keyword (e.g., #csun09) • dm username sends a direct message
    37. 37. Optimizing Tweets for Accessibility Provide context Jared Smith is presenting at Power Up vs. @jared_w_smith is presenting at Missouri Power Up Conference - http://at.mo.gov/powerup/ #powerup09 Provide context to @replies for those that follow only you.
    38. 38. Optimizing Tweets for Accessibility Use full URLs... unless you can’t http://webaim.org vs. http://is.gd/nRoE
    39. 39. Optimizing Tweets for Accessibility Be careful with abbreviations and language fwiw, I srsly <3 this kewl a11y pres. oktnxbai. This is unintelligible in a screen reader
    40. 40. There is no one way to use Twitter or any other social network. Find your own voice.
    41. 41. Glenda Watson Hyatt doitmyselfblog.com @GlendaWH
    42. 42. Web 2.0
    43. 43. • Content (preferably not crappy content) • Standards (semantic markup) Text • Users • Something to ‘glue’ it all together
    44. 44. AJAX “Asynchronous Javascript + XML” Jesse James Garrett February 2005
    45. 45. AJAX • HTML • JavaScript • CSS • XML • DOM • XMLHTTPRequest
    46. 46. Solutions http://www.flickr.com/photos/leadsoup/374510671/
    47. 47. Web 2.0 Accessibility ... it’s not rocket surgery!
    48. 48. Web 2.0 Accessibility
    49. 49. What is “Accessible”? To Whom? http://www.flickr.com/photos/pixelcore/32826662/
    50. 50. Content and Structure HTML
    51. 51. Presentation Styles
    52. 52. Behavior AJAX
    53. 53. Technology should enhance content AJAX Styles HTML CONTENT CONTENT
    54. 54. Progressive Enhancement AJAX Styles HTML
    55. 55. NOT Progressive Enhancement!
    56. 56. Progressive Enhancement Hijax • Plan for AJAX from the start. • Implement AJAX at the end.
    57. 57. AJAX Styles HTML Graceful Degradation
    58. 58. Ungraceful Degradation?
    59. 59. Progressive Enhancement AJAX AJAX Accessibility Styles HTML
    60. 60. Search Engines are blind
    61. 61. Where do we go from here? http://www.flickr.com/photos/csb13/184057163/
    62. 62. Web 2.0 = Accessibility 2.0?
    63. 63. Questions? <shameless plug=”true”> join the list attend the training check the forums get the newsletter buy the guide </shameless> Jared Smith @jared_w_smith

    ×