Archive for the ‘social networking’ Category

Sticking On Labels: Making the GetGlue iOS App Accessible

Sunday, November 27th, 2011

In this approximately 45-minute podcast, Allison Hilliker and Darrell Shandrow use the new iOS 5 VoiceOver custom-labeling feature to make the GetGlue social-entertainment iOS app accessible. Join us to learn about an exciting, useful iOS feature and have some fun along the way.

Custom Labeling Step-By-Step

  1. Locate the unlabeled button by dragging your finger or flicking to it on the screen.
  2. Double tap with two fingers and hold them in place. This is also known as a two-finger double-tap-and-hold gesture. You will hear three tones followed by “Alert, label element, text field, is editing.”
  3. Type a short label for the button.
  4. Locate and double tap the Save button. It can be found above the keyboard on the left side of the screen.

In addition to making the controls in an app accessible, the custom-labeling feature can be used to describe pictures in other contexts, such as the photos in your iPhone’s camera roll.

Allison asked an excellent question: Are custom labels backed up to iCloud or iTunes? Please feel free to answer in the comments.

GetGlue Information

GetGlue is a Foursquare-like social network for entertainment. It is available on smartphones and the Web. You can check into your favorite books, movies, music, TV shows and much more and share information about all the fun you’re having with your friends. The primary GetGlue.com website works best with browsers like Chrome, Firefox, Internet Explorer or Safari on computers. The mobile m.getglue.com website is intended for use with smartphones. It may be a more accessible alternative to the primary site for some computer users.

Tip from Allison: I recommend signing up on the GetGlue website before logging in with the iOS app.

There are two ways to get started:

We’d Love To Hear From You!

Do you like the show? What would you like us to cover next? Please give us your feedback in the comments.

Listen or Pause – Custom Labeling Demo

Download – Custom Labeling Demo

Making a Difference by Thrusting Accessibility into the Public Sphere

Friday, January 7th, 2011

On Sunday, Nov. 14, 2010, Karen and I enjoyed a nice dinner meeting with Chronicle of Higher Education reporter Marc Parry in a nearby Applebee’s restaurant for an initial in-person interview as part of a story he was writing about technology accessibility for blind college students. Over the following Monday and Tuesday, Marc and I spent a great deal of time reviewing and testing the accessibility or inaccessibility of a number of college-related websites.

On Dec. 12, 2010, the Chronicle published an article entitled Blind Students Demand Access to Online Course Materials, in which my contributions were prominent.

The article highlighted significant accessibility barriers with ASU on Facebook, an application designed to help Arizona State University students connect in a virtual community. The app, developed by San Francisco-based Inigral, Inc., featured controls that couldn’t be accessed by keyboard navigation and images lacking text descriptions.

An Inigral representative contacted me within a few days of the publication of the article, saying she would be in the Phoenix area and asking if we could meet in person to discuss the situation. I agreed, a lunch meeting was scheduled then postponed that very morning till January due to family circumstances.

On Friday, Marc published After Chronicle Story, a Tech Company Improves Accessibility for Blind Users on the publication’s Wired Campus blog, stating that Inigral representatives met with the university’s Disability Resource Center and work is underway to improve the app’s accessibility.

After briefly reviewing the ASU on Facebook app as of Friday, Jan. 7, I can report that significant improvements have already been achieved. The “Go to App” link can now be followed using keyboard navigation, the website is more usable and I notice fewer images lacking descriptions.

Inigral’s co-founder, Joseph Sofaer, posted an accurate Jan. 4 article about the key elements of good website accessibility on the company’s blog.

