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

1. Web 2.0 = Accessibility 2.0?
Missouri Power Up 2009
http://webaim.org/presentations/2009/powerup
Jared Smith
webaim.org

2. What is Web 2.0?

3. static content
vs
dynamically updated content

4. new content requires page
reloads
vs
new content now

5. links and buttons
vs
full desktop-like interactivity

6. save data on form submit
vs
save data anytime

7. traditional interactions
vs
non-traditional interactions
(drag & drop, etc.)

8. Real-time content

9. Simplified interfaces
Better visual design
Higher usability

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. Visual design is an
important aspect of web
accessibility!!1!

12. Reduce barriers to entry
Which door is the men’s room?

13. Reduce barriers to entry

14. Reduce barriers to entry

15. ... but more cues are not
always better

17. Advanced technologies and interactions

20. User-centric applications

21. Standards Compliance

22. Community and Social Networking

23. User-generated content

24. Mashups

25. Mashups

26. Mashups

27. Mashups

28. Mashups

29. Wikimapia

30. Wikimapia

31. Tagging of content

32. Content Aggregation

56. Content Aggregation

57. Content Aggregation

58. Social Media

60. Accessible Twitter
http://accessibletwitter.com/

61. CAPTCHA

62. CAPTCHA
Completely Automated Public Turing
test to Confuse the Hell out of your Audience

63. 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

64. 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.

65. Optimizing Tweets for
Accessibility
Use full URLs... unless you can’t
http://webaim.org vs. http://is.gd/nRoE

66. 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

68. There is no one way to
use Twitter or any other
social network.
Find your own voice.

69. Glenda Watson Hyatt
doitmyselfblog.com
@GlendaWH

70. Web 2.0

71. • Content (preferably not crappy content)
• Standards (semantic markup)
Text
• Users
• Something to ‘glue’ it all
together

72. AJAX
“Asynchronous Javascript + XML”
Jesse James Garrett
February 2005

73. AJAX
• HTML
• JavaScript
• CSS
• XML
• DOM
• XMLHTTPRequest

74. Solutions
http://www.flickr.com/photos/leadsoup/374510671/

75. Web 2.0 Accessibility
... it’s not rocket surgery!

76. Web 2.0 Accessibility

77. What is “Accessible”?
To Whom?
http://www.flickr.com/photos/pixelcore/32826662/

78. Content and Structure
HTML

79. Presentation
Styles

80. Behavior
AJAX

81. Technology should enhance content
AJAX
Styles
HTML
CONTENT CONTENT

82. Progressive Enhancement
AJAX
Styles
HTML

83. NOT Progressive Enhancement!

84. Progressive Enhancement
Hijax
• Plan for AJAX from the start.
• Implement AJAX at the end.

85. AJAX
Styles
HTML
Graceful Degradation

86. Ungraceful Degradation?

87. Progressive Enhancement
AJAX
AJAX
Accessibility Styles
HTML

88. Search Engines are blind

89. Where do we go from here?
http://www.flickr.com/photos/csb13/184057163/

90. Web 2.0 = Accessibility 2.0?

91. 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