Full Issue: AccessWorld Spring 2023

Editor's Page: Welcome to the First Issue of The Relaunched and Expanded <i>AccessWorld!</i>

Dear AccessWorld Readers,

Welcome to the inaugural issue of the refreshed AccessWorld! As I have mentioned in the last two issues, with our inclusion into AFB's Talent Lab program, AccessWorld has been updated with new content, a new look, and a new structure.

Historically, AccessWorld has focused primarily on assistive technology users with blindness or low vision, their friends and family, teachers of the visually impaired, and rehabilitation professionals. With our transition to the Talent Lab, our new vision is to be a practical source of knowledge regarding the intersection of disability and technology and include technology professionals in our community to help them build their accessibility skills and create a digitally inclusive future.

As part of this effort, we will begin publishing an array of article categories to support our mission of promoting digital inclusion:

  • Product Reviews: Analyses focused on the accessibility of a given product or service, detailing the standout accessibility features as well as what access pitfalls may be present in order to inform you of the accessibility of a given product while also spotlighting important practical accessibility takeaways for designers and developers.
  • Employment Journeys: Conversations with people with disabilities, spotlighting their experiences and advice for employers and other people who are blind or low vision seeking employment.
  • Ask an Expert: Interviews with experts in the field of accessibility, from access professionals to app or web developers.
  • Best Practice Guides: Detailed technical insights to digital designers and developers, focusing on process, techniques, and examples for practical application.
  • Inclusive Tech Research: Exploration of the use of technology or trends in accessibility to pieces exploring a given piece of novel technology that might be valuable in the work of digital inclusion.
  • Conference Coverage: Reports on developments in the field of accessibility as well as new developments in mainstream technology that might be applicable to improving accessibility.

AccessWorld is also sporting a new visual presentation (including a cool new logo) as well as minor changes to page structure. Going forward, AccessWorld will be published quarterly, on a seasonal basis. This issue is our inaugural Spring 2023 issue. The next issue to be released will be our Summer issue, which will be published in August 2023 with Fall and Winter issues released in November and February, respectively. Don’t forget to sign up for our email alerts for the launch of new issues, if you haven’t already subscribed!

As always, we’d love to hear your feedback, so feel free to contact me by email at apreece@afb.org.

Sincerely,

Aaron Preece

AccessWorld Editor in Chief

Check out the Spring 2023 Issue now!

Moderating Google Groups: A screen reader and browser comparison

Janet Ingber

There tends to be a heavy focus on consumer-facing technology in regards to accessibility. It is important to be sure for the largest number of people to be able to access a product as possible, but it is also vitally important that back-end technologies and internal software is accessible as well. The accessibility of back-end products can have a profound effect on someone's ability to perform their job if they are blind or have low vision. Google Groups is no different; the public facing interface is known to be quite accessible, but how does the back-end fair? To answer this question, we took a look at the controls available to Google Group moderators to determine their accessibility as well as highlight where their access choices could be emulated by others seeking to make similar interfaces accessible.

For this piece, we will be reviewing moderator controls on both Mac and Windows. The Safari, Chrome, and Edge browsers were used for testing, and all use Google’s Chromium rendering engine. For this reason, many of the features of Google Groups work similarly on Mac and Windows.

Common Features

Before we explore the accessibility of Google Group moderation, it is important to understand the structure of the interface. The My Groups table has the list of all your Google groups. The first row of the table is clearly labeled with controls for sorting and subscription. Subsequent rows contain the name of the list, including a link to view the group. Next is a brief description of the list. This is followed by the joined date and subscription options. At the end of each group’s name is a More button. When activated, there are choices including Add Members and Leave Group.

Once a group’s link is selected, a new page loads. It can be explored with basic navigation techniques.

The first item is Conversations. This is where you can select a conversation and perform actions, including Report Abuse and Block.

The next two options are Approved and Pending. These relate to messages posted to the group. Next is the People option. This contains basic information about group members and also contains information about members posting status. The Members option gives the same basic information as the People option. It also has buttons to add members and export the member list. The Pending option is for potential members. Banned members is self explanatory. The final three options are About, My Membership Settings, and Group. About has information about the group. My Membership Settings are your settings for the group. The Group Settings has specific settings for the group.

Once in any of the lists, you will find a table containing the content you have focused. For example, if the Members option is selected, a table will be below the controls. Table headings are the member’s name, whether they are an external member, their email address, and their role. The role can be member, moderator, or owner. You can change their status from within this table. Next is their joined date and whether their posts are allowed or need to be moderated. This status can also be changed from this table.

