Job-hunting isn’t what it used to be! Back when I started out in the workforce, looking for a job meant picking up the phone to ask about job openings, and mailing (yes, snail mailing, with a stamp) paper copies of my resume and cover letter. But times have certainly changed.
Today, everything seems to be happening online. Most people find and apply for job openings online. Some companies even conduct pre-employment assessments on the web and remote interviews before they ever meet a job candidate in person—if they do at all.
Years ago, I was issued a compelling challenge by my friend and colleague, Dr. David Braddock, executive director of the Coleman Institute for Cognitive Disabilities. He asked me to consider examining the right to web access for people with cognitive disabilities—and I was intrigued.
IBM is a global technology and consulting company headquartered in Armonk, New York. With operations in more than 170 countries, the company develops and sells software and systems hardware and a broad range of infrastructure, cloud, and consulting services.
IBM has also been a leader in the accessible technology arena for more than 100 years, and in July 2014, it appointed Frances West as the company's first chief accessibility officer. PEAT recently talked with West about her new role and IBM's approach to accessibility.
CLOSED: Tell us about your experiences! PEAT is conducting a national survey about online job applications. This initiative will help us to better understand and document accessibility needs related to online job seeking and focus PEAT’s future efforts in this area. This survey will close on June 30, 2015.
As a senior vice president and information technology manager at Wells Fargo, I frequently received the question, "Can the company buy me a...?" Managers and team members always seemed to want the latest and greatest gadget, software application, or piece of hardware. My answer was always, "How will it make you more productive, and how will it fit into our environment?" Most of the time, the requester had no answer to these questions, so we didn't pursue things any further.