Disability Dialogue with Bill

Leverage Collective Intelligence, Accessible Digital Technology and Music: Creates Happiness and a Beautiful World

After listening to Gustavo Dudamel, who is a conductor of orchestras interview “Harmony In Times Of Crisis” on a local radio station, caused me to think about how his ideas could also positively assist with leveraging collective intelligence, accessibility and inclusion. Gustavo talked about how a person needs to utilize everybody’s unique skills and talents to get the best results. If you left any section or person out of the orchestra or anything you do it would result in a poor performance which would show up in the quality of  the work and more than likely the customer may not be happy.

When listening to the interview it reminded me of my blog post I wrote “Collective Intelligence: Include The Disabled for Success” that talks about digital technology (which is anything accessed by a computer or mobile device). If a person does not utilize and leverage everybody’s unique skills and differences the result will be a poor performance in any project they are doing. This is because the people you are working with do not truly represent your customers in the world that are a diverse population including people with disabilities. The result of your work would be as if an essential section was left out of an orchestra such as the violin, flute, piccolo, English horn, clarinet, bass clarinet, trumpet, French horn, Trombone, keyboard and others. Therefore, it would result in an orchestra that would not sound pleasant and the concert would be a failure instead of a widely diverse group of people working gracefully together to create astonishing results.

If you are a designer or developer of digital technology you could be preventing  some people from being able to participate in the orchestra of life if you do not incorporate accessibility and usability into the digital technology you are developing like I describe in my Collective Intelligence blog post.

During these times in our world we have plenty of things to be discouraged about therefor let us all be happy and make a beautiful world for all people as we harmonize and combine all peoples unique and different skills to create a loving orchestra of people with fewer barriers to inclusion.

Do you have any stories or examples to share regarding the benefits of allowing all people to equitably participate without accessibility barriers? Does anyone have any suggestions regarding how to educate people on the benefits of utilizing collective intelligence of people to resolve complicated issues or how to work better as a team?  Our world is an orchestra of diverse people including those with disabilities who participate in the orchestra to deliver beautiful music and create a  happy  and  a beautiful world. Do not place false barriers such as inaccessible digital technology in the way of creating joy and causing sadness and exclusions.

I look forward to hearing your comments to help us increase happiness in the world and not leave any instruments (people) out of the orchestra of life.

Bill Tipton

Contributing Author,

Global Dialogue Center

http://www.globaldialoguecenter.com/

LinkedIn: http://www.linkedin.com/in/wdtipton

Facebook: https://www.facebook.com/bill.tipton.39

Twitter: http://intercoms/wdtipton

How To Publish Photos /Images Even People Who Are Blind Can Visualize

Like myself some of you add photos / images to your social media posts with a goal that these images will provide enjoyment, attract or keep the attention of your followers or friends. One thing you may not be aware of if you do not take one extra relatively simple step to make the images you share accessible by adding alternative text some of your followers or friends will not know what the photo or image is. Alternative text provides a textual alternative to non-text content such as photos and images. Without taking the step of adding alternative text to your images people who are blind or visually impaired who use screen readers may feel left out since they will have no idea of what the image is.

Also finding an image without alternative text may cause your followers or friends who use screen readers to pause and wonder what they are missing in the image, thus distracting them from the desired text in the social media post. Sometimes the screen reader user even has to go back and attempt to reread the text understanding that on their second attempt they will need to skip through some images without alternative text while concentrating on the text they can read in-between the inaccessible content. Or even worse, some readers may give up attempting to read the message due to the accessibility issues in the content.

Fortunately, in most cases it only takes a few extra steps to add alternative text descriptions to make your photos and images accessible to people who are blind or visually impaired and use screen readers.

Alternative text descriptions should describe the image in as much detail as possible. However, they should also be concise to reduce the amount of text read by the screen reader. To best determine what alternative text description to use, just close your eyes and think about what you would want somebody to tell you to describe any image you cannot see enabling you to clearly visualize what the image looks like in your mind.

If your publishing software does not allow for adding alternative text directly in your publishing user interface it is possible you can incorporate HTML or ARIA directly in the code your publishing software published. For some suggestions refer to my two HTML examples below and for more details see the resource section.

If you are able to edit and view the HTML code, look for a line that says something similar to the example below:

<img src="filename.gif" alt="filename">

Replace the text in between the quotes after alt="with the alternative text description you want. For example, for the photo below I used “Bill wearing blue jeans, a red, black and gray flannel shirt, blue vest, sunglasses with support cane extended and long cane in pouch clipped to belt standing by lake at Grant Ranch Park with green rolling hills, trees, shrubs and a gray cloudy sky overhead”.

 

If the image or photo is decorative and adds no meaningful content add “” after alt =“”.

Although the suggestion described above is focused on HTML, these alternative text description concepts can assist for Facebook, Twitter and Yammer as well.