The important point I hope readers will take away is that advocating for accessibility does make a difference. One more web-based application is now going to be accessible because a blind person agreed to be part of an article published in a widely-reade higher-education publication. It is critical for us to continue going after what we know is right: the equal accessibility that affords us the full participation we must have in order to learn, live and work in society as productive members alongside our sighted peers. This means we absolutely must pound the pavement. When we encounter an inaccessible app, piece of software or website, we *MUST* contact the company about it right away asking that it be corrected. If we don’t get timely responses, we need to follow up, escalating communications as far and as high in a company’s chain of command as they must go in order to get results. It’s a lot of hard work that can’t be done by one person, so I urge each and every one of you out there, whether you are a blind person or a sighted one who cares about us, to do your part by taking each and every possible opportunity to advocate, kick the ball out of the stadium, score the touchdown and win the game for the pro-accessibility team!

Accessible Instant Messaging iPhone App Hits the iTunes Store

Friday, August 13th, 2010

A highly-anticipated update to Shape Services’ popular IM+ iPhone app featuring comprehensive VoiceOver accessibility hit the iTunes Store Thursday.

According to its iTunes Store entry, the new version 4.30 of this app, renamed IM+ Pro, features “New themes and wallpapers, hi-res graphics for iPhone 4, full VoiceOver support, setting own display picture from iPhone 4 front camera, improved contact search and bug fixes.”

Blind high school senior Michael Hansen said he was delighted to learn of the accessible instant messaging option for his new iPhone.

“I use my iPhone mainly for various applications, messaging, and phone calls,” Hansen said. “I just found out about it this morning and I immediately purchased the app and tweeted to @implus to thank them for their work.”

He said IM+ Pro works better for him than other apps he has tried.

“I started out last week using Palringo, and I found that to be unsatisfactory because I could not log into Facebook and I could not read messages that were sent to me from AOL Instant Messenger,” Hansen said. “There went $4. I think that Apple should refund VoiceOver users if an app they purchased is not accessible. ”

He said IM+ works just fine with AIM, but he is having an accessibility problem connecting with Facebook.

“I have tried to connect to AOL Instant Messenger and Facebook; AIM worked fine, but Facebook did not,” Hansen said. “When I tried to add Facebook as a service, I got a message saying that I would have to tap the ‘Connect’ button to validate my information. However, I could not, for the life of me, find the ‘Connect’ button.”

He said he is confident the Facebook issue will be fixed quickly.

“I think that Shape Services has done the VoiceOver community a big service, and the Facebook connect button issue is a small bump in the road which I would imagine they could fix quickly,” Hansen said. “I just wish more app developers cared about accessibility—that’s the biggest problem with using an iPhone right now.”

Shape Services’ business development team official Natalia Kasyanova said the company has another nice surprise in store for blind users in the coming weeks.

“I would like to confirm that we are planning to release an IM+ Lite version with VoiceOver support by the end of August. It is a free adware version of IM+ which has the same functionality as IM+ Pro,” Kasyanova said. “We hope that it will make instant messaging even more available for blind users of iPhones and iPads.”

Let’s Ask Twitter to Enable Us to Moderate Follow Requests

Sunday, September 27th, 2009

Hard-working, honest Twitter users are getting sick and tired of all the bogus follow requests they receive on a daily basis as they post updates to Twitter. It seems there are automated computer programs, AKA bots, that search for interesting topics and try to follow everyone who tweets about them in hopes the favor will be reciprocated. Once the user follows the bogus Twitter account, their time line can be spammed with unwanted links to advertising and marketing from a strange company with an unknown reputation. What measures can we take now to protect ourselves and what can Twitter do to help?

Some people I know take a conservative, guarded approach to Twitter. These users protect their accounts. They may be followed only by request and their tweets may be viewed only by approved followers. Users in this camp restrict their followers to close friends and relatives, limiting their participation in all that Twitter has to offer. These users can’t be followed by others with a legitimate interest in the topics about which they tweet and are unable to meet new people. It would seem they lose out on most of the benefits of social media. While a portion of these users really do want a private Twitter experience, others feel the need to employ these measures as protection against spammers.

