Skip to Content

Blind Access Journal Posts

Expand Your Independence and Work Around Inaccessibility: Join Aira for a Sept. 12 Conference Call

September 8, 2017 • Darrell Shandrow Hilliker

Michael Hingson, Aira’s Director of Strategic Sales, has asked us to distribute the following announcement regarding a conference call for blind people who may be interested in expanding their independence using Aira.

If you are looking for ways to deal with the inaccessible, real world, we hope you will take some time to attend the Sept. 12 conference call, contact us for answers to any additional questions you may have and sign up to start enjoying the benefits of remote sighted help on your schedule. Signing up through this link provides you and us a free month of Aira service, which helps you and our family.

Hello,

I am writing to invite you to a teleconference call on Tuesday, September 12, to introduce you to Aira. Perhaps you have heard of Aira or perhaps you have not yet heard of this incredible product.

We call Aira “a visual interpreter for blind and low vision persons”. With Aira anyone can accomplish tasks usually inaccessible to blind people because they require significant eye sight to perform them, more eye sight than we have ourselves.

So, what is Aira exactly? Aira is a product consisting of smart glasses with a tiny high-resolution video camera, an app on a smartphone, and a specially trained agent who describes the images seen by the glasses’ camera. To use Aira a blind person contacts Aira through the Aira app. When a request is made an agent is called by the smartphone while at the same time a video internet connection is established between the agent and the glasses. When the agent answers the call from the user, not only does the agent see what the camera transmits, but they also receive gps and Google map data showing where the user is and what is geographically around them.

Agents are specifically hired because they have an aptitude for describing and providing information as required. They go through special training and a rigorous battery of tests before they are permitted to accept calls and go to work. Aira agents do not help, but rather they provide information. If, for example, you use Aira while walking and you approach a street corner the Aira agent will not tell you when it is safe to cross the street. The agent can indicate it they see cars coming and they can tell you when the traffic light turns green for you. Aira does not replace canes, guide dogs or your travel skills. Instead, Aira enhances your toolbox of information gathering techniques.

People have used Aira to go shopping, travel through airports and malls, better perform household tasks such as identifying and preparing meals, putting on makeup, visiting places such as amusement parks and Arlington cemetery, assembling items and even running in the Boston Marathon. Aira is limited in what it can do only by your imagination.

If you want to learn more about Aira you are invited to attend a special teleconference call on Tuesday, September 12, 2017 at 2PM Hawaiian time, 5PM Pacific time, 6PM Mountain time, 7PM Central time, and 8PM Eastern time. To attend all you need to do is to dial in with the phone number (605) 468-8004, and enter the access code 329906# when the call is answered. During the conference, you will learn all you wish to know about Aira. We shall be conducting a live demonstration with an Aira agent assisting me, or at least describing to you what I am doing as well as helping me answer your questions.

Should you have questions you wish to ask me before the call please feel free to contact me directly at michael.hingson@aira.io and I will do my best to provide a timely response. This teleconference is intended to be an introduction to Aira and not a call for existing Aira users to discuss their thoughts. Such a forum already exists.

I hope to see you next Tuesday and I look forward to you joining the Aira family. Below my signature are some links you can click on to learn more about Aira. Thank you for your time.

Best regards,

Michael Hingson
Director of Strategic Sales

Never Say “No”: Expand Your TechVision with Dr. Denise Robinson

July 14, 2017 • Darrell Shandrow Hilliker

In this approximately 45-minute podcast, Allison, Allyssa and Darrell Hilliker talk with Dr. Denise Robinson all about her company, TechVision and her thoughts about the education of blind children and adults.

TechVision
Low-cost technology lessons for blind children and adults from a certified teacher of the visually impaired (TVI).
YouTube Channel
Watch videos showcasing the educational possibilities for blind children and adults.

We love hearing from our listeners! Please feel free to talk with us in the comments. What do you like? How could we make the show better? What topics would you like us to cover on future shows?

If you use Twitter, let’s get connected! Please follow Allison (@AlliTalk) and Darrell (@darrell).

Exploring the World with Aira: A Candid Discussion with Suman Kanuganti

July 13, 2017 • Darrell Shandrow Hilliker