Below are some resources with details to help you add alternative text to images in Yammer, Twitter and Facebook. Also, there are tips to leverage HTML and ARIA if your publishing interface does not allow adding alternative text directly. Lastly, I have additional resources to help you learn more about alternative text and why it is so critical to help increase inclusion and decrease exclusion.

 

• How to add alternative text to images in Yammer
• How to add alternative text to images in Facebook
• How to add alternative text to images in Twitter
• WebAIM-Alternative Text
• WAI Web Accessibility Tutorials-Images Concepts
• WCAG WG-Using aria-labelledby to provide a text alternative for non-text content
• w3schools-HTML img alt Attribute

 

On the topic of alternative text descriptions does anyone have any other recommendations to help create a more inclusive environment for people who are unable to see the photos / images shared in social media?

Do any of you have suggestions on how to include everybody equally in our social media posts? Does anyone have tips to help increase inclusion for people with other disabilities besides blindness or low vision?

We all look forward to hearing your valuable comments and suggestions.

Bill Tipton

Contributing Author,

Global Dialogue Center

http://www.globaldialoguecenter.com/

LinkedIn: http://www.linkedin.com/in/wdtipton

Facebook: https://www.facebook.com/bill.tipton.39

Twitter: http://twitter.com/wdtipton

Reach Out to the disAbled for Assistance to Design and Develop an Intuitive and Accessible Application or Web Page

Are you responsible for the application or web page development cycle? Is one of your goals for it to be intuitive and accessible for everyone to use efficiently?  You could be designing or developing an enterprise application installed on a server accessed by a browser by anyone over the internet. Maybe you are designing or developing a consumer or an enterprise application installed on a computer, mobile device, or a web page. Or you may be deploying a digital service and have these same goals of equal access.

As part of your careful design and development process you may have implemented user interface (UI), User Experience design (UX), accessibility and usability techniques to help with this goal. 

One valuable resource you may have overlooked to assist is getting some guidance from people with disabilities. Since they may use a variety of assistive technologies, they could provide excellent feedback on User Experience (UX), User Interface (UI), usability as well as accessibility. To be sure you are evaluating for a broad range of assistive technology (AT) I suggest you at least have people evaluate with screen magnification, screen readers and voice recognition AT. Also people with disabilities have other unique and valuable skills that could be beneficial to your design.

Although other people with disabilities or challenges can assist just as well as I can, I will explain some skills a person who is blind may have that can relate to assisting with developing an organized and accessible user interface with some added accessibility tips.

Since I am completely blind it is helpful to keep track of things around the house and in my office. To assist with this goal I attempt to keep things in a familiar and organized location. This organization allows me to easily and quickly locate what I am looking for by utilizing landmarks by touch alone.

The way I locate things and get around in my physical world could be compared to designing a user interface in the digital world where all aspects of the application or web page are usable and accessible. This includes all user elements in the application or web page.

Some examples of user elements are hyperlinks, buttons, radio buttons, check boxes, drop down lists, form fields, navigational elements and additional user elements.  This design includes insuring text and all user elements has sufficient contrast in an organized well-designed user interface where all actions can be performed by a keyboard. This user experience design and development attention along with accessibility techniques will aid in creating a positive user experience to help prevent frustration and unintentionally excluding some users.

One example from the physical world might be how some people who are completely blind walk down a hallway. They could know when they reach the fifth doorway on the right side of the hallway from cane tapping, sound differences as they pass doors or if they use a guide dog.  If they have been in the room before they may know what the layout of the room is based on past experience. If you translate that to user interface design in the digital world you could think of each doorway as navigating down to the third heading level and know what is within that heading based on the text of that heading and the text of the second level heading.

Another way you can think about designing an effective user interface and creating a positive user experience is by being able to find your way around no matter where you are located within the application or webpage. For example from the physical world if I drop something on the floor and I hear it bounce or slide far away from where I am located I listen for it hit the floor. As it either bounces or slides across the floor I focus on where it stops making the noise to give me an idea of where it might be. I can then locate it by feeling navigational landmarks on the floor such as furniture to help me avoid obstacles and guide me to what I have dropped. This is similar to designing an effective user interface with key landmarks on it that will guide the user to sections, user controls, form fields or other user interaction types.  This design will help the user to intuitively use the application or web page successfully.

Another example from the physical world. Just think of a completely blind person attempting to walk alone without the aid of a long white cane or a guide dog in an unfamiliar area. Their chances of locating a glass of water they were told would be on one of the tall cabinets in one of the rooms could be difficult or time consuming.

If you label all like user element types the same throughout the application or webpage and have sufficient descriptive landmarks this will assist users in effectively knowing how to interact with the user elements and move around the user interface with ease.