In contrast, other users wish to avail themselves of all the social media benefits Twitter offers, putting up with the junk in the process. They allow everyone to follow their public tweets and revel in the prospect of connecting and communicating with people they met online. The public profile of these users exposes them to phishing, spamming, social engineering and other forms of abuse. How can public users protect themselves while enjoying all of Twitter’s benefits?

There are currently a number of ways for public Twitter users to combat abuse, but all may require significant time and effort. How does one avoid unscrupulous users while ensuring they allow participation by those who have a legitimate interest in their tweets? While much of the abuse is perpetrated by bots, it seems the defense must be conducted manually, on a case-by-case basis as attacks are attempted.

Good protection seems to start at the point where a user makes a follow request. The requester is asking for permission to see your updates on their Twitter home page or in their Twitter application. Once the user follows you, he or she typically hopes you will return the favor in order to form a connection. When two Twitter users follow each other, a two-way relationship exists permitting the private exchange of direct messages and the public swapping of Twitter updates. The malicious user can abuse this new relationship by posting pushy marketing information to all their followers or by attempting to lure their followers to questionable Web sites that try to collect usernames, passwords and other personal data.

The key is to ensure you are only forming healthy relationships on Twitter by carefully evaluating each new follow request and keeping these guidelines in mind before approving anyone:

  • Check the Twitter username. If it contains several numbers after the name, this may represent a red flag. Proceed with caution. Bots can create accounts based on a name, adding numbers until an unused one has been found.
  • Look for nonsensical names or missing biographical information on the user’s Twitter home page. If you don’t like what you see, by all means ignore the follow request.
  • Consider taking a look at the Web site linked in the user’s profile. Exercise caution, though, as this link might point to a malicious page or an attempted social engineering attack. Do not trust the page’s content and avoid entering any personal data.
  • Review the updates the user has posted. You can quickly see the 20 most recent tweets on the user’s Twitter home page. Red flags include a large number of links without context, little or no conversation with other users and a lack of information you deem interesting.
  • If you believe the user is malicious, press the Block button. If you just find the user’s content uninteresting, simply ignore the follow request but do not block. Blocking can have a negative impact on a user’s reputation and may potentially limit their future ability to use Twitter.

We can ask Twitter to develop an easy solution that would allow us to strike a balance between the limitations inherent in a protected account and the anything-goes nature of a public account. The solution is moderated following. In a moderated following scenario, anyone making a follow request would be asked to explain why they should be granted that honor. The proposed feature would work like this:

  • A user wishes to follow someone on Twitter.
  • She visits the person’s Twitter home page and presses the Follow button.
  • She is asked to provide the reason she wishes to follow the other person.
  • Twitter notifies the recipient of the follow request, including the stated reason.
  • The recipient is given a chance to accept or reject the request.
  • If it is accepted, the requester receives appropriate notification. If denied, the requester receives nothing.

Let’s all think about how a moderated follow scenario might work and, if it’s something worth pursuing, ask Twitter to consider putting it in place as a new feature. All comments are appreciated as always.

Twitter Quietly Fixes Broken Audio CAPTCHA

Saturday, June 6th, 2009

A blind Internet user has reported that Twitter has corrected issues with its audio CAPTCHA during a one-hour Friday evening maintenance window. Blind Access Journal has confirmed the fix.

On August 22, 2007, Twitter implemented the ReCAPTCHA service to protect the site from abuse while granting a level of accessibility to blind and visually impaired people wishing to sign up for the new social networking service. The enhancement was implemented by Twitter in cooperation with members of the connected online blind community. Twitter received praise for this move.

On December 7, 2008, reCAPTCHA began deploying a new audio playback scheme. “Instead of using spoken digits or letters, our new audio CAPTCHA presents entire spoken sentences or phrases that the best speech recognition algorithms failed to recognize,” Luis von Ahn, the project’s executive producer, said on the reCAPTCHA Blog.

“For now, if you are using our custom theme option, we ask that you update the instructions for the audio CAPTCHA to say something along the lines of ‘type what you hear’”, von Ahn told web site developers who implemented reCAPTCHA, signifying the possible need to modify their sites in response to this change.

