Imagine that you have low vision and you’re completing an online job application using screen reader software.
You get through half the form and then come to a question with drop-down options the screen reader cannot access because the online form doesn’t conform to accessibility standards. You’re stuck. You can’t submit the application, and your time has been wasted.
Assistive technologies like screen readers go a long way toward closing the gap between people who are blind or have low vision and their sighted peers. But the technologies often hit roadblocks because the information they are designed to work with – documents, websites and software programs – don’t work with them, leaving the information inaccessible.
There are 8 million people with blindness or low vision in the U.S. More than 4.23 million of them are working age, but only about half of that working-age population are employed. Employment rates for people with blindness or low vision have historically been much lower than for the general population.
An overwhelming majority of jobs across all industries require digital skills. Assistive technologies such as screen readers, screen magnifiers and braille notetakers provide people who are blind or have low vision a chance to succeed in school and the workplace.
Assistive technology has improved, and new technology for people with blindness or low vision is being developed all the time. The technology developed today by big tech companies for the general population often incorporates built-in accessibility features like VoiceOver in the iPhone and Narrator in Windows, both text-to-speech functions. These assistive technology advances have expanded job opportunities, and the percentage of people who are blind or have low vision in the labor force has increased over the past decade.
Out of sight, out of mind for the sighted
But despite the abundance of assistive technology, people who don’t rely on it are typically unaware of how it’s being used at work and the challenges users experience with it. My colleagues and I are conducting a five-year longitudinal study to increase knowledge in this area that, we hope, can help prepare unemployed people who are blind or have low vision to enter the workforce. The study is slated to continue through 2025, with the last survey starting in late 2024.
While most of the people we surveyed reported being satisfied with the assistive technology they use at work, almost all also reported challenges with it. The most significant challenges related to assistive technology centered on the inaccessible digital environment: documents, software, websites, graphics and photos.
Digital content is sometimes technically accessible but unusable by people who use assistive technology. For instance, online job application systems often generate accessibility and usability challenges. Inaccessible and unusable company software means those who are blind or have low vision are often left out of jobs they could easily perform simply because the employers’ software doesn’t work with screen readers.
People who are blind or have low vision have been harder to place in jobs than people with other types of disabilities due to inaccessible company software, Ross Barchacky, vice president of business development and strategic partnerships at Inclusively, told me. The organization supports companies who want to hire people with disabilities, including matching them with qualified job seekers with disabilities.
Digital accessibility
Although the Americans with Disabilities Act does not mention the digital environment explicitly, the Justice Department has taken the position that Title III of the ADA, which covers public accommodation for people with disabilities, applies to websites and mobile apps. Thousands of digital accessibility lawsuits are filed under the ADA each year, and the number has increased substantially in the past five years.
Digital standard-setters have begun paying attention. The World Wide Web Consortium developed standards for accessible web content: the Web Content Accessibility Guidelines, just revised in a 2.2 version. The guidelines provide free guidance to help developers make their digital content accessible. Two related standards are the U.S. government’s Section 508 and the European Telecommunications Standards Institute’s EN 301 549. Global Accessibility Awareness Day was established in 2012 to encourage people to learn and think about digital inclusion for people with disabilities.
Despite laws requiring and guidelines supporting an accessible digital environment, much if not most digital content is still not fully accessible. In its latest annual review of the accessibility of the top 1 million websites, the nonprofit WebAIM found an average of 50 accessibility errors per page. Worse, almost all home pages – 96.3% – had Web Content Accessibility Guidelines 2 failures.
What can be done
Accessibility can be built in from the beginning more easily than retrofitting after the fact.
For accessibility to be built in from the ground up, accessibility would have to be part of the curriculum for digital developers, but it typically is not.
Companies could require developers to create accessible software and refuse to buy software that isn’t accessible. Individuals can help by producing their own accessible digital documents – inaccessible digital documents were the most commonly experienced challenge at work. Microsoft has been working to make producing accessible digital documents easier with its accessibility checker and now with its new accessibility assistant.
An accessible digital environment is possible, and it would result in greater employment opportunities for people who are blind or have low vision.
This article is republished from The Conversation, a nonprofit, independent news organization bringing you facts and trustworthy analysis to help you make sense of our complex world. It was written by: Michele McDonnall, Mississippi State University
Read more:
Michele McDonnall receives funding from the National Institute on Disability, Independent Living, and Rehabilitation Research. Grant number 90RTEM0007 provided funding for the research discussed in this story.