In addition to the Design, Development and Accessibility Section further down I have a few accessibility and usability tips below. If I use HTML terminology please translate these to whatever coding language you are using.

• Insure every user element in your application or webpage is accessible by a keyboard because not everyone uses a mouse. Designing for keyboard accessibility not only helps the disabled who use specific types of assistive technology it also will help the keyboard only users who do not have a disability.
• Be sure all essential graphics have alternative description to enable the screen reader users to understand the complete content and interact with all user controls.
• Insure all hyperlinks describe the destination and are descriptive when reading out of context and none of them have duplicate names if the destination page is not the same.
• Be sure the tab order and on-screen focus is correct. When you use your tab key to navigate through the interface the focus should mirror the visual order of navigation, links and controls on the page with sufficient visual indication of focus. 
• Insure any tables are accessible by identifying the row and column headers and use captions if needed.
• Be sure all aspects of the application or web page have sufficient contrast to help all users.
• Insure like user controls are named the same within the same application or group of web pages that have the same topic to help the user from getting confused. Example: Do not use both buttons and hyperlinks if they both act like hyperlinks.
• Use headings and utilize other landmarks to assist with navigating the user interface to speed up navigation for all keyboard, voice recognition such as Dragon Naturally Speaking, and screen reader assistive technology users.
• The use of proper headings will not only help screen reader users, these will also assist keyboard only users and help with the structure and visual layout.
• Headings will also assist people who use voice recognition assistive technology such as Dragon Naturally Speaking (DNS) since some of the DNS users could speak the concise heading name to jump from heading to heading.
• Leverage proper semantics or the equivalent in your application or web page. If you cannot incorporate HTML in your application utilize the equivalent of semantic elements that are available in HTML in the specific technical requirements for your technology you are using to develop your application.  Also use semantic elements when developing webpages.  By leveraging semantics you can provide meaningful information regarding the user elements or page structure to the web browser thus to assistive technology users to assist them in using the product effectively.
• Developing a usable and accessible application or webpage does not only assist the disabled it helps everybody. For example you may have heard of people without any disability talking about an application or web page where they were so confused attempting to interact with it they had no way of intuitively knowing how to use it. This leads to extreme frustration and loss of valuable time.

After you complete your design and have a functioning product you are ready for your first pilot and to receive feedback. If you know of a person who uses assistive technology such as a screen reader, screen magnification or voice recognition ask them to try out your application or web page and provide their valuable feedback. If you do not know of anyone, contact a professional accessibility evaluation company to assist. You could also contact a non-profit organization related to people with disabilities and they may be able to get you connected with a person who can assist. In my opinion if they are located near you, you might even watch them use the application or web page in person over having them perform the evaluation remotely since this will benefit you in at least two ways.

• You will see any difficulties they may be experiencing first hand to allow you to resolve the issues in the next revision or better yet on the fly when you are with them.
• You will see a big grin on their face if you’ve developed and designed the application or webpage well and they can easily navigate it. I know personally I have a great big smile on my face if I am using an application or a webpage that is accessible, designed and functions well.

To learn about how people who are blind access information on their PCs or mobile devices read Understanding Assistive Technology: How Does a Blind Person use the Internet and How People Who Are Blind Can Orientate Themselves Using a Screen Reader.

Resources to Assist with Design, Development and Accessibility

User Interface Design Basics-Usability.gov

A Beginner’s Guide to User Experience (UX) Fundamentals-General Assembly

Web Content Accessibility Guidelines (WCAG) 2.1

Does anyone have any tips for User Interface designers, User Experience designers and developers for applications and web pages to help us design more effective applications or webpages that will result in a user friendly experience instead of a user unfriendly experience? Do you have any resources to share that will help us all in designing more effective and accessible user interfaces or techniques to design more intuitive and less cluttered user interfaces?

We all look forward to hearing your valuable thoughts, resources and any other information you want to share to help everyone to showcase talents equally and effectively without artificial limits.

Bill Tipton

Contributing Author,

Global Dialogue Center

http://www.globaldialoguecenter.com/

LinkedIn: http://www.linkedin.com/in/wdtipton

Facebook: https://www.facebook.com/bill.tipton.39

Twitter: http://twitter.com/wdtipton

Resolving Accessibility Barriers in Isolation: Achieve with Kindness

Are you older and have found using some technologies such as web pages, web applications, standalone applications on your mobile device or computer difficult to use if not impossible? Are you disabled and use assistive technology on your mobile device or computer and find using these same technologies not possible?  Do they not react the way you believe they should compared to similar technologies you have successfully used? Are you disabled or have short- or long-term challenges and do not use assistive technology and find using these same technologies difficult?

Although you may have never heard of usability or accessibility, these issues you are experiencing could be related to accessibility or usability.