Reports began to surface of blind people locked out of Twitter’s account creation process. Investigating, Blind Access Journal opened the urgent support ticket 329388 with Twitter’s technical support team on May 28.

“Please resolve this because, as it stands right now, some people are being locked out solely because they’re blind / visually impaired,” Darrell Shandrow stated as part of the request for assistance.

On June 3, the support ticket was closed and removed with the statement “Twitter is a free service, and while we try to provide as much help as we can, we can’t get to every email”. A subsequent request for follow up went unanswered.

On Friday, Twitter underwent an evening maintenance window lasting approximately one hour. Shortly after, an update appeared on the Twitter Status site “The maintenance was successful and we are back up!”

Early Saturday morning, Mika Pyyhkala (pyyhkala) reported “the audio captcha for the Twitter sign up process has been fixed and works now!”

Twitter has made no statement regarding the audio CAPTCHA or any other issues that may have been resolved in Friday’s maintenance downtime.

“Unfortunately it was a very frustrating issue for a lot of people who couldn’t get beyond it,” said Larry Gassman (Lgsinger).

Easy Access to the Most Important Twitter Commands

Saturday, March 22nd, 2008

Mark Taylor has posted an easy to use list of Twitter commands in an accessible format on his Candle Shore Blog. We thank Mark for his contribution to the connected online blind community. Great job!

Visual Verification: Request of NFB to Officially Support CAPTCHA Accessibility Initiatives

Saturday, September 8th, 2007

The following letter was composed and sent to Dr. Marc Maurer, President, National Federation of the Blind, on July 28, 2007. It has been five weeks now. We continue to await a response from the organization concerning their official position and willingness to dedicate additional resources to these critical accessibility concerns.

July 28, 2007 

Dear Dr. Maurer:

My name is Darrell Shandrow.  You and I met a number of times at NFB national conventions and the National Center for the Blind.  I am an online accessibility evangelist, operating a blog known as Blind Access Journal.  It can be found at http://www.blindaccessjournal.com.  My purpose for writing this letter is to ask you to direct some of the resources of the National Federation of the Blind toward effectively advocating equal accessibility of CAPTCHA (visual verification) and other multifactor authentication systems for the blind and visually impaired.   

In CAPTCHA and some hardware based multifactor authentication schemes, a string of distorted characters is presented visually, and entry of those characters into an edit field is required in order to be granted access to a protected system.  The purpose of CAPTCHA is to differentiate between a script or other automated computer program designed to abuse a resource and a real human being who desires legitimate access.  Visual multifactor authentication schemes provide a second level of security beyond the traditional username and password.  Pictures can’t be interpreted or automatically conveyed using Braille or speech access devices and many hardware security keys still do not provide any alternative output mechanisms.  Until an accessible alternative is made available, people with vision loss can’t see the code to be entered into the box to be granted admission.  

There now exists a number of techniques to reasonably accomodate CAPTCHA and multifactor authentication for the blind and visually impaired.  The most commonly implemented accomodation is an audio CAPTCHA, where the characters in the image are audibly played back to the blind or visually impaired user for correct entry into the edit box.  America Online, Microsoft and PRWeb are examples of companies offering this form of accomodation.   

