Twitter Accessibility


Published on

"Twitter Accessibility" micro-presentation given at CSUN conference tweetup by Jared Smith of WebAIM

Published in: Technology, Design
  • Nice information about twitter..
    very interesting..

    Are you sure you want to  Yes  No
    Your message goes here
  • Thanks for sharing.
    Are you sure you want to  Yes  No
    Your message goes here
  • Jared, thanks for putting together these succinct comments. Many of them apply to programmers developing Twitter or related applications.

    As I tried to follow your suggestions in tweeting the presentation (@nancyf), I of course noticed that you had indeed used a URL shortener in your own tweet about it, and without one, I'm left with few available characters (slide 17).

    Another point that's within the user's control, avoiding the severe shortenings and unexpected abbreviations (slide 18), also gives us a challenge at being transparent and creative.
    Are you sure you want to  Yes  No
    Your message goes here
  • great points, Jared! especially the ones on providing context in tweets so people can follow you and how screen readers can't read twitter shorthand.
    Are you sure you want to  Yes  No
    Your message goes here
  • Great slides! And thanks for the link to!
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Twitter Accessibility

  1. 1. Twitter Accessibility Jared Smith @jared_w_smith
  2. 2. Use #csun09 hashtag in conference tweets Follow the tweets at
  3. 3. CAPTCHA Required for registration
  4. 4. CAPTCHA Completely Automated Public Turing test to Confuse the Hell out of your Audience
  5. 5. Inaccessible Buttons favorite (or ‘favourite’ for our Twittish friends), reply, and delete ‘buttons’ are not keyboard accessible
  6. 6. Inaccessible Buttons Focus Twitter Greasemonkey Script for Firefox places buttons in tab order - courtesy of Gez Lemon -
  7. 7. Accesskeys 15 accesskeys for all major site functions These are rarely used. They have potential to conflict with assistive technology.
  8. 8. Tabindex Most form elements are unnecessarily assigned tabindex. The default tab order is sufficient and tabindex can be omitted.
  9. 9. Document Structure Headings are used, but incorrectly structured
  10. 10. Alt Text A few images are missing alt text (profile images), have redundant alt text, or inappropriate alt text (alt=”Icon_lock”)
  11. 11. In general, is a classic case of web accessibility poorly implemented.
  12. 12. ...but it would be very easy to fix. It’s usable, but not optimal.
  13. 13. Twitter API The API allows development of fully accessible Twitter applications (though most aren’t) ...but you still must sign up at
  14. 14. Accessible Twitter
  15. 15. Optimizing Tweets for Accessibility Use @replies, #hashtags, and dm’s • @username replies to that user - though others can still see it. • #hashtag provides a searchable keyword (e.g., #csun09) • dm username sends a direct message
  16. 16. Optimizing Tweets for Accessibility Provide context Jared Smith is presenting at tweetup vs. @jared_w_smith is presenting at CSUN tweetup - #csun09 Provide context to @replies for those that follow only you.
  17. 17. Optimizing Tweets for Accessibility Use full URLs... unless you can’t vs.
  18. 18. Optimizing Tweets for Accessibility Be careful with abbreviations and language fwiw, I srsly <3 this kewl a11y tweetup. oktnxbai. This is unintelligible in a screen reader
  19. 19. Twitter Accessibility There’s not one right way to use Twitter, so make it your own
  20. 20. Twitter Accessibility Jared Smith @jared_w_smith