If the designers and developers leverage the accessibility recommendations documented in the Web Content Accessibility Guidelines (WCAG) 2.1, Authoring Tool Accessibility Guidelines (ATAG) 2. and other guidelines/recommendations the accessibility issues you may have experienced could have been avoided.

If the technology owners are not aware of the positive Business Case for Digital Accessibility (Web Accessibility Initiative) WAI/W3C) they may find this resource beneficial to influence accessibility.

Have you experienced and reported accessibility obstacles and felt like you were working to resolve the issues in isolation? If you have felt or feel this way, I encourage you to never give up hope to not only to help yourself, but to assist the many other people who are experiencing the same barriers as you are. One or more of the many points below and others you find elsewhere may assist you at being successful at working on resolving accessibility issues with kindness.

• When contacting the product managers, designers and developers with kindness keep in mind, they may not have intentionally excluded any person. If you do find a person who has not heard of accessibility and does not understand it, explain how if they would have leveraged the documented techniques and requirements that are available some of the barriers encountered could have been avoided.
• After providing valuable accessibility education some developers may enjoy making the necessary modifications to incorporate accessibility and inclusion.
• Subsequently after receiving accessibility education some may also recognize the benefits of including accessibility in the upfront design and development plans to save time and money over retrofitting for accessibility after the technology has been released to customers and users start reporting the barriers preventing them from using the technology.
• During the process of resolving accessibility issues some owners may offer alternatives that may work to accomplish the task the person was attempting to do when they experienced the issue.  Although these suggestions may not be an efficient or effective solution and will take much longer for the end user to accomplish the task compared to if the technology was accessible.  
• Some may discourage you from doing what you need to accomplish to enhance your personal life or to advance your professional career instead of modifying the technology to incorporate accessibility.
• When someone discourages you from fully utilizing technology this may make you feel like you’re not worthy of participating in certain technology activities that other people who do not run into accessibility challenges are able to do anytime they feel like it without waiting for external assistance instead of implementing the needed accessibility technology enhancements.
• You may hear that it costs too much money to modify the technology after you submit your issue. Therefore, the owner may elect to sacrifice the ability for all people to use the technology over costs to retrofit the technology for accessibility. If you find you need to wait some time before they possibly address your issue keep in touch with the owner you took valuable time to locate and develop a positive relationship with as they incorporate accessibility in their next release.
• It is best to keep in touch from time to time with the person you reported the issue to since if you do not check in the enhancement request may drop off the enhancement list due to other priorities.
• When talking with some developers or others you may hear them say a person with a disability will never use my technology. You might also hear some developer say this hardware is locked up in a closet and only one person has access to it and that person does not have a disability therefore it does not need to be accessible. You may gently remind the developer it is possible that person who has access to the hardware may no longer be available and you may have another extremely qualified candidate to take over that job function who has a disability. Therefore, you would have been better prepared by making the hardware accessible to be ready for such personnel flexibility. Also, all the software to manage the hardware should be accessible since people anywhere in the world are able to access hardware over the Internet or Intranet using the latest technology.
• Some developers or others may tell you this technology is only for managers, scientists or other professions.  You may need to gently remind them that many people with disabilities hold a large variety of positions and are highly successful in their professions.  
• Subsequently after you communicate an issue you may hear back from the owner that this technology is not theirs and they procured it from an outside vendor. If you have a relationship with the person you contacted, they may be in a better position to influence accessibility enhancements on your behalf if this occurs.
• Although bullying or shaming people into making technology accessible may seem like a good short-term solution it is never ever a positive long-term solution for forming mutual exclusive valuable partnerships. At some point you may require their assistance again and if you did not treat them with respect and kindness in the past, they will be less likely to engage with you the next time you need them.   
• Be patient and listen as you educate the designers and developers regarding accessibility. Treat them with kindness, compassion and respect as you teach them about the technical aspects as well as the value of accessible technology to increase their customer base and customer satisfaction.
• I encourage you to not feel discouraged. Pursue ahead to help the product managers, designers and developers understand how they can improve their technology so it works for all people equally and not just certain people. Also remember it does take time to resolve accessibility issues once they are reported therefore be patient and understanding.
• Although at times you may feel frustrated and discouraged at your progress towards increasing accessibility, think about the countless others you are not aware of who do not have accessibility skills to resolve the issues themselves that you are helping to be more productive.
• Never stop partnering with others to increase accessibility with a kind and understanding attitude.
• At times during the process of resolving an accessibility issue you may feel discouraged, sad and tempted to give up. However, it is best to pursue ahead otherwise progress will not be made.
• If you submit an accessibility enhancement request and do not get a response or updates on progress do not be completely discouraged and feel as if you are resolving accessibility barriers in isolation. Although this is an example of poor customer service, it is possible the people you reported the issue to are making progress “in silence” without responding to you with an update.