Moderating with Safari and VoiceOver

When using Safari, I experienced focus order issues when moderating Google Groups with VoiceOver. I would navigate about the screen and end up in a location far from where I intended. Sometimes I was out of the Google Groups interface and in the area containing links to other Google apps and services. In addition, I could not always navigate to the search form.

Some controls could have clearer labels. As an example, the Pending control for messages did not say the number of messages needing to be approved which would be useful information to include.

The fastest method for accessing needed areas of the page was to perform a find on key text, meaning efficient aids to navigation are not present. If a user must find text to quickly access parts of the page efficiently, this means that the app or website does not use enough proper navigation options, such as headings or ARIA Landmarks.

Chrome

When using Chrome and VoiceOver, accessing member controls was more efficient than when using Safari. After a given group link is activated, VoiceOver focus is placed in a position so that navigating through the page to group controls is more efficient. In Chrome, the controls are numbered 1-9. The final control, Group Settings, is not numbered. You can also access the controls using headings navigation. Controls that provide lists of information, such as the members list, Chrome renders these in a table similar to Safari. Though focus order issues did not occur when using this browser, it was still necessary to find strings of text to efficiently access certain controls.

Windows with Edge and Jaws

Google Groups is rendered similarly when using Windows and the Edge browser. During testing, JAWS was found to be the most efficient screen reader to use with the interface, though NVDA is also functional. Due to screen reader options, finding strings of text are not as necessary to efficiently navigate the interface. In addition, focus order issues were not experienced when using Edge and JAWS.

A special thank you to Maria Kristic for her help with Windows. JAWS is her primary screen reader. She uses both Edge and Chrome. She indicated that Edge and Chrome provide a similar experience when working with Google Groups on Windows.

Access Tips

If you are managing Google Groups, be sure that you are signed into the email domain assigned for the groups. If you sign in with your personal email address you will not have access to the controls used by a moderator. In addition, you need to be familiar with your screen reader’s navigation controls such as locating tables and performing searches.

Google Groups has a feature called Scope Search Selector. It consists of a combo and an edit box. The feature is context sensitive. For example, if you are in a particular group, your results will reflect that group. Google also now has a Navigational Drawer. This feature can help you move to specific locations.

Google Groups makes frequent use of tables. Having the tables option in my VoiceOver rotor was helpful. I bookmarked the Home page. Using these techniques made it easier to get where I needed to go. Sometimes I would end up at the top of the web page. Instead of going item by item, I would just navigate with VoiceOver to get to the My Groups table.

Conclusion

Google Groups is fully accessible in that all controls are labeled and function properly when using a screen reader. When using VoiceOver on Mac with Safari, some focus order issues might be experienced. In addition, outside of navigating to main group controls, the use of find is necessary to efficiently navigate the interface. Overall, moderating Google Groups is accessible, but does not have any specific access features of note and navigation options could be improved.

Employment Journeys, Darren Burton, Access Industry Veteran

Aaron Preece

If you are familiar with AFB, or have been an AccessWorld reader for many years, you probably recognize the name of Darren Burton. Darren was a key member of AFB Tech and a prolific AccessWorld author for many years before his move to Yahoo in 2014. As part of our inaugural issue of the relaunched AccessWorld, we sat down with Darren to get his insights on recovery after vision loss, technology, and solutions to the employment barriers facing the blind and low vision community today.

Background

Before losing his vision, Darren attended West Virginia University before moving on to join a brokerage firm. Several years later, while skiing, he noticed that his vision was decreasing and upon inspection, it was discovered that there was a tumor on his pituitary which was affecting his vision. During surgery in 1993, his optic nerve was damaged, leaving him with light perception only. After a few years of regaining his living skills, he returned to college to finish his degree where he also taught himself how to use the assistive technology available at the time. After finishing his degree, Darren attended law school at WVU where he found his way into the access industry. While in law school, a judge who was blind was appointed, and Darren became the consultant who aided in setting up an accessible court room for him. After this position, Darren left law school and entered the blindness technology industry full time. His next position was at the West Virginia Assistive Technology System, followed by his position with AFB when the AFB Tech office opened in Huntington in 2002. He rose to the position of director of the Huntington office before becoming an access expert for Yahoo in 2014. In semi-retirement, he now instructs the interns and apprentices as part of the AFB Talent Lab.

