Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Scripting Enabled at Georgia Tech


Published on

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

Published in: Education, Technology, Design
  • Be the first to comment

Scripting Enabled at Georgia Tech

  1. 1. Christian Heilmann,, Georgia Tech, Autumn 2008
  2. 2. Hello, I am Chris.
  3. 3. I love the mashup and ethical hacking movement.
  4. 4. Barcamps, Hack Days, Mashups, Crowdsourcing, the social web.
  5. 5. Things that make me happy.
  6. 6. ... but I felt that it all became a bit stale.
  7. 7. We’ve been mashing things up nicely.
  8. 8. Many a photo has been placed on a map!
  9. 9. However, was that really something new?
  10. 10. HACKER!
  11. 11. John Snow helped the London authorities in 1854 to trace back the reason of cholera...
  12. 12. placing the deaths caused by cholera on a map and analyze the surroudings.
  13. 13. The answer: water supply!
  14. 14. Another example comes from advertising.
  15. 15. James Webb Young’s “A technique for producing ideas” is a book about coming up with new ideas...
  16. 16. ...presented in 1939 and published in 1965.
  17. 17. Amongst other things, he claims this to be about combining old elements.
  18. 18. Mashups are much more than just a technical feat.
  19. 19. Anything purely technical can be created by computers.
  20. 20. This is why we now have “mashup generators”...
  21. 21. ... effectively killing all creativity in the mashup camp.
  22. 22. Which makes developers that could still move and shake the market get bored and stop hacking.
  23. 23. This, to some degree happened to me.
  24. 24. {sad kitty}
  25. 25. I was wondering what you could do with the drive of the mashup community...
  26. 26. ...realizing that there is one part of web development that needs a strong, swift kick up the backside.
  27. 27. Accessibility
  28. 28. For years, I’ve been preaching and begging for people to consider disabilities when they develop.
  29. 29. The problem was first and foremost a lack of communication.
  30. 30. It is *very* easy to get bad and incomplete information about web accessibility.
  31. 31. The reason is that it is not sexy...
  32. 32. Publishers don’t really look for new books and people don’t bookmark and link blog posts.
  33. 33. We will change this tomorrow!
  34. 34. Webmaster Jam Session
  35. 35. People who work with people that need assistive technology are most of the time not geeks.
  36. 36. They are people people, not computer people.
  37. 37. Geeks on the other hand love everything.
  38. 38. They especially love shiny new technology.
  39. 39. So, there is a camp of people that are annoyed with the web as it doesn’t work the way it should...
  40. 40. ... and on the other hand there are people that are getting bored of it as they know all about it.
  41. 41. This was the gap to close.
  42. 42. The solution was YouTube.
  43. 43. At Accessibility 2.0 Antonia Hyde showed research results of how users with learning disabilities have problems using YouTube.
  44. 44. media-and-web-apps-for-people-with-learning- disabilities
  45. 45. Shortly before YouTube announced their API to build your own YouTube Player.
  46. 46. I took the API and Antonia’s findings and built EasyYouTube.
  47. 47. Screenshot of Easy YouTube
  48. 48. I put it online and asked for feedback...
  49. 49. The feedback was amazing!
  50. 50. So I did more...
  51. 51. Easy Flickr screenshot showing donkeys
  52. 52. I also used the YouTube API earlier to build easy captioning interfaces.
  53. 53. I also used the YouTube API earlier to build easy captioning interfaces.
  54. 54. Which inspired others to hack their annotations API:
  55. 55.
  56. 56. And again others to build a whole web app about it:
  57. 57.
  58. 58. This was going places.
  59. 59. Special needs driving innovation.
  60. 60. We had this before...
  61. 61. What inventions were created because of disabled users?
  62. 62. The speaker.
  63. 63. OCR Scanning
  64. 64. Remote Controls
  65. 65. All of these were great because they had input from people who need barriers removed.
  66. 66. Without this input, we build lesser successful solutions.
  67. 67. This is why I organized Scripting Enabled
  68. 68. On the 19th and 20th of September, around a 100 people listened to 6 speakers...
  69. 69. ... speakers with different barriers to the web or researchers that spoke for people with barriers.
  70. 70. On the second day about 30 hackers took these insights and built solutions that work around these barriers.
  71. 71. We now have presentations on the barriers faced by the blind, dyslexic, learning disabled, the impacts of MS and and and...
  72. 72. The videos of these talks are now being transcribed and will be online soon.
  73. 73. We have hacks working around these issues.
  74. 74. Easy Google Maps Reduce to the max Easy Audio Books Stylesheet Selector Accessible Editing ...
  75. 75. The energy at the event was amazing.
  76. 76. For *nearly 10 hours* we presented and discussed in Q&A sessions on day one.
  77. 77. Hackers didn’t bother with presenting and competing with their hacks from 4–5pm as intended...
  78. 78. ... but instead stayed till 7.30pm and kept hacking until we had to leave the building!
  79. 79. There was good blog coverage on all kind of personal and professional (BBC) blogs.
  80. 80. Some companies are right now taking the results and embedding them in their own systems (audio books).
  81. 81. The video player research is already in use in Yahoo video and I am helping drafting our API specifications.
  82. 82. There is more happening and available to you:
  83. 83.
  84. 84.
  85. 85. 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.
  86. 86. Screenshots of with and without JavaScript
  87. 87.
  88. 88.
  89. 89.
  90. 90.–05–18.javascript-karaoke-lyric-scroller.html
  91. 91. Screenshot of the JW Video Player
  92. 92. Screenshot of the JW player with captioning and audio description showing a scene from Coronation Street.
  93. 93.
  94. 94.
  95. 95.
  96. 96. What does the future hold?
  97. 97. I’ve come to realize that Scripting Enabled is a great concept.
  98. 98. I spent about 10 hours of planning and less money than the plane ticket to here on the event.
  99. 99. As I don’t have the time to run it wherever I want to, I opened the event up.
  100. 100. Anyone can run their own Scripting Enabled, if they follow these simple rules:
  101. 101. 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 is the source of truth – I want to know about events Use the social web to store the photos, slides and links
  102. 102. What about it?
  103. 103. Thanks! Chris Heilmann