Do you have any suggestions for people who are working on resolving accessibility issues in what seems like isolation? Do you have any tips for product managers, designers and developers to encourage them to work on accessibility in the design phase instead of waiting for users to become excluded from using the technology they develop? Do you have any tips to assist those who are new to accessibility so they feel more comfortable at providing accurate and actionable suggestions to developers in order to help them resolve any accessibility issue they report?

Also do you have any suggestions on how to help the user so they do not feel discouraged and frustrated when working on accessibility issues on what seems like their own?

We all look forward to hearing your valuable thoughts and comments to help increase accessibility thus enabling inclusion.

Bill Tipton

Contributing Author,

Global Dialogue Center

http://www.globaldialoguecenter.com/

LinkedIn: http://www.linkedin.com/in/wdtipton

Facebook: https://www.facebook.com/bill.tipton.39

Twitter: http://twitter.com/wdtipton

 

Lack of Awareness Can Result in Accessibility Obstacles

Has anyone ever heard discussions about people with disabilities not necessarily needing or requiring access to particular applications, web pages or documentation because they assume people with disabilities will never use them?

Or, maybe you have experienced people displaying a lack of awareness of what skills disabled people have to offer? Others may not be willing to fully utilize the valuable and unique skills people with disabilities have. Maybe that is because they are unaware of how effective assistive technology can be at levelling the playing field and assisting employees to be as effective as anyone not using assistive technology. Some uninformed people may assume no disabled person could be a people manager or a leader of others. Therefore, their thought process is that applications needed to perform that job function is not required to be accessible since no disabled person will use those particular applications, web pages or documentation. This thought process unfairly restricts promotional opportunities for the disabled.

It is also possible you may have heard someone tell a person with a disability that they do not need to use that application therefore it does not need to be made accessible. Perhaps you have also overheard the excuse that it is not likely a person with a disability who uses assistive technology is going to become a system administrator, therefor that function of the software does not need to be made accessible.

I know of people who are disabled and use assistive technology successfully who perform very technical roles. For example, database administrators, system administrators managing systems locally or remotely using software, application developers and scientists as well as others working in many other highly successful professional roles including managers.

To increase accessibility/usability I feel it is not beneficial to make assumptions on who will use a product. It is far easier to design and develop all applications, web pages and documentation to be accessible and usable to all people. This best practice will also save valuable time and money if a person reports an accessibility issue that requires the developer to immediately drop everything and retrofit the product for usability/accessibility after the product has already been designed, developed and released to the public.

Has anyone ever experienced any of the awareness or stereotypical challenges I talk about above regarding accessibility? Does anyone have any ideas of how to break the assumptions that people with disabilities should not be restricted to certain jobs or professions despite their education and skills?

Does anyone have any thoughts on the value of accessibility and the benefits of demonstrating inclusion and valuing all people equally? Has anyone experienced any positive examples regarding this topic that you might want to share? 

Lastly, does anyone have other tips or success stories to help educate us all on the benefits of fully utilizing the complete talents of people with disabilities instead of restricting their professional or personal progress?

We all look forward to hearing your valuable comments and tips.

Bill Tipton

Contributing Author,

Global Dialogue Center

https://www.globaldialoguecenter.com/

LinkedIn: https://www.linkedin.com/in/wdtipton

Facebook: https://www.facebook.com/bill.tipton.39

Twitter: https://twitter.com/wdtipton                

Documentation Accessibility: Consider Usability as Well

Are you a developer or designer of software (standalone or web based) and would like to develop a product to enable as many people to effectively use it successfully?  

To assist in increasing customer satisfaction do you develop your product to be as usable and accessible as possible? Do you follow and conform to such guidelines as the Web Content Accessibility Guidelines (WCAG) 2.1) and the Revised Section 508 standards and Section 255 of the Communications Act?  

You may also follow up by performing the necessary automated and manual accessibility evaluations enabling you to review the results of the evaluation reports and correct anything before going live. Since all accessibility evaluation reports you received were positive you felt comfortable everything was addressed to help insure your product was as accessible as possible. To help assure all users would be able to read your documentation you followed procedures on how to make your user documentation accessible such as the procedures in Make Your Word Documents Accessible - Office Support and Create and Verify PDF Accessibility - Adobe.

Since software may have many options and screens to interact with it and operate all controls, a clear, concise and accurate user documentation is required to learn the product. Also it may have a user interface that is not intuitive to a new user.  Because of this complexity without clear and correct user documentation a new user may not be able to teach themselves all aspects of the product, preventing them from using the software.

After all of the careful planning and your software product went live you received some feedback from a customer stating they could not use the software with a screen reader (assistive technology).  Receiving such a comment made you wonder what you may have missed in your vigilant plan to launch an accessible software product. Could it be the user documentation?  

Although I talk a little bit about usability for software this blog post focuses on documentation.

