Categories
Tags
- #devsummit
- answr
- Aspiration
- aspirationtech
- best practices
- blogs
- comments
- communication
- communications
- community
- custom
- dashboard
- development
- feedback
- feeds
- FLOSS
- listening
- message calendar
- netvibes
- nonprofit
- nptech
- online communications
- open source
- privacy
- profile
- publishing matrix
- rss
- security
- share
- Social Media
- social media dashboard
- social networking
- social source commons
- software
- spam
- story
- tool
- toolbox
- Tools
- tracking
- web 2.0
Blogroll
- I collaborate, e-collaborate, we collaborate
- Tech for Non-Profits
- Amy Sample Ward’s Version of NPTech
- Beth’s Blog
- Confessions of a Non-Profit Executive Director
- Daily Cup of Tech
- Groundwire
- Idealware
- IT|Redux
- Lifehacker
- NPTech Meta Feed 1.0
- Solution Watch
- Tech Soup
- The Agitator
- Zen and the art of Nonprofit Technology
Archives
- November 2014
- September 2014
- June 2014
- February 2014
- January 2014
- December 2013
- November 2013
- September 2013
- June 2013
- April 2013
- January 2013
- September 2012
- June 2012
- May 2012
- April 2012
- February 2012
- January 2012
- December 2011
- October 2011
- September 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- January 2008
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- May 2006
- April 2006
- November 2005

Social Media and Accessibility
We here at Social Source Commons Blog recently got an email asking us to reconsider our use of reCaptcha for spam management on our blog. reCAPTCHA is a tool that uses the CAPTCHA technique to verify that the person requesting to interact with the site (post a comment, register as a user, etc.) is, in fact, a human and not a spam robot (or “spambot”) looking for places to automatically insert links to Viagra resellers and porn sites.
It works by showing the user an image of a word usually slightly distorted but still readable. The idea here is that bots can’t interpret what’s shown on a picture the same way that humans can so while a human can see that the swirly picture says “following”, the bot just sees an image and can’t pull out the word that is being displayed because it isn’t actual text but rather an image of text. The user then types in the word that she sees in the picture thereby verifying herself as a legitimate human commenter or user. The CAPTCHA system works very well and as of right now (spambots are constantly becoming more effective), it is the go-to security measure for websites. Website administrators can let CAPTCHA catch spambots before they event submit content.
However, CAPTCHA has a big problem. What happens when the user trying to submit a comment is blind and accessing the internet with speech or other accessibility software? The software cannot read the image any better than the spambot so that the user cannot complete the puzzle and thereby verify their human commentor status. The user’s comment is denied even though the comment is valid and from a human. Even if the software was able to speak the CAPTCHA text aloud, this would still exclude those who are deaf-blind who access the internet with braille tools. (see The Equipment for Deafblind People Page for more info).
The person who alerted us to our blog’s default disabled discrimination asked that we reconsider using CAPTCHA programs like reCAPTCHA and instead focus on plug-ins that check comments for spamminess rather than ineffectively screen for humans.
We thought this was a valid concern and a valid alternative so we’ve stopped using reCAPTCHA and are going to see how our spam management and security are affected. Instead of reCAPTCHA, we are using Akismet which looks at comments’ content and searches for specific spam-related terms and users.
If we are to provide a place for Social Source Commons community and nonprofit tech conversations and information, then we need to address accessibility for all of our users as best we can.
What are your thoughts about spam management, security and accessibility? Many sites like Facebook and Twitter rely on CAPTCHA programs for spam security causing social media to discriminate against the disabled. Is there a solution (yet)? Or are those with visual and hearing impairments casualties of the war on spam?
Further Reading: