I’ve created an Accessibility toolkit for accessibility-related Twitter applications on the website OneForty, a great directory of Twitter-related apps. A “toolkit” is a collection of apps with a theme in common. There are only four apps listed in my toolkit so far, so I’d surely welcome any suggestions. Note that the app must be listed on OneForty to be included in a toolkit.
Category: twitter
A few nights ago, I submitted a comment to a recent article on Lifehacker, Navigate the New Twitter Like a Pro with Keyboard Shortcuts. My comment wasn’t approved. I also tweeted a reply about the article to @Scobleizer and Twitter employee @rsarver. Received no response there either.
The article to which I was responding glamorizes New Twitter’s keyboard shortcuts. I take offense to this so-called “feature” because the Twitter.com website itself is not accessible to users of keyboard-only input devices (which includes many types of assistive technology). And like all websites, Twitter.com should be accessible to anyone, not just to those who are able to use a mouse (device independence, see WCAG 2.0 Guideline 2.1). Does everyone see the irony here?!
So what my argument boils down to is this: if a website offers special keyboard shortcuts, it should first ensure that the it is fully keyboard accessible.
Here is my comment and Tweet below. Did I overreact?
Unapproved article comment:
This sickens me. Twitter isn’t keyboard accessible, period. Users of assistive technology can’t access the website. People who use a screenreader (visually impaired) or another type of keyboard-only input device (mobility impairments) are nearly completely blocked and makes Twitter.com useless. New Twitter is even worse than the old Twitter site. The so-called keyboard enhancements are an insult to those with disabilities. Fortunately, there is a web-based Twitter app that pays attention to everyone (and web standards, too). It’s called AccessibleTwitter.com.
My tweet reply:
.@Scobleizer Not valuable to users of keyboard-only devices; Twitter.com isn’t accessible to assistive tech. /cc @lifehacker @rsarver #a11y
- Bonus! An offer to the HTML5 team to save longdesc by Vlad Alexander at XStandard
- Landmark Technology Access Bill Heads to President Obama’s Desk
- Accessibility testing tools (Steve Faulkner, The Paciello Group)
- Response to HTML5 editor on Canvas accessibility (by Rich Schwerdtfeger)
- Adobe’s Andrew Kirkpatrick interviewed on Accessibility in Government (video)
- Accessibility for web writers, part 1: Introduction
- Assistive Technologies for Online Learning
- Web Accessibility day course by RNIB in Edinburgh (Oct) & London (Nov)
- Should Sighted Developers Use Screenreaders To Test Accessibility? (great comments!)
- Using Accessible Twitter With JAWS Screen Reader
- HTML5 Canvas Accessibility in Internet Explorer 9 by@stevefaulkner
- 20 Sites Assessed For Cognitive Web Accessibility
- Top 4 Reasons Why You Need to Address Web Accessibility
- WebAIM Aids eBay Accessibility Efforts
- Blind woman sues Canadian feds over online access
- Very entertaining video explaining closed captions (YouTube)
- Does your website legally need to be accessible? (U.S.)
- Web Design Guidelines for Low Bandwidth
- Web #Accessibility, Structured Negotiations & DOJ Rulemaking
- 10 Tools for Evaluating Web Design Accessibility
- WCAG 2.0 for Usability Specialists presentation (W3C) (April 2010)
- Facebook patent for ‘social CAPTCHA’ fails on accessibility
- Accessibility and the Law: How good UX can keep you out of court (U.S.)
- Raakt – The Ruby Accessibility Analysis Kit
As far as some accessible social media, here are my suggestions:
Twitter – Of course, use http://www.AccessibleTwitter.com
YouTube – http://icant.co.uk/easy-youtube/ OR http://tube.majestyc.net/
Facebook – http://m.facebook.com
LinkedIn – http://m.linkedin.com
MySpace – Nothing
Donate to Accessible Twitter
Accessible Twitter needs your help!