A Few Tips to Assist in Developing More Usable User Documentation:

• Follow all vendors’ procedures that describe how to develop accessible documents using the application used to develop the document.
• Insure the user documentation uses the exact words that are in the software user interface.
• Use the correct terminology for each user interface element contained in the software so it matches the documentation since some assistive technology like screen readers read these controls. A few examples are drop down menu, hyperlink, and button and...
• Do not use orientation words in the documentation such as “refer to the upper left-hand corner of the screen”. Screen reader users who are blind cannot easily reference within an application using spatial references with no text or user control element landmarks.
• Do not rely on color alone when providing guidance. Describe the text user interface controls in detail. A poor example is “Click on the red image”.
• After every software modification update the user documentation if the update changes the user interface or landmark words you used in the past versions.
• Not all users use a mouse therefore include all equivalent short cut keystrokes to perform all mouse tasks.  
• If alt attributes (alternative text) were used to specify an alternate text for images in the software, be sure the text that was used for the alt attribute matches the user documentation. This is especially important if an alt attribute happens to be on a user control.  
• Perform automated accessibility evaluations and manual evaluations following well designed scripts by people with disabilities who use a wide range of assistive technology.
• Get feedback from people with disabilities who use a wide range of assistive technology.
• Lastly, it is possible the software is accessible. However, without accurate and complete user documentation a user who uses assistive technology could get lost attempting to learn a new non-intuitive software product without accurate documentation designed for all users.

Although my short list is not inclusive, if one thinks about these tips they may assist in developing more usable and accessible user documentation. This will help users who use assistive technology to use the software effectively.

Since I am completely blind, use a screen reader plus have many years of experience in accessibility, often people ask my opinion on accessibility.  When a person asks me if a certain software application I have used is accessible sometimes I'm reluctant to answer because I do not have enough information to tell if it is accessible. This may be because I do not know how to use the software well enough since the user interface is complicated and not intuitive allowing me to learn without accurate user documentation. In these instances the user documentation may be the problem and not the software unless I immediately find obvious accessibility issues which even excellent user documentation cannot overcome.

When developing software it is extremely beneficial to incorporate accessibility in the design and developmental phase due to the expense of going back and retrofitting accessibility after it is developed and launched to the public. Plus, if it is launched with accessibility issues a developer may receive negative customer feedback which impacts customer relations. Developing accurate, accessible and usable user documentation is critical in completing the accessibility experience.

If you develop accurate and accessible documentation it may also help you from receiving comments regarding users stating they cannot use the software due to accessibility issues when the issue could be with the user documentation and not with the software. As I stated in my introduction to this topic this could have been the case why a screen reader user reported an accessibility issue preventing them from using the software just after the product went live.

Do you have any tips to help develop more accurate and usable user documentation? Would you like to share any success stories? Any other thoughts that come to mind that may help our conversation after reading this?

We all look forward to hearing your valuable thoughts and comments.

Bill Tipton

Contributing Author,

Global Dialogue Center

http://www.globaldialoguecenter.com/

LinkedIn: http://www.linkedin.com/in/wdtipton

Facebook: https://www.facebook.com/bill.tipton.39

Twitter: http://twitter.com/wdtipton

Increase and Promote Accessibility: Global Accessibility Awareness Day

 

May 17 was Global Accessibility Awareness Day. To celebrate the importance of accessibility I am humbled to share a blog post my employer wrote and published “Celebrating Global Accessibility Awareness Day” (Hewlett Packard Enterprise). This blog post contains a tip I provided to assist in increasing one component of accessibility. This also describes some of the work I do for my employer and the importance of accessibility.

• What did you learn from the blog post?
• If you recognize  Global Accessibility Awareness Day, how do you plan to celebrate this in 2019?
• How do you plan to increase accessibility in the work place to help employees who use assistive technology to be as productive as they can be and overcome barriers that in most cases can easily be resolved?
• Any suggestions for on-line course developers to assist them in developing courses everyone can complete without assistance, even people with disabilities?
• Do you have any tips for web developers to help them increase accessibility and usability to enable equal access for all?
• Can you suggest some ideas to increase usability and accessibility in services and products to help   increase customer satisfaction and loyalty?

We all look forward to hearing your valuable thoughts and comments.

Bill Tipton

Contributing Author,

Global Dialogue Center

http://www.globaldialoguecenter.com/

LinkedIn: http://www.linkedin.com/in/wdtipton

Facebook: https://www.facebook.com/bill.tipton.39

Twitter: http://twitter.com/wdtipton

 

 

Attending the American Foundation for the Blind Leadership Conference and Helen Keller Achievement Awards Ceremony

My wife Kathy and I had an enjoyable time attending the American Foundation for the Blind Leadership Conference and Helen Keller Achievement Award ceremony and Gala in Oakland California this April.

 