Interview with Darren

Question: When you started losing your vision, did you have an idea where you could learn the skills you would need to function as someone who is blind in daily life, e.g., assistive technology, Orientation and Mobility, living skills, etc., or did you have to learn after vision loss?

Burton: I was clueless; I really knew nothing about anything technology wise. Right out of the hospital, my brother worked for the state department of vocational rehabilitation so he connected me there, and I went there for a few months learning braille and cane travel, but they had no technology training whatsoever. The rest of it, the technology, I had to learn 100% on my own, save up the money to buy it on my own. But yes, 100% I was very clueless and unprepared; I knew a few people who helped me out here and there, but it was really an unstructured discovery so to speak.

Question: How did you regain your confidence after losing your vision; were there specific skills that helped with this?

Burton: One good skill I learned from Voc Rehab was cane travel. Getting out the door, that's number one. Luck and good fortune doesn't come sitting at home. Also what helped me get my sea legs and get back on my feet and confident when doing things-not only getting out of the house and seeing friends but doing things like skiing. Skiing was huge. Getting back on the slopes and successfully getting down the mountain, having a lot of fun at it and skiing fast, that was awesome. Playing cards with my buddies. My buddies helped me get down the mountain, but playing poker, it was an even playing field competing. That, in many ways, was even better, especially if I won a few bucks.

Question: Did you have certain views of what it would be like to be blind before losing your vision? Did any of these views change after vision loss?

Burton: I did have stereotypes. I had read the Helen Keller book and knew some blind people around town; one was a very skilled wood carver who did a really good job. So I had the Superman idea but also the idea of the homeless blind person begging on the street. I'd seen the Stevie Wonder commercial using one of the early OCR machines, so I thought, ‘Hey, we take good care of blind people; they've got everything, they've got dogs, we're good.’ But after I lost my sight I was really surprised at things like the lack of technical knowledge in the training I got and the incredibly bad state of the technology available for blind people at the time. In 1993, there wasn't a whole lot. There were some talking watches, but there were no accessible phones, JAWS was extremely limited, there was no internet access at all, and the only things accessible were email, spreadsheets, and word processing. Many of my impressions were not true.

Question: Since you have experienced both employment from the perspective of someone sighted as well as someone who is blind, what have been the major differences? What has been the largest obstacle working as someone who is blind or low vision?

Burton: When I was sighted, I was cavalier about everything in life. When I lost my sight, I became much more focused. Right now, the biggest barrier is the inaccessibility of 3rd party software. Even when they're accessible like Google Docs, from a usability standpoint, it can still be frustrating to use. If we have a 40 hour work week, we're probably working 50 to keep up with our colleagues. As an example, at Yahoo, I had to do travel and expenses, and any of our internal stuff like our benefits management portal, our time management portal-none of that was accessible. To get it done, we didn't have any admin support that we could sit down with for an hour and do it either. I had to twist the arms of friends or say, if you'll do this for me, I'll do this for you.

Question: What has been the largest positive development in technology that has occurred since 2010?

Burton: The new full page braille displays have the potential I think to be a game changer. Remember all the talk about wearables; I don't think that's ever hit. Right now, the AI we're seeing is going to be a huge game changer. We already have some of our interns and apprentices using one of them to choose the proper WCAG success criteria; that's huge. I think it’s scary, I think it’s exciting.

Question: You are considered to be a natural leader and very charismatic; are these traits something you have deliberately cultivated or did you find that they are something inherent to who you are?

Burton: Being outgoing has helped my career. Being the mountain climber, football player, having the ‘lets go for it even if I run into a wall, I'll keep going’ mentality has helped. I've certainly worked on developing that outgoing spirit, for sure. I worked on presentations, getting up in front of people and speaking; I've improved on that over the years. Soft skills, I think, are as important or possibly even more important than the tech skills. Just building that confidence. When I lost my sight, I was afraid to go out; I had this feeling that I would let everybody down. I didn't really leave the house for months, and when I finally went to a party, I was scared to death but ended up having a lot of fun. Those kinds of things really helped for sure, both personally and professionally. As my confidence grew, my abilities and my career grew; that gave me more confidence and it feeds upon itself.

Question: If you could go back in time and change or tell yourself something at any point in your employment journey, when and what would that be, if anything?