In this approximately 50-minute informal podcast, Allison, Allyssa and Darrell Hilliker talk with Aira CEO Suman Kanuganti at the 2017 National Federation of the Blind Convention about this promising, new disruptive service that aims to give blind people “instant access to information” through the use of augmented reality and wearable technology.

We love hearing from our listeners! Please feel free to talk with us in the comments. What do you like? How could we make the show better? What topics would you like us to cover on future shows?

If you use Twitter, let’s get connected! Please follow Allison (@AlliTalk) and Darrell (@darrell).

Amateur Radio Field Day 2017

June 29, 2017 • Darrell Shandrow Hilliker

In this approximately 10-minute podcast, Darrell Hilliker demonstrates high-frequency (HF) amateur radio operation and thanks Gary (AC7R) and his crew for the chance to spend some time on the air during Field Day weekend.

We love hearing from our listeners! Please feel free to talk with us in the comments. What do you like? How could we make the show better? What topics would you like us to cover on future shows?

If you use Twitter, let’s get connected! Please follow Allison (@AlliTalk) and Darrell (@darrell).

Apple Considering Accessible On-screen Text and Described Videos at Future Events

June 12, 2017 • Darrell Shandrow Hilliker

After watching Apple’s June 5 WWDC keynote and listening to a summary of the event on Jonathan Mosen’s Blind Side Podcast, it dawned on me that we blind people are missing a lot of critical information!

Many of the videos played at Apple’s events lack sufficient dialogue to be comprehensible by a blind person without audio description, and there’s a lot of text displayed through on-screen slides that is never verbally mentioned by the presenters. On the Blind Side podcast, it was necessary for Jonathan’s sighted daughter to describe the videos and read the on-screen text in order for the blind podcasters to understand important details from the keynote, some of which may significantly impact those of us who rely on the company’s built-in accessibility.

On June 7, I decided to write the following note to Apple’s accessibility team asking that audio descriptions of on-screen text and videos be provided moving forward.

Hello Apple Accessibility Team,
While watching the WWDC keynote, I observed there was no way to hear audio descriptions of the on-screen slide content or the cool videos.
I have since learned about crucial accessibility improvements in software such as iOS 11 that were not verbally mentioned but were presented only through slides.
Have I missed something, or does Apple leave out this critical information?
In view of Mr. Cook’s declaration that accessibility is a “human right,” I am asking Apple to provide audio description of slides and videos during its events moving forward.
I look forward to hearing from someone on your team soon.
Thank you for your consideration.
Regards,
Darrell Hilliker
Accessibility Evangelist
BlindAccessJournal.com

I received the following same-day response from someone on the company’s accessibility team.

Hello Darrell,
Thank you for your email.  We appreciate the feedback and will pass this on to the appropriate people for their consideration.
Apple Accessibility

While the response was generic as corporate communications go, I am hopeful that the “appropriate people” will take this feedback from a loyal Apple customer seriously and that, moving forward, we will experience accessible on-screen text and described videos at future Apple events.

If you agree that Apple should, indeed, take care to fully include its customers and developers with disabilities by providing accessible on-screen text, audio description and closed captions, please add your voice to mine. Simply visit Apple’s Accessibility website and email the team.

In a World Ravaged by Inaccessibility, Aira Brings New Hope to the Blind Community

May 28, 2017 • Darrell Shandrow Hilliker

Do you cringe every time you think about that huge pile of print accumulating in your mail basket? Are you worried you might miss something important to your family or be forced to pay a late fee on a bill for the stupid reason that you missed the print notice that was mailed to you last month? How about all the cans in your pantry? Would you like to be more helpful to your child participating in recreational opportunities outside your home? Would you just like to receive sighted help on your schedule, rather than someone else’s?

Aira, the self-styled “Visual Interpreter for the Blind,” is here to help. Aira really is like OnStar for the blind! Simply open the Aira app on your smart phone, dawn the supplied glasses, press a few buttons and, voila! You have near-instant sighted help! Even better: they know what they’re doing!

