PerkinsHacks: Solving real problems for real people
At Perkins School for the Blind, we are always on the lookout for new, innovative ways to address challenges faced by members of the blind community. And now, we want your help! Please join us at our first-ever hackathon, where you'll have the opportunity to solve real problems faced by real people with visual impairment at home, school, in the workplace and in the community.
Join our Slack ChannelHackathon Schedule
April 13, 2018 at 5:00 PM through April 14, 2018 at 6:30 PM at Perkins School for the Blind
$2,100 in prizes
Career in Coding Challenge Prize
Arduino Starter Kits (one per team member)
Finding a Seat Challenge Prize
Amazon Gift Cards (one per team member)
Privacy, Please! Challenge Prize
Fire TV Stick with Alexa Voice Remote (one per team member)
Making a Meal Challenge Prize
Google Home Mini (one per team member)
Going the Extra Mile Challenge Prize
FitBit Flex 2 for each team member
Large Sphero (one per team member)
Submitting to this hackathon could earn you:
All college undergraduate and graduate students are welcome to attend PerkinsHacks!
Teams (maximum team size of 5 members) will form around one of six challenges for the visually impaired. Prizes will be awarded for each challenge.
When submitting your hack, please include a good representation of your work. This could be a link to your code (Github, bitbucket), screenshots of the project or a video walking through how your project works.
Projects must be submitted by 3PM on April 14, 2018.
---------------------Rights to Work Results and Intellectual Property All work done by participant, including any intellectual property rights thereto, during the Hackathon shall be released for free to the community.
Olin College of Engineering
Solutions must be accessible to everyone, including the visually impaired. How was accessibility accounted for in your solution?
Does your solution do something entirely novel, or at least take a fresh approach to an old problem?
Is the hack usable in its current state? Is the user experience smooth? Does everything appear to work? Is it well designed?
How well was the project presented? Did it make the hack more compelling? Did it give a good idea of its purpose?
Is the hack technically interesting or difficult? Is it just some lipstick on an API, or were there real technical challenges to surmount?