Burton: I think I would have gone to Silicon Valley earlier, but I was afraid to go, even back when I was sighted. I would have been bolder. I was just talking with our interns and apprentices who are afraid they will find a job they are interested in but that they are not qualified for. I have never been qualified for any job I have ever gotten. There has always been something in the job description that I am not qualified for, but that’s the same with everyone. I would want to be more aggressive to encourage change, I think. I would have also found ways to develop ideas I wanted to build. I had access to the right people at different times but didn’t take advantage of it.

Question: What do you think we could do to positively impact employment for people who are blind or low vision?

Burton: One of the things I think we can have an effect on more easily are those accessibility barriers I talked about. The 3rd party software, the inaccessible websites, the apps– we're never going to go out of the accessibility business. Let’s say we solve that. Then they're are two more barriers. We have to change the attitudes of the employers to lower the unemployment rate for people who a blind; although it is certainly improving, it’s not well enough. We also need to set high expectations for the younger generations of blind students about to enter the workforce so they have confidence for the workplace.

Question: What is something you wish was common sense, something you wish you could tell to people (be it to employers, coworkers, companies, able-bodied people, other people with disabilities, etc) regarding employment and inclusion/accessibility?

Burton: Really, the trust in our abilities. We function in our lives, why couldn't we function at work? I had someone the other day ask, "I saw that you were blind, but how are you using that phone?" And they had no concept of speech output and the power of assistive technology, which opens so many doors for us. That needs to change.

A Novice’s Guide to VPATs

John Lilly

If you’re new to the accessibility space, or even if you are not, you have probably heard the term “VPAT” (usually pronounced “vee-pat”) thrown around. So what is a VPAT, and why is it important?

When evaluating a vendor or product for potential use, one requirement that the product may (and definitely should) fulfill is that the product must be accessible for users using assistive technology. Before even evaluating the product, the first question to be asked is if the product is accessible, and if the developer claims it is, then a VPAT is usually provided as proof of the product being accessible.

VPATs are generally not provided to the public audience since they are intended to indicate to the government and other companies looking to use a product that it is accessible, but for some companies, you can request them although you may run into roadblocks if you are not actually trying to buy or use the product. But if you are planning to use a product yourself, seeking out the VPAT might be a helpful step in evaluating if the product will meet your needs. This is especially true when taking into account cost and the seriousness of your use case, e.g., using accounting software for a home business.

What is a VPAT?

VPAT stands for Voluntary Product Accessibility Template and is used as part of the Section 508 Standards which for the purpose of this discussion boils down to the rule that vendors and products that contract with the US Federal Government must meet certain accessibility standards, and the VPAT is documentation of how well the product conforms to those standards. VPATs are usually used for software which can include computer applications, websites, and mobile apps. They could also be included for certain types of hardware such as smart TVs, but they usually still detail the accessibility of the software or user interface associated with the hardware. You may have also heard of an ACR or Accessibility Conformance Report. Where the VPAT is simply an empty template, the ACR is a completed VPAT, and they are generally used interchangeably in conversations. For this article, we will just refer to them as VPATs.

Since 2017, the VPAT has been based on the Web Content Accessibility Guidelines or WCAG. WCAG is a set of accessibility guidelines that the World Wide Web Consortium or W3C maintains with input from accessibility experts across the world. The template contains a list of the WCAG success criteria and allows authors to document whether their product meets each of the success criteria.

Due to the voluntary nature of VPATs, they should not be used as proof of the product being accessible. VPATs can be written by anyone. You don’t have to have a special certification in order to fill out the template, but usually they are written by a third-party, independent accessibility expert in order to give the document more credibility. VPATs can also be written by the product owner themselves, but the product owner has a vested interest in showing their product in a good light. VPATs should only be used as a first step in the process of determining if a product is accessible. If the vendor does not have a VPAT for their product or has never heard of a VPAT, it is a pretty good indication that they have not taken accessibility seriously or at all.

If you did get a VPAT from a vendor, the first thing you should look at is the date that the VPAT was created. If it is over a year old, ask the vendor when the last major code update took place because there is a chance that the VPAT is no longer accurate due to changes that have been made to the product. If the VPAT seems particularly old, you will want to be extra skeptical of its claims to accessibility due to how quickly most digital products are updated these days.

How to Read a VPAT

VPATs should be treated as an initial step in the evaluation process for determining whether a vendor or product is accessible. If the vendor is honest, their VPAT will reflect what WCAG success criteria they meet, and what success criteria they partially meet or do not meet at all.