It’s almost that simple. There are a few caveats:

  • Aira currently requires you to have a smart phone with a data plan and a decent level of knowledge about how to use it effectively.
  • With pricing starting at $89/month for the most basic plan, the cost is out of reach for most blind people.
  • Although Aira goes to extensive lengths to serve everyone in the United States, including providing a AT&T MiFi hotspot for the glasses, it remains limited by the availability of network infrastructure. Your smart phone must have a good signal to your carrier or you must connect it to WiFi in order to use the service.
  • You must be comfortable talking with people, patient with the need to aim your phone’s camera or turn your head and some prior experience working with sighted readers is helpful.
  • Using Aira is not the same as true accessibility. A sighted person is helping you work around a barrier that might otherwise exclude you or prevent you from enjoying the benefits of full participation.

If you can maneuver past these caveats, though, Aira is amazing!

In the week and a half since our family started using Aira, we have used it to help us:

  • Clean our refridgerator: An Aira agent read the expiration dates of numerous items so that Allison could decide what to throw out.
  • Settle the bill: Aira helped Darrell read a Cracker Barrel receipt so he could separate the items he purchased from those his mother bought.
  • Identify medication: Aira helped Allison read the labels on several pill bottles.
  • Go to baby school: Aira described the motions of the teacher and the overall scene to Darrell as he and Allyssa participated in a music therapy activity.

We know we haven’t even begun to touch the tip of the iceberg of possibilities. Last month, Aira helped a blind man run a marathon!

Although Aira is not perfect, they’re off to a great start. We are looking forward to Aira’s continued evolution as an important part of a blind person’s toolbox of alternative techniques, skills and technologies used to enjoy a full life on terms of equality with the sighted.

Are you using Aira? Would you like to learn more? Please feel free to tell us about it in the comments.

We love hearing from our readers! Please feel free to talk with us in the comments. What do you like? How could we make the blog better? What topics would you like us to cover in future articles?

If you use Twitter, let’s get connected! Please follow Allison (@AlliTalk) and Darrell (@darrell).

Teaching and Testing iOS App VoiceOver Accessibility Webinar

August 5, 2016 • Darrell Shandrow Hilliker

This approximately one-hour podcast is an audio recording of a real-world demonstration for following a systematic plan that explores, evaluates and tests iOS apps for accessibility with Apple’s built-in VoiceOver screen reader for blind and low-vision users. The August 3, 2016 webinar was presented by Darrell Hilliker and hosted by the Arizona Technology Access Program. A video, including closed captioning, is also available.

Teaching and Testing iOS App VoiceOver Accessibility Webinar Notes

Introduction

Webinar Purpose: introduce and demonstrate a step-by-step plan that provides a straightforward way for advocates, developers, educators and others to quickly explore, learn and improve the accessibility of all apps in Apple’s iOS ecosystem.

What is a Screen Reader?

  • A form of assistive technology
  • A Software program that turns information shown on a screen of a computer or mobile device into Braille or speech
  • Screen readers and accessibility enable blind people to learn, work and live in a technology-based world alongside sighted people.

VoiceOver

  • One type of screen reader that was created by Apple
  • Has been a built-in feature on all iOS devices since 2010
  • Enables Braille and speech access for users who are unable to see the screen
  • Speaks screen elements aloud or enables them to be displayed in braille

Accessibility

  • True accessibility means that all parts of a platform’s features, benefits, information, policies, procedures, products, responsibilities, rights, services and technologies are developed and implemented in ways that are usable by people with disabilities.
  • VoiceOver and other screen readers work best when apps are deliberately developed in ways that ensure compatibility.
  • Important for blind/VI individuals to be considered during development and included in the testing process.
  • Apple provides developers guidelines for making apps work with VoiceOver.

The Benefits of a Plan for Evaluating and Testing AppAccessibility

  • Advocates may use the plan to identify the accessibility issues they report to developers.
  • Developers may follow the plan to test their apps.
  • Decision makers may incorporate the plan into their user-acceptance testing and other procedures.
  • Educators may use the plan as a framework for evaluating the non-visual accessibility of iOS apps.

Starting VoiceOver

  1. Press the Home button on the iOS device. (round button located on the bottom middle of the screen)
  2. Tap Settings.
  3. Tap General.
  4. Tap Accessibility.
  5. Tap VoiceOver.
  6. Hold the VoiceOver switch and swipe to the right to turn it on.
  7. (Recommended) Hold the Speak Hints switch and swipe to the right to turn it on.
  8. (Optional) Triple tap the screen with three fingers to enable the Screen Curtain. This feature blanks out the screen, resulting in a more realistic environment for nonvisual accessibility testing.

