Accessibility Hackathon Project
Published on Thursday, November 10, 2011 - 11:38am
The following is a list of products that have been proposed to be built collaboratively as a part of an ongoing Accessibility Hackathon project at DC Public Library. The first event of this kind will be held on Saturday, Nov. 12, 2011, 10 a.m. to 5:30 p.m., in the Library Lab space and Room 215 at the Martin Luther King Jr. Memorial Library. Further events in the project will be announced on the calendar under Accessibility Hackathon.
Please send any comments or additional ideas to email@example.com.
Register for the first event at: http://accessibilityhackathon.eventbrite.com/
1. Lightweight version of Bookshare for BrailleNote users using the Bookshare API (http://developer.bookshare.org).
2. TTS Twitter client either using Chrome TTS APIs (http://code.google.com/chrome/extensions/tts.html). See example code at http://github.com/gcapiel/ChromeWebAppBookshareReader.
3. Searchable Repository of 508 Technology Guides. Jamal would contribute zip of content. Could be done in Drupal or Wordpress.
4. Mobile Accessible Book Generator -- Scan a book with your phone, type in, speech recognize or OCR the text, keep the images and output an RTF, DAISY 3 text (http://daisy.org), or EPUB version, which can be submitted to Bookshare and other repositories of accessible ebooks for people with print disabilities. This is particularly useful for children's books, which have few pages and words.
5. Mobile App that detects when the person in line in front of you has moved. One idea is to check when the iPhone camera comes out of focus.
6. Mobile color identifier that speaks a smaller set of colors (8 or 16?).
7. Accessible version of Tor.
8. Accessible fork of privacy tools at http://guardianproject.info using Android's Accessibility APIs.
9. Alphabetic keyboard for beginning level VoiceOver users. The QWERTY keyboard arrangement is a barrier for some users.
10. Facetime Audio description network.
11. Face-Name or Voice-Name recognition Quiz for social networks -- a system that would train the user to associate either images of a face or recordings of a voice with the name of the person they belong to.
12. VoiceOver Math Equations, Audio Description for Video Programming, instead of audio track, have metadata -- pause the screen and get an audio description, searchable.
13. App for movie description via iPhone, a collection of inaccessible material made accessible using a mobile accessible format conversion station.
14. Something that makes Twitter easier to read -- automatically read a stream of information to you, using live regions ARIA Web App, when a New Tweet comes in, it announces it automatically.
15. Are there any apps that desperately need to be made accessible?
16. Non-visual mind mapping app -- structure information present non-visual trees, branching tree nodes, windows explorer folders, nested folders, tree control http://www.informationtamers.com/WikIT/index.php?title=Mind_mapping_for_people_who_are_blind
17. An application that integrates with TheMashupApp, a powerful personal database that could work together with #4, #10, #18 and possibly others.
18. An application that makes audio description non-linear, with text to speech, from an educational point of view, tagged, with layers of information.
19. QR codes could be used to put in an app or provide info to the iPhone, add contacts to your iPhone, a QR code on movie ticket, push description to iPhone, embedded in clothing, various object, specialized information, walking directions, signs specialized info pushed to iPhone, tactile identification so you know where it is.
20. Any of various tasks that would help out the Adaptive Technology Program like making an accessible interface for Ustream where all the STTS audio and video is stored, captioning those videos, dragon-recognize Victor-Streamed interviews from the beginning of Accessibility Camp.
21. An accessible conferencing solution.
22. Create accessibility templates, wizards.
23. An iPhone app for Metro Access that shows the location of all vehicles.
24. Basic, accessible installation profiles for Drupal, JoomLa! or WordPress. Initial configuration settings, modules and themes would be selected to maximize accessibility. Documentation would be included that explains why each installation profile was built in the ways chosen. Results of testing on WCAG or ARIA guidelines would be included if possible.
26. Google shared docs and Facebook aren't very compatible with ZoomText. I'm told this is because they are "real time." Is there a fix for this?