The meat of the VPAT is the list of WCAG success criteria. Typically each success criteria will have a conformance rating that the product meets. These ratings include:

  • Supports - The product fully supports or meets the success criteria
  • Partially Supports - The product supports or meets the success criteria with exceptions
  • Does Not Support - The product does not support or meet the success criteria
  • Not Applicable - The success criteria does not apply to the product. You typically see this response with success criteria like captions or audio descriptions when the product doesn’t contain any video or media.
  • Not Evaluated - The product was not evaluated against the success criteria.

When a success criteria is rated as Partially Supports or Does Not Support, there should be an accompanying remark or explanation as to why the success criteria received that rating, which should give some examples as to why the product partially supports or does not support the success criteria.

The sample table below demonstrates the formatting of the VPAT:

Criteria Conformance Level Remarks
1.1.1 Non-text Content (Level A Supports The product provides sufficient text alternatives.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Not Applicable The product does not contain pre-recorded audio or video.
1.3.1 Info and Relationships (Level A) Does Not Support The product does not support this success criteria. None of the data tables presented within the product contain the proper semantic markup.
1.3.2 Meaningful Sequence (Level A) Partially Supports The product partially supports this success criteria. There is one instance on the home page of content being repositioned using CSS which affects the reading order of the content.

If a success criteria is marked as “Partially Supports” or “Does Not Support”, that does not mean that the product is “not accessible”. It is very rare to see a product that is 100% accessible with zero issues, and that is very hard to achieve considering that not everyone interprets WCAG in the exact same manner. If you see “Partially Supports” or “Does Not Support” within the VPAT, you should ask the vendor why those are marked as such and when they plan on fixing those issues. You should also validate those issues yourself just to see how severe they are because those issues could be fairly minor or appear somewhere in the product that you do not have any plans of using.

Validating a VPAT

So, you’ve found or received a VPAT and the date on it appears reasonable, what is the next step? In order to be certain that the product is accessible, it is necessary to investigate its claims yourself to see if it is accurate. This doesn’t mean that you need to do a full accessibility audit of the product, but you should check some of the success criteria that they claim to support. For example, if they claim to fully support 1.1.1 Non-Text Content, check out some of the images within the product to make sure they do indeed have alternative text and that the alternative text is accurate. If the vendor refuses to give you access to test the product in order to validate the accessibility yourself, that should be considered a red flag. You as the purchaser bear the responsibility of the product being accessible from the standpoint of whoever is going to be using the product. If the vendor will not allow you to validate the accessibility yourself, it gives off the air of not caring about customer satisfaction.

On the other hand, if you see that a product has “Partially Supports” marked for some success criteria, verify the severity of the claim. It could be that the issue is more severe than what the VPAT is claiming, or it could be not that big of a deal such as a list not being coded correctly within the footer.

If you do not have the expertise or time to validate VPAT issues yourself or within your organization, contact the AFB Talent Lab. We have decades of comprehensive experience as well as individuals that use assistive technology on a daily basis.

Takeaways

VPATs should be thought of as a starting point for determining the accessibility of a product. You can think of them as the keys to the starting point of an accessible product. If they do not have a VPAT, have never heard of a VPAT, or refuse to share the VPAT with you, then it should be a big red flag that the product is most likely not accessible. VPATs should also never be used as proof of an accessible product if you are trying to determine whether a product is accessible or not. The VPAT could claim that the entire product is free from accessibility issues but was written 5 years ago and they have not produced a new VPAT since then. Or they could claim to have zero accessibility issues, but the product contains numerous accessibility issues after you have already signed a contract and started using it. Use the VPAT as a starting point and do a spot check of the claims that the VPAT is making. Don’t be afraid to ask the vendor questions about inconsistencies within the VPAT or concerns you may have because in the end, the VPAT is their claim of accessibility, and they should be able to defend their claims.

Interest In and Adoption of Novel AT: Findings from NRTC's AT in the Workplace Study

Michele McDonnall, Ph.D., CRC

Anne Steverson, MS

The National Research & Training Center on Blindness & Low Vision

In the past 20 years, there has been a plethora of new technology and dramatic advances in existing technology for people who are blind or have low vision. Innovative, novel assistive technology (AT) continue to be introduced every year, and additional novel AT is in development. Professionals from multiple, diverging backgrounds are working on developing these novel AT to benefit people who are blind or have low vision. For example, some novel AT include the number of head mounted video magnifiers now available, as well as the developing field of multi-line braille tablets, with the Canute by Bristol Braille Technology being the first of the latest efforts available on the market. Other novel AT include the numerous AT meant to help people with orientation, navigation, and/or wayfinding, such as the Mira backpack and a smart cane by HearSee Mobility.

Although many novel AT are introduced, few are widely adopted or regularly used. Given the abundance of novel AT but limited adoption, we wanted to know how people who are blind or have low vision learn about novel AT, what impacts their decision to try it, and what they think about it in general. We addressed novel AT in our most recent survey from the AT in the Workplace Study with our sample of employed people who are blind or have low vision.

Takeaways

Most participants with blindness or low vision in our survey appear to have an interest in novel AT, but only if it meets certain requirements. Two primary requirements are that the new AT be highly functional and affordable. The novel AT being easy to use was also an important consideration for most people.

Several people commented on the learning curve with novel AT – the (often) large amount of time it takes for them to learn how to use a new device or app. Some people mentioned the considerable amount of energy required for this task. Several people's sentiment was they would only be willing to go through the process of learning a novel AT if the reward was expected to be great enough. An adequate reward might be a unique feature unavailable elsewhere, a true improvement over an existing feature or function, or something that would save them time in the future.

For employers, our research indicates that in most situations, employees that are blind or have low vision will prefer traditional AT, screen readers and magnifiers like JAWS and Zoom Text and similar, over novel AT. This may vary by position. For example, those in the sciences may need novel accessible lab equipment, but overall, few people are interested in adopting novel AT when the traditional AT that they use will suffice. If you are considering adopting novel AT for your workplace, a key consideration would be training. If you wish to implement a piece of novel AT, ease of use and the availability of robust training materials would be important factors in successful implementation.

The many developers of new AT should keep these findings in mind as they create new AT for people who are blind or have low vision. Developers should be aware of all currently available AT and focus on creating something truly unique or an improvement on existing AT. Keeping in mind that people with blindness or low vision are the ones to determine improvement is critical. More than one participant commented on developers lacking awareness of the population's needs. Consulting with people who are blind or have low vision in the development of novel AT is essential.

There have been astounding advancements in technology recently. The extent that these advancements can be applied to novel solutions that will help people who are blind or have low vision remains to be seen. Hopefully, creators will carefully consider the potential cost, functionality, and ease of use of their planned product, in consultation with people who are blind or have low vision, prior to and during development.

Participant and Survey Information

Data from 328 participants were collected from May to August 2022. Participants ranged in age from 22 to 90, with an average age of 46.42 (SD = 12.21), representing 46 states and 4 Canadian provinces. A majority (61%) were female. Most were white (83.8%), followed by black or African American (7.0%) and Asian (6.4%), and 7.1% reported other races. About 61% were totally blind, 20.7% were legally blind with minimal functional vision, 15.2% were legally blind with some functional vision, and 3.4% had low vision. Many participants (58.7%) experienced vision loss before age 1, and only 16.2% experienced vision loss at or after age 20.

Participants completed the survey either online via Qualtrics or by phone. In the survey, we defined newly introduced, novel AT for participants as novel technology that is commercially available but is not widely used yet, such as WeWALK, BrainPort Vision Pro, Discover Access for SharePoint, and Microsoft's Soundscape app. We asked three questions to find out how people learn about novel AT, factors that impact their decision to try it, and current interest in adopting novel AT.

Learning About Novel AT

We gave participants a list of potential ways they may have learned about novel AT, and they selected all that applied. Table 1 in the appendix provides their responses, from most to least common methods for learning about novel AT. The most common way to learn about novel AT was from other people who are blind or have low vision, and only 8% of our sample reported that they do not usually hear about novel AT.

Deciding Whether to Adopt

To find out how our participants decide whether to adopt a novel AT, we provided them with a list of potential factors that might impact their interest in it. We asked them to rate the importance of each factor, from 1 (not important at all) to 5 (very important). Table 2 presents the average rating for each factor, sorted from most important to least important.

Three factors were more important than the others, with one being the clear standout: functionality, meaning that the novel AT would need to be more helpful than current AT options. Functionality was considered "very important" by most participants. The affordability of the novel AT was also important for most people, and its ease of use was equally important.

We invited participants to provide comments about how they decide whether to adopt newly introduced, novel AT, and 206 people responded. We reviewed their comments and organized them into categories, or themes. Most comments fit into more than one category, suggesting that multiple factors contribute to deciding whether to adopt novel AT. Here, we provide some of the most pertinent themes, along with some illustrative quotes.

The most common theme, mentioned by 24.8% of respondents, was that cost/affordability was a large factor in their decision to try a novel AT, and several commented that novel AT is usually expensive. Another common response was that the novel AT must be useful in daily life, practical, and/or functional, which was mentioned by 18.9% of participants. Along these same lines, some people emphasized that the product would have to be truly useful and better than the AT the person is currently using (7.8%). Many responses touched on both affordability and the importance of product usefulness, for example:

I want to determine if this is a truly useful new technology, not something that someone sighted thinks blind people would find helpful which is often my impression when I hear about vendors offering new tech at conferences. However, sometimes things come along that are truly innovative like Aira or GPS or OCR, and I am willing to pay for these types of new tech. I am willing to spend hundreds of dollars but not thousands unless I know the investment is something I will use frequently and for years to come.

A number of people (16.4%) commented on their excitement about novel AT, stating that they like to learn about, try, and/or use novel AT.

I am excited with how often new technology is coming out at this point. When I was in high school in the 90's it cost a lot more, and tech was slow.

Several people commented on the importance of the new AT being easy to use and/or easy to learn (11.2%).

The more user friendly and accessible the AT is, the more interested I am in finding out about it and purchasing it.

Others focused on the importance of the AT improving their productivity or efficiency (9.2%); while some considered whether the novel AT offers new or unique features not available elsewhere (7.3%).

I'm all about novel assistive tech, especially if it performs a new function I haven't previously been able to do without sighted assistance. Aira has been this novel AT in recent years, and I think the Braille/tactile tablet and/or the multi-line Braille display may represent the next revolutions .

Decisions about adopting new AT are based, at least for me, on whether they provide the ability to do something that I do not already have a solution to do, whether their way is more efficient than what I am already using, and the price (is what the new AT able to help with worth the investment.)

Several respondents commented on the time and energy it can take to adopt new AT, or the big learning curve for new AT (6.3%).

I am practical. If the novel or new AT will help me do my job more efficiently or will be easier to use, I'm willing to adopt it, if I can. Learning to use new AT takes time, I don't want to waste my time if it won't save me time later.

I have big fears about the learning curve. Adding to the issue of training that is made available through [the] AT provider is usually just an introduction and overview that I will forget shortly after.

Only 11, or 5.3%, of participants who provided comments indicated that they are not interested in adopting novel AT. Some people did not want to take time learning new AT and others did not want to deal with potential issues due to the novelty of the AT.

I really prefer using standard, integrated AT rather than more devices. I need things to work. I don't have time to play with the new stuff as I have advanced in my career.

I don't like to be one of the first ones to try something new because all of the potential bugs have not been worked out yet.

Current Interest in Adopting Novel AT

We also asked participants about their current interest in adopting a novel AT; about a third of participants would like to adopt a novel AT. The two most common types of novel AT they were interested in trying were (1) orientation/navigation/wayfinding devices or apps and (2) braille devices (both at 29.4%). Interest was almost as high for wearable glasses or other wearable devices (28.4%). Voice control or dictation software was the only other commonly mentioned AT, by fewer people (5.9%). Several people (21.6%) mentioned items that are AT but not novel AT as we defined it, and some of the braille devices mentioned were not novel AT.

Appendix

Table 1:

Methods for Learning about Novel AT Percent
Word of mouth/from other people with blindness or low vision 75.2
From emails, listservs, or podcasts 61.5
Conferences 40.5
I like to learn about new AT so I seek out information online. 40.5
I don't seek out information but sometimes learn about it online. 27.1
Directly from talking to AT vendors 20.7
From a rehabilitation professional, including AT specialist 15.6
I don't usually hear about newly introduced AT. 8.0
Other 4.5

Table 2:

Factor Average Rating
Functionality (whether what it does would help me more than current AT options) 4.7
Price/affordability 4.2
Ease of use (whether it would be easier to use than my current AT) 4.1
User reviews 3.2
Friends or colleagues are using it 3.1
Uniqueness of the AT – I like to be one of the first to try new products 2.0

Acknowledgement: The contents of this manuscript were developed under a grant from the U.S. Department of Health and Human Services, NIDILRR grant 90RTEM0007. However, these contents do not necessarily represent the policy of the Department of Health and Human Services and should not indicate endorsement by the Federal Government.