Use Any of These Techniques To Activate VoiceOver Without Sight.

  • Press the Home button three times quickly. (Works if the Triple Click Home option in the iOS device’s accessibility settings is configured to use VoiceOver)
  • Hold down the Home button and ask Siri to “turn on VoiceOver”
  • Connect the iOS device to a computer running iTunes and turn on VoiceOver under the accessibility configuration screen.

The Plan

  1. Open the app to be tested.
  2. Tap the top of the screen with four fingers.
  3. Flick to the right through all elements on the app’s home screen.
    1. Are all controls labeled in a way that makes sense when you listen to VoiceOver without looking at the screen?
    2. Are you able to choose all buttons and other controls by double tapping them as you hear them spoken by VoiceOver?
    3. Does VoiceOver stay focused throughout use or does it become jumpy and read items out of order?
    4. When one or more items in a list is highlighted or selected, does VoiceOver say “selected” or provide any other indication of its status?
    5. If a list typically enables a sighted user to pull down with one finger, is a VoiceOver user able to update the list by swiping down with three fingers?
    6. Are all elements available to VoiceOver or are some items not spoken?
    7. Are there features that require the use of custom gestures that are not available to VoiceOver users?
    8. If visual cues, such as color, are important, does VoiceOver speak this information?
    9. Are all elements presented in a logical order as you move around the screen? If the relationship between elements is important, is it clearly conveyed nonvisually?
    10. Listen for special hints, such as “double tap to play,” spoken after the name of each element. If these hints are never heard, make sure hints are enabled in VoiceOver settings.
    11. If audio is playing, does its volume decrease, or duck down, while VoiceOver is speaking?
    12. Does a two-finger scrub (Z-shaped gesture) activate the escape function of the arrow in the upper-lefthand corner of the screen?
    13. Does the app offer accessibility enhancements such as direct touch, keyboard shortcuts, magic tap or specific support for Braille displays, switches or other forms of assistive technology?
  4. Flick to the left through the same home screen. Make detailed notes of anything that does not seem to function as expected with VoiceOver enabled.
  5. Tap the top of the screen with four fingers.
  6. Flick to the right, one element at a time, and double tap the first item where choosing it should lead to another screen.
  7. Repeat steps 3 through 5 on every screen the app contains, testing and noting any issues found with all elements.

Reporting and Resolving Accessibility Bugs

If you are a developer, using the notes obtained from testing, make all bug fixes necessary to deliver a fully accessible experience for users who rely on VoiceOver. Consider prioritizing the correction of accessibility bugs according to the order suggested in the plan. See the resources at the end of this presentation for details.

If you are reporting accessibility bugs to a developer, consider using the following format:

  • Description: A few concise words explaining the accessibility issue.
  • Steps to reproduce: Write down the exact steps you followed to cause the accessibility bug to happen.
  • Current behavior: Summarize the incorrect or unexpected behavior you are observing.
  • Expected behavior: Summarize the behavior you expect to observe once the accessibility issue has been resolved.
  • App and hardware information: Include a statement concisely providing as much information as possible about the version of the app being tested and the iOS device on which it is running.

Example Bug Report

The following accessibility bug was recently filed with Facebook against an important feature in the company’s iOS app.

Description: The details of event invitations are inaccessible to VoiceOver.

Steps to reproduce:

  1. Make sure VoiceOver is turned on in Settings > General > Accessibility > VoiceOver on the iOS device.
  2. Open the Facebook app.
  3. Open any event invitation.
  4. Tap the top of the screen with four fingers.
  5. Repeatedly flick to the right through the event invitation, pausing after each flick to listen to the information provided by VoiceOver.
  6. Note that important information, such as the event’s date, location, time and other details, are not spoken.

Current behavior: In its current implementation, event invitations are inaccessible and virtually useless to blind people using Facebook’s iOS app.

Expected behavior: Blind Facebook users should be able to access event invitations on terms of equality with their sighted friends.

Facebook version 60.0.0.37.141 is running on an iPhone 6 with iOS version 9.3.3.

