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 Channel

Hackathon Schedule

 

PerkinsHacks 2018

April 13, 2018 at 5:00 PM through April 14, 2018 at 6:30 PM at Perkins School for the Blind

 

View full rules

Eligibility

All college undergraduate and graduate students are welcome to attend PerkinsHacks!

Requirements

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.

Judges

Greg Raiz

Greg Raiz
Raizlabs

David Ting

David Ting

Julian Aknin

Julian Aknin
Cooper Perkins

Paul Ruvolo

Paul Ruvolo
Olin College of Engineering

Jeremy Perkins

Jeremy Perkins
iFactory

Scott Mackie

Scott Mackie
athenahealth

Amanda Lange

Amanda Lange
Microsoft

Judging Criteria

  • Accessibility
    Solutions must be accessible to everyone, including the visually impaired. How was accessibility accounted for in your solution?
  • Originality
    Does your solution do something entirely novel, or at least take a fresh approach to an old problem?
  • Design
    Is the hack usable in its current state? Is the user experience smooth? Does everything appear to work? Is it well designed?
  • Pitch
    How well was the project presented? Did it make the hack more compelling? Did it give a good idea of its purpose?
  • Technical Difficulty
    Is the hack technically interesting or difficult? Is it just some lipstick on an API, or were there real technical challenges to surmount?