Another form of accomodation is a text based CAPTCHA.  In such a scheme, a user is asked to solve a simple logic or math problem or answer a basic question in order to be granted admission.  The Federal Emergency Management Agency (FEMA) is an example of an agency that uses such a text based solution.  Some technology experts say this solution is relatively easily cracked by computer programs, so it probably will not be widely implemented in its current form. 

  A third form of accomodation involves the need for manual human intervention on the part of the company requiring the CAPTCHA.  In such a scheme, the resource is protected with a visual CAPTCHA along with a link to click, an e-mail address to write a message or a telephone number to call.  The blind person clicks the link, writes the e-mail or calls the telephone number to receive assistance.  Unfortunately, this approach is fraught with serious challenges that make it completely unworkable in most cases where it is in use.  When a blind user fills out the form, writes the e-mail or calls the number, it is absolutely necessary that the request for help be fulfilled immediately in order for the solution to provide a level of access equal to that enjoyed by his or her sighted peers.  In almost all cases, such requests for assistance either go completely unanswered or are answered in an inappropriate time frame, perhaps days after the request is made.  Another serious problem is the actions taken once the requests are answered.  Are there specific processes in place for effectively delivering these reasonable accomodations?  Are all employees who may be taking the calls properly trained to follow the procedures?  It has been proven to us over and over that the unfortunate answer to both questions is a resounding “no”.  Though some companies are willing to offer these manual interventions as reasonable accomodations, it is clear that, in all cases we have experienced, they do not take seriously the promise to actually deliver the goods.  Examples of web sites supposedly offering the human intervention method of accomodation include GoDaddy.com, Slashdot.org, ticketmaster.com and Yahoo.com. 

Unfortunately, there still exist many web sites that do not offer any reasonable accomodations to their visual CAPTCHA at all.  Examples of sites in this camp include activate.sirius.com, friendster.com and myspace.com.  When a blind person does manage to find someone at these companies to contact, assistance is rarely, if ever, offered. 

At a bare minimum, visual only CAPTCHA locks blind people out of equal participation in web sites such as information portals and social networking resources.  More seriously, visual CAPTCHA without reasonable accomodation actually prevents blind people from completing business transactions, as in the CAPTCHAs on godaddy.com and ticketmaster.com.  Finally, visual only multifactor authentication schemes, such as security keys, can prevent blind people from accessing their money or even obtaining or retaining employment! 

I am writing to ask that you direct the National Federation of the Blind, as the largest consumer organization of the blind in the United States, to show clear leadership in advocacy for access to CAPTCHA and multifactor authentication.  In the short term, please officially support the Yahoo! Accessibility Improvement Petition at http://blindwebaccess.com and make higher level efforts to contact Yahoo! executives to discuss the need for a better CAPTCHA solution on Yahoo! web sites.  In the longer term, please consistently support existing grassroots advocacy efforts in this area and carry out new efforts on an organizational level to exercise influence and, possibly, legislation to address these serious concerns. 

Sincerely, 

Darrell Shandrow – Accessibility Evangelist

We thank the American Council of the Blind for joining us in support of the Yahoo! Accessibility Improvement Petition along with the organization’s willingness to consider taking on additional future efforts surrounding accessibility issues involving CAPTCHA and multifactor authentication. A cross-organizational approach to this and other critical access needs would serve to further these vital causes.

Visual Verification: Twitter Audio CAPTCHA Issues Likely Resolved – Please Retest

Sunday, September 2nd, 2007

The reCAPTCHA folks have been hard at work over this Labor Day weekend chasing down the issues with their audio CAPTCHA implementations in secured forms with Internet Explorer 7.0. Please retest the Twitter audio CAPTCHA and submit your feedback as soon as possible. Let’s also be sure to show our appreciation to the reCAPTCHA team for going far above and beyond the call of duty to resolve this critical issue over a holiday weekend!

Visual Verification: Trouble with Audio CAPTCHA on Twitter

Thursday, August 30th, 2007

We have received numerous reports from blind users who are unable to use Twitter’s audio CAPTCHA for the past several days. We ask as many of you as possible to visit Twitter, try the audio CAPTCHA and report your results in this ticket opened with Twitter’s customer support team. If you’re already signed into Twitter, it will be necessary to sign out in order to try the audio CAPTCHA again.

Visual Verification: Twitter Tears Down "No Blind People Allowed" Sign in Style!

Wednesday, August 22nd, 2007

The folks at Twitter have now added an audio CAPTCHA to their signup process, thus affording blind and visually impaired people the opportunity to register and participate alongside their sighted peers. See New: Accessible Captcha with Recaptcha for all the exciting details.