Accessibility Testing

  • If you are a developer, check your work using blind alpha testers, followed by a select group of beta testers from the blind community.
  • If you are an advocate, thoroughly test the app according to the plan,then provide detailed feedback to its developer along with your accessibility request.
  • If you are an educator, test the app against this plan and any additional laws, policies or regulations your institution may have in place before recommending its use for your blind students.
  • If you are a decision maker, test the app against this plan and any additional laws, policies or regulations that apply to your agency, company, organization or personal conscience, then do not recommend or purchase the app if it is not accessible. Provide feedback about your decision to the company that owns the app.

Resources

We love hearing from our listeners! Please feel free to talk with us in the comments. What do you like? How could we make the show better? What topics would you like us to cover on future shows?

If you use Twitter, let’s get connected! Please follow Allison (@AlliTalk) and Darrell (@darrell).

Picture Imperfect: Our Family Explores Photo Management on iOS

August 2, 2016 • Darrell Shandrow Hilliker

In this approximately one hour and 49 minute podcast, Allison, Darrell and baby daughter Allyssa go on an adventure through their photo library, experiencing fun and frustration with accessible and inaccessible iOS apps.

We found Moments by Facebook completely inaccessible with VoiceOver. Please submit feedback to Facebook’s accessibility team.

We were looking for a good way to organize and store our family’s memories, photos and stories, not unlike sighted families the world over. We tried Keepy, on the recommendation of a parenting podcast we like, only to find it almost, but not quite, accessible enough to use. Please send customer feedback to the developer asking for improved VoiceOver accessibility.

On a positive accessibility note, we enjoyed adding descriptions to our photos using TapTapSee and BeSpecular. We appreciate the work the awesome BeSpecular volunteers do to help blind people see.

We love hearing from our listeners! Please feel free to talk with us in the comments. What do you like? How could we make the show better? What topics would you like us to cover on future shows?

If you use Twitter, let’s get connected! Please follow Allison (@AlliTalk) and Darrell (@darrell).

Inaccessibility in the Hospital: The Adventures of My Daughter’s Fourth Eye Surgery

May 20, 2016 • Darrell Shandrow Hilliker

My four-month-old daughter is sleeping, so, in belated celebration of Global Accessibility Awareness Day, I thought I would describe our experience with her fourth Glaucoma surgery from an accessibility point of view.

Before I get started, let me say that I think Phoenix Children’s Hospital always treats my daughter very well and provides her with excellent care. I also believe the staff at the hospital do the best they know how to make the experience as accessible and pleasant as possible.

Allison, Allyssa and I arrived at Phoenix Children’s Hospital one hour before Allyssa’s scheduled surgery start time of noon. As we have done with previous surgeries, we contacted the hospital’s Language Services department to request accessible, electronic copies of Allyssa’s discharge instructions and medical records. As has been the case for previous surgeries, we agreed to receive a secured email containing the discharge instructions prior to leaving the hospital, followed by the remaining records tomorrow.

In order to check our daughter in for surgery, I initialed and signed several pieces of paper, including consent, financial responsibility and health insurance documents, without fully reading their contents. The person at the front desk simply provided me a one- or two-sentence summary of each document. There wasn’t enough time to fully read each piece of paper.

A screen in the waiting room displayed the status of Allyssa’s surgery, without any alternative means of independently obtaining the same information.

When our daughter had recovered sufficiently to be discharged, an initial miscommunication almost resulted in our failure to receive the promised accessible instructions. It was difficult for the nurses to understand why we were insisting we could not simply wait until tomorrow to receive our discharge instructions from medical records. Advocacy and awkward conversations with supervisors were required in order to make sure we received the same instructions regularly afforded sighted patients without incident.

In this case, everything turned out fine. No service was denied, Allyssa recovered without incident and we went home with accessible, easy-to-read follow-up care information.

So, you may ask, why am I bothering to write about this incident if, in the scheme of all things inaccessible, this situation enjoyed a happy ending? I am doing so to point out the difference between accommodation and accessibility, and to suggest ways of implementing realistic solutions that value and serve the needs of everyone, including people with disabilities.

As things stand right now, when Phoenix Children’s Hospital receives an accessibility request like ours, it is handled through the Language Services department as an accommodation, similar to situations where a translator is needed in order to help someone who does not understand English. In that framework, my requests for universal accessibility are met with shrugs, because I appear to be asking for nothing less than a perpetual universal translator to automatically convert all printed materials into Braille on the fly. Obviously, I am not requesting such an unrealistic solution, but my inability to successfully communicate this fact to those who may be able to change things for the better means overall accessibility for all patients remains at a standstill.

So, now that we know what’s not wanted, what would represent a better solution that embraces true accessibility, rather than just slapping on another Band-Aid?

I am asking Phoenix Children’s Hospital to make the following changes in order to improve the accessibility of their services for everyone:

  • Insure all the hospital’s websites, including bill pay and patient portal, meet internationally-recognized accessibility standards such as WAI-ARIA and WCAG and undergo regular user-acceptance testing by a diverse group of stakeholders for ongoing accessibility.
  • Insure the secure email system is being operated by a vendor with a deliberate, publicly stated commitment to accessibility.
  • Implement techniques to create or generate all PDF documents in ways that meet Web Content Accessibility Guidelines (WCAG).
  • Provide accessible display screens and kiosks, or supply similarly proactive alternatives, such as smart phone apps and text messages, that work for everyone, including people with disabilities.
  • Enact clear policies and procedures for positively and proactively handling accessibility requests from employees, patients and the general public as appropriate.
  • Train staff to value accessibility and understand the difference between it and reasonably accommodating a request for a service such as language translation.

Asked to Make Your iOS App Accessible to Blind People? There’s a Plan for that!

May 14, 2016 • Darrell Shandrow Hilliker

Are you a developer who has been asked to make your iOS app accessible to blind people using Apple’s built-in VoiceOver screen reader? Are you uncertain how to respond, why you should care or where you can go to get started? I hope to demystify these questions and encourage you to create and improve your product in ways that empower and include all your customers, even those who can’t see the screens of their smart phones and tablets.

How should I respond to a request for VoiceOver accessibility in my app?

However you choose to respond, I would encourage you not to simply ignore the request. As a professional, you expect a timely response to communications you initiate, so please afford your blind customers that same courtesy when approached. Please consider the following ideas for communicating with users regarding accessibility requests:

  1. Respond to the request right away informing the customer you have received it and you will take steps to follow up promptly.
  2. If you have a bug-tracking or case management system, create a ticket and escalate it as needed in order to get an answer.
  3. If you do not possess the authority to make this strategic decision, please work with your company’s owner or executive leadership to urge them in the right direction. If you do have the necessary authority, please read on for information on how you can open your doors to your blind customers.
  4. If your business has decided to be inclusive to blind people, please respond affirmatively to your customer, utilize the resources provided here and elsewhere online and start working actively with the connected, online blind community.
  5. Regardless of the outcome, please remember to follow up with your customer by providing updates as you are able to release information to the public.

Why should I care?

There are at least four reasons why you should incorporate accessibility into your apps:

  • Accessibility is simply the right thing to do. Would you create an app designed to categorically exclude women, African-Americans, Chinese or any other group of people? If not, then why would you want to exclude blind people or anyone else with a disability? The answer to the accessibility question determines whether or not everyone, including people with disabilities, will be afforded the opportunity to learn, work, enjoy leisure activities or otherwise participate in the benefits your app offers.
  • There is a business case for accessibility.
  • Accessibility can be easy, fun and interesting. In 2015, the White House and several other U.S. government agencies sponsored a hackathon demonstrating and discussing techniques for improving the accessibility of several forms of technology.
  • Accessibility is the law of the land in many parts of the world. In the United States, the Americans with Disabilities Act, Individuals with Disabilities Education Act (IDEA), Sections 504 and 508 of the Rehabilitation Act, 21st Century Communications and Video Accessibility Act (CVAA), and numerous other lesser-known laws require accessibility and full inclusion of people with disabilities in activities, education, employment, products, programs and services offered to the public at large. Similar laws are on the books in many other nations. Failure to empower people with disabilities to use your app may result in complaints, lawsuits, loss of business, negative publicity and a poor reputation.

Where can I go to learn more about iOS accessibility and get started with developing my apps in an inclusive manner?

Apple provides an excellent overview of all the accessibility features available on its iOS platform. The Applevis online community hosts Information For Developers On How to Build Accessible iOS and Mac Apps. Finally, a comprehensive, systematic plan has been published to aid developers and others in beta testing and evaluating the accessibility of iOS apps with VoiceOver.