You can read about the last time we attended the Helen Keller Achievement Awards ceremony in New York City in my blog post I did “Helen Keller Achievement Awards & Exploring NYC without Eyesight”.

I enjoyed attending the sessions and due to my accessibility experience having the opportunity to talk with others in person I otherwise know virtually and seldom get to meet in person. One example is having the opportunity to talk in person with Jennison Asuncion, Engineering Manager, Accessibility at LinkedIn. Attending this event also gave me the opportunity to meet people I have never met before who are as passionate as I am about accessibility for products and services. These people also share the same enthusiasm as I for increasing accessibility in the work place. These shared goals include sponsoring inclusion for people with disabilities also with hiring, retaining and promotional opportunities. It was refreshing to be around people who understand the technical and business reasons for insuring people with disabilities are included in the work place to enhance the diverse conversations that lead to better project outcomes.

I especially enjoyed the General Sessions” How Leading Tech Companies Are Raising the Bar for Blind and Visually Impaired Users” on Thursday and “Empowering a Future of No Limits: Employment panel” on Friday. In Fridays’ general session some speakers discussed why leading companies value the unique skillsets people with disabilities have to offer. I also definitely enjoyed listening to some of the speakers explain how their companies have established partnerships between product accessibility, HR, Diversity & Inclusion to promote internal accessibility goals to assist current employees with disabilities along with the goals of attracting new talented employees.

After the Helen Keller Achievement Award ceremony I was very excited and fortunate to meet a longtime, mostly virtual friend Jenny Lay-Flurrie , Chief Accessibility Officer from Microsoft. She was honored and awarded one of the three Helen Keller Achievement Awards for Microsoft’s significant strides in developing inclusive technologies to empower people with disabilities.

Read about this prestigious award and the other 2018 Helen Keller Achievement Award Winners that include Facebook and Haben Girma who I was also fortunate enough to meet and congratulate virtually after the event.

You can read some of the highlights from The 2018 American Foundation for the Blind Leadership Conference in the April 2018 AccessWorld®. Also you can find some of the pictures of this event at American Foundation for the Blind Leadership Conference and Helen Keller Achievement Awards (Facebook) Photos.

Has anyone else attended events where you learned the value of accessibility and the benefits of demonstrating inclusion of all people equally?  If yes, what did you learn? Do you plan to incorporate anything you learned?  If yes, what do you think might be your largest obstacle you may have to overcome in order to promote any change if needed?

We all look forward to hearing your valuable comments.

Bill Tipton

Contributing Author,

Global Dialogue Center

http://www.globaldialoguecenter.com/

LinkedIn: http://www.linkedin.com/in/wdtipton

Facebook: https://www.facebook.com/bill.tipton.39

Twitter: http://twitter.com/wdtipton 

 

How People Who Are Blind Can Orientate Themselves Using a Screen Reader

Most of you who have read my blog posts or know me are aware I am completely blind. From my electronic communications you have read from me you also may understand that I use computers and mobile devices. Some probably do not know how I use these tools therefor I will explain some.  

I use a form of assistive technology called a screen reader which is software on my devices.  The screen reader reads aloud in synthesized speech the application components including the user interface controlling elements for the application enabling me to use these. My screen reader also reads web pages, web applications and the user interface elements to perform the system administration tasks for my devices. 

I think you will find the blog post A Tale of Two Rooms written by an employee I know from The Paciello Group beneficial to help you understand how a screen reader user navigates and orientates themselves on a web page or within an application. 

Does anyone have any questions to clarify anything? Do you have any other examples of how accessibility design can assist in navigation and orientation? Does anyone have an example of similar navigational and orientation techniques for people with other disabilities? 

We all look forward to hearing your valuable comments. 

Bill Tipton

Contributing Author,

Global Dialogue Center

http://www.globaldialoguecenter.com/

LinkedIn: http://www.linkedin.com/in/wdtipton

Facebook: https://www.facebook.com/bill.tipton.39

Twitter: http://twitter.com/wdtipton 

Ripple Effect of Inaccessible Tools and Potential Dollars Lost

Some of you may understand the direct relationship accessibility has on the effectiveness of people using assistive technology with the tools you develop or deploy from practicing techniques or objectives in "Web Content Accessibility Guidelines (WCAG) 2.0", "Mandate 376 (301 549)" and "Section 508 Refresh" or other guidelines and requirements.  It is less likely some of you may understand the ripple effect of inaccessible tools, (software, hardware, web pages, services and processes) have on potential dollars lost or time wasted. Others who use assistive technology and experience accessibility barriers first hand can understand the negative impact inaccessible tools have on their productivity.

I am grateful several developers and some individuals who procure tools understand the benefits of incorporating accessibility into the developmental processes or tools they deploy.  This minimal amount of attention to quality goes a long way to assist in reducing barriers resulting in increased customer base, customer satisfaction and effectiveness.

