An introductory explanation of scripting enabled and accessibility hacking i've given at Georgia Tech this morning

1. Christian Heilmann,, Georgia Tech, Autumn 2008

2. Hello, I am Chris.

4. I love the mashup and ethical
hacking movement.

5. Barcamps, Hack Days,
Mashups, Crowdsourcing, the
social web.

6. Things that make me happy.

8. ... but I felt that it all became
a bit stale.

9. We’ve been mashing things
up nicely.

10. Many a photo has been
placed on a map!

11. However, was that really
something new?

13. HACKER!
http://en.wikipedia.org/wiki/John_Snow_(physician)

14. John Snow helped the London
authorities in 1854 to trace
back the reason of cholera...

15. ...by placing the deaths
caused by cholera on a map
and analyze the surroudings.

17. The answer:
water supply!

18. Another example comes from
advertising.

19. James Webb Young’s
“A technique for producing
ideas”
is a book about coming up
with new ideas...

20. ...presented in 1939 and
published in 1965.

21. Amongst other things, he
claims this to be about
combining old elements.

22. Mashups are much more than
just a technical feat.

23. Anything purely technical can
be created by computers.

24. This is why we now have
“mashup generators”...

25. ... effectively killing all
creativity in the mashup
camp.

26. Which makes developers that
could still move and shake
the market get bored and
stop hacking.

27. This, to some degree
happened to me.

28. {sad kitty}

29. I was wondering what you
could do with the drive of the
mashup community...

30. ...realizing that there is one
part of web development that
needs a strong, swift kick up
the backside.

31. Accessibility

32. For years, I’ve been
preaching and begging for
people to consider disabilities
when they develop.

33. The problem was first and
foremost a lack of
communication.

34. It is *very* easy to get bad
and incomplete information
about web accessibility.

35. The reason is that it is not
sexy...

36. Publishers don’t really look
for new books and people
don’t bookmark and link blog
posts.

37. We will change this
tomorrow!

38. Webmaster
Jam
Session

39. People who work with people
that need assistive
technology are most of the
time not geeks.

40. They are people people, not
computer people.

41. Geeks on the other hand love
everything.

43. They especially love shiny
new technology.

44. So, there is a camp of people
that are annoyed with the
web as it doesn’t work the
way it should...

45. ... and on the other hand
there are people that are
getting bored of it as they
know all about it.

46. This was the gap to close.

47. The solution was YouTube.

49. At Accessibility 2.0 Antonia
Hyde showed research results
of how users with learning
disabilities have problems
using YouTube.

50. http://www.slideshare.net/hi.antonia/rich-
media-and-web-apps-for-people-with-learning-
disabilities

51. Shortly before YouTube
announced their API to build
your own YouTube Player.

52. I took the API and Antonia’s
findings and built
EasyYouTube.

53. Screenshot of Easy YouTube
http://icant.co.uk/easy-youtube/?http://
www.youtube.com/watch?v=vkdZmi85gxk

54. I put it online and asked for
feedback...

55. The feedback was amazing!

56. So I did more...

57. Easy Flickr screenshot
showing donkeys
http://icant.co.uk/easy-flickr/index.php?s=donkeys

58. I also used the YouTube API
earlier to build easy
captioning interfaces.

59. I also used the YouTube API
earlier to build easy
captioning interfaces.
http://icant.co.uk/sandbox/youtube-captioning.html

60. Which inspired others to hack
their annotations API:

61. http://www.nihilogic.dk/labs/youtubeannotations/

62. And again others to build a
whole web app about it:

63. http://www.tubecaption.com/watch?v=jpCPvHJ6p90&vcId=137

64. This was going places.

65. Special needs driving
innovation.

66. We had this before...

67. What inventions were
created because of disabled
users?

68. The speaker.

69. OCR Scanning

70. Remote Controls

71. All of these were great
because they had input from
people who need barriers
removed.

72. Without this input, we build
lesser successful solutions.

75. This is why I organized
Scripting Enabled

76. On the 19th and 20th of
September, around a 100
people listened to 6
speakers...

77. ... speakers with different
barriers to the web or
researchers that spoke for
people with barriers.

78. On the second day about 30
hackers took these insights
and built solutions that work
around these barriers.

79. We now have
presentations on the
barriers faced by the
blind, dyslexic,
learning disabled,
the impacts of MS
and and and...
http://scriptingenabled.org/presentations/

80. The videos of these talks are
now being transcribed and
will be online soon.

81. We have hacks working
around these issues.

82. Easy Google Maps
Reduce to the max
Easy Audio Books
Stylesheet Selector
Accessible Editing
...
http://scriptingenabed.pbwiki.com/

83. The energy at the event was
amazing.

84. For *nearly 10 hours* we
presented and discussed in
Q&A sessions on day one.

85. Hackers didn’t bother with
presenting and competing
with their hacks from 4–5pm
as intended...

86. ... but instead stayed till
7.30pm and kept hacking
until we had to leave the
building!

87. There was good blog
coverage on all kind of
personal and professional
(BBC) blogs.

88. Some companies are right
now taking the results and
embedding them in their own
systems (audio books).

89. The video player research is
already in use in Yahoo video
and I am helping drafting our
API specifications.

90. There is more happening and
available to you:

91. http://icanhaz.com/twitterwithlang

92. http://live.yahoo.com/

93. Yahoo live showing hard of
Using yahoo live a group of deaf people were
hearing peoplefor the first time. with
able to chat online chatting
another in sign language.
http://blog.deafread.com/abcohende/2008/02/15/yahoos-live-deaf-chat-room/

94. Screenshots of uk.video.yahoo.com with and
without JavaScript
http://uk.video.yahoo.com/

97. http://www.schillmania.com/projects/soundmanager2/

98. http://www.schillmania.com/projects/soundmanager2/

99. http://www.schillmania.com/projects/soundmanager2/

100. http://dt.in.th/2008–05–18.javascript-karaoke-lyric-scroller.html

101. Screenshot of the JW Video Player
http://www.jeroenwijering.com/?item=JW_FLV_Player

102. Screenshot of the JW player with
captioning and audio description
showing a scene from Coronation
Street.
http://www.jeroenwijering.com/?item=JW_FLV_Player

103. http://code.google.com/p/google-axsjax/

104. http://webvisum.com/

105. http://services.alphaworks.ibm.com/socialaccessibility/

106. What does the future hold?

107. I’ve come to realize that
Scripting Enabled is a great
concept.

108. I spent about 10 hours of
planning and less money than
the plane ticket to here on
the event.

109. As I don’t have the time to
run it wherever I want to, I
opened the event up.

110. Anyone can run their own
Scripting Enabled, if they
follow these simple rules:

111. It has to be free
It has to be a mix of information and
hacking around accessibility
Everything has to be released as CC
or Open Source
Scriptingenabled.org is the source of
truth – I want to know about events
Use the social web to store the
photos, slides and links
http://scriptingenabled.org/host-your-own-scripting-enabled/

112. What about it?

113. Thanks!
Chris Heilmann
http://scriptingenabled.org
http://wait-till-i.com