If you are unfamiliar with assistive technology or how a person who is completely blind uses a PC and experiences some of the accessibility barriers I will be describing later in web application number one and two the short scenario below may assist you in understanding the concepts. As a screen reader (one type of assistive technology) user I attempt to do some on-line shopping for groceries in a very simple web application. Once I start to process my order I quickly find the drop down list to select the method of delivery cannot be activated by keyboard commands (screen reader users generally do not use a mouse) or the results are not read to me as I scroll through my possible choices. Therefore I cannot choose how I want my order to be delivered. I also find when I tab to three different form fields I am not able to determine what I am to enter into these unlabeled form fields or even if these fields are required since they are not properly labeled with a description of what I am to enter. As I had to skip these unlabeled form fields since I was not sure what they are used for I wondered if one of them was for me to type in what I wanted to order, although I did not want to guess and pay for something I did not want therefore I continued. I did find a form field which was labeled for a telephone number, although the form field element did not specify the format I was to use (e.g. use dashes in between area code and.. or leave out dashes or include the country code). Due to these accessibility issues I was prevented from proceeding to place my order because I was not able to fill out all of the required fields or enter the telephone number using the correct format, therefore, I was not able to receive the groceries I needed.

Some developers, businesses and corporations might think it is too costly to develop tools that are accessible or usable. However, developing accessible tools can go beyond helping the employees or customers to be more productive, self-supportive and effective. Accessible tools can also potentially save money if one considers the ripple effect of inaccessible tools.

Below is just one of many possible examples:

Web Application Number 1:

• A person using assistive technology attempts to enter time critical data into a simple web application with just a few user interface elements (e.g. form fields, drop down menus, user notifications and a submit button) and found the application had accessibility barriers preventing them from accomplishing the task themselves.
• The affected person then locates anyone they can find who can help enter the data into the web application on their behalf.
• Although they did find assistance, the person they found was unfamiliar with the application. Therefore they did not notice an issue with entering the data and thought all was submitted without issues since the web application submitted the data without errors or alert messages.
• After the data was processed the result did not get processed as expected resulting in a missed deadline.
• Subsequently the person who had assisted went back to verify that the data they entered was correct, entered on time and was not processed as expected.
• The next step was that the affected person now was required to submit a help ticket to attempt to correct or explain the issue generated by web application number one.

Web Application Number 2:

• The affected person who uses assistive technology then attempted to enter a help ticket into a very simple web application with a few user interface elements to request help and found this help system also had accessibility issues preventing them from entering the case effectively.
• Then the affected person who uses assistive technology found another person who was unfamiliar with application number two to request help on their behalf to enter the help ticket regarding web application number one.
• Since the process for receiving an answer to the submitted help ticket using the fictitious accessibility work-around was becoming very time consuming the affected person contacted the person waiting for the information generated by web application number one and others affected by the delay in a resolution.
• After the help ticket generated by web application number two was received by an agent they found the request was unclear. This required a few back and forth conversations by email to attempt to resolve the issues since the help desk person could not be contacted by telephone to quickly explain the issue verbally to help overcome any language differences or barriers.
• This lack of resolution resulted in yet another group getting involved to help resolve the issue generated by web application number one.

Although what I describe above should have been a quick task of entering very little data into a simple web application with just a few user interface elements that could have possibly been resolved by the developer utilizing resources like "Labeling Controls- Forms WAI Web Accessibility Tutorials” it had become a long process.  By the time the issue was resolved at least six people over several days were involved. This could have been avoided if the people who procure tools insured they procure accessible tools or if one web application developer or their team incorporated accessibility into their web application.

If end users, businesses or corporations could capture the potential dollars and time lost for every one of these individual ripple accessibility obstacles affecting many people I describe above by incorporating accessibility into the applications, services and processes, individuals, businesses or corporations could save many dollars to reinvest into the businesses or people. Incorporating accessibility will also empower end users enabling them to be more effective allowing them to flourish and prosper without the false ceilings of inaccessible tools.

Even though my example of how many people might be involved to provide a work around to accessibility issues with tools is hypothetical, I am sure some of you might have real examples to share.

Does anyone have examples of how tool developers and procurement individuals can increase accessibility and get the required sponsorship to make positive changes?

Any thoughts to help advance the enabling of all to flourish and prosper without the false ceilings of inaccessible tools?

Does anyone have additional information or input to contribute to this conversation?

I look forward to hearing your valuable comments to help us continue this important accessibility discussion.

Bill Tipton

Contributing Author,

Global Dialogue Center

http://www.globaldialoguecenter.com/

LinkedIn: http://www.linkedin.com/in/wdtipton

Facebook: https://www.facebook.com/bill.tipton.39

Twitter: http://twitter.com/wdtipton