M3 Sweatt

“So, what happened to your blog?”

That’s a quest I got on Friday at the office from one of my associates. She asked why I had posted fewer and fewer posts per month until about a year ago, and then nearly nothing at all, save a few posts which were more general updates than insights or preaching in front of the fence with a bucket full of brushes. (Some of you will understand that reference in relationship to how I spend many days at the office.)

TL;DR, After recovering from an injury and returning to work, I knew that I would have to find ways to cope with the limitations on how I used the computer: I was lucky if I could type ten our fifteen words a minute, much slower than I could think, and somewhat slower than I could get the words out after a month of recovery. I’ve been fortunate enough to work closely with the folks in our product groups and cross company accessibility team, as well as with some of our amazing people who use our technology to accomplish basic productivity tasks after suffering much more debilitating injuries. I knew the technology and applications existed. I had even purchased some of the software solutions to help out my youngest son when he had experienced challenges early on with typing on the computer, to dictate his work. But I hadn’t used them myself beyond the basic dogfooding we do on new product releases, given several of the core abilities are offered in Windows.

My hand-eye coordination hadn’t been as impacted as much as my speech, concentration and typing, so I was able to mouse around and use my Surface tablet and Sony all-in-one touchscreens without much on an issue. But I found that I needed to enlarge what I found on the screen to make it easier to see my work and to navigate around the desktop.

So, I decided to use some of our resources to determine what I could do out of the box with our products and services to get my job done. Being somewhat stubborn and independent, I decided to do this myself, leveraging what was available in our office, on our websites and from our partners.

Having worked in the Windows group, and with Rob Sinclair and his team on accessibility solutions, I knew that Windows 7, Windows 8 and Office 2013 (where I spend most of my day) had built-in capabilities and companion programs to make it easier to use the computer. And I am a big fan of folks like Jenny Lay Flurrie, Kelly Ford, (the late) Michael Kaplan and many others at Microsoft who are not only making great contributions at the office and in our industry, but are strong advocates and adamant voices for the customers we serve.

I’ve close to 20/20 vision, so I didn’t need to take advantage of Narrator, our bundled screen reader, which reads aloud the text on the screen. But I did use the Magnifier in Windows 7 to make it easier to see parts of the screen as I moved my mouse over a document. And I found I regularly used the zoom feature in Internet Explorer and Office 2013 to magnify the documents I worked on and pages I visited. I also optimized my display to change the options of displayed dialogue boxes and the attributes of the cursor, making them easier to see and notice on the large displays. Changing the desktop screen resolution and adding a second larger 40” screen to my all-in-one computer at home made it easier to view materials and work on things in the same familiar flow, but without the need to squint.

I also found myself using the keyboard more and more, rather than the mouse, through Mouse Keys to move the arrow via the arrow keys on my keyboard, and Sticky Keys to trigger multiple, simultaneous key presses to hold one modifier key down while remembering the combination to unlock Windows or log on. I also made it easier to use Windows by preventing the automagical arrangement of windows when moved close to the edge of a screen.

One of the biggest challenges for me was typing. I had tested and used some of the capabilities in Windows 7 and Windows 8 to use my voice to control the computer with basic commands and simple dictation. It takes a while and some training before you can start using Speech Recognition reliably. But after a while of becoming familiar with the basic commands, controlling the computer and moving around a document during dictation are relatively easy, but rudimentary in my experience.

Then I remembered the copy of Dragon NaturallySpeaking I’d purchased for my son. There, I’d found the software to be very good at dictation and voice recognition (kudos to our robust set of third party developers!) over our own solution, particularly for parsing what I’d said and transcribing it automatically in Word our Outlook onto the screen. The user interface is intuitive and overall the application works quite well and is extremely fast and accurate – the key reasons I purchased version 11 (and happily upgraded to 11.5). Recognition also improves with use, and it transcribed what I said father than I could get the words out, and with great accuracy. The biggest challenge was remembering how to enter punctuation, note the end of sentences and overall formatting. One of the first public results was my blog post last July on dotless domains: Dragon handled the words like a champ with a minor amount of typing and editing. The same was true for my last two posts: although I liberally leveraged past posts and materials, I was able to edit and add to them with relative ease.

What I found myself using more and more were the Speech features on my Windows Phone. Almost by accident, I found not only could I use the large tiles on the phone to make a call, send a text or search for something on Bing, I could also initiate the action with my voice. So much easier than hunting and pecking for an app or the tile. It made it so much easier to initiate a phone call to my wife, get my voice mails, open my emails or send a text. But the real win for me was using my Windows Phone to dictate email messages instead of typing with my thumbs. I was impressed that even with my stammered speech, my Windows Phone correctly interpreted what I said with incredible accuracy. So much so that I used it to easily and effortlessly create documents in OneNote which would then be available the next time I got in front of any of my connected devices. Further I set my Windows Phone up so that it would read my incoming text messages aloud, saving to have to read them on screen… and a feature I wish I had for email, too. (I learned recently that http://www.drivesafe.ly/ is coming to Windows Phone.)

A year after my injury I still find myself using many of the features I found last summer while recuperating. I now type about forty to fifty words minute (still below my norm), and regularly use my Windows Phone for dictation, and Dragon on my Windows devices to dictate emails and documents. (That’s how I drafted much of this post today.) In all, I find that I’m more productive in many ways, plus it’s much faster and less tiring – one of the reason I save my focus for my work, and less on long blog posts and (thankfully, I’m sure many recipients think) emails. I find it easier to post on social media (Twitter publicly and Yammer internally) on walks or on the shuttle between meetings, using my phone to dictate comments in the Messaging or Outlook app which I then easily copy and paste into the social app. I also still have my standing desk (although I take more walking and seated breaks) with multiple large screens using IE and Office to magnify my work, all with a desktop screen resolution that’s more to my liking. For the tinnitus, I stream and play music from my Xbox Music account over headphones, and I use a headset or the integrated mic on my Surface Pro with speakers to sync with people over Lync.

I was fortunate enough to recover from the event generally unscathed. I’ve since moved the items around in my office, and I rarely place anything on top of my bookshelf anymore for fear of repeating my uncoordinated move of a year ago. And I have a deeper appreciation for the accessibility features and technology we build into our products at Microsoft and services that many rely upon.

I’ve read that seven out of ten people in the world will experience either permanent or temporary disability at some point in their life, and learned that we have a lot to live up to when it comes to Bill Gates’ vision “to create innovative technology that is accessible to everyone and that adapts to each person’s needs.” Having experienced and worked closely first hand on the requirements of the disabled over the last decade, I like to think that I have a good appreciation for the need, but my own personal experience was something more than I have seen and heard third hand through family members and friends. We have a great deal of work to do to make our devices and services more transparent and easy to use. I’m happy to know that our devices and services teams are dedicated and focused on knocking down the barriers for people with disabilities encounter and help them make the most of the tools we offer.

And I’ll get better about posting here, in addition to my updates on Twitter.

Additional links

• Microsoft Accessibility site
• Accessibility in Microsoft Products
• Microsoft Office 2013 Accessibility Fact Sheet

Post also available at https://aka.ms/M3-060114.

I was prodded this morning much too early: “I expected to hear from you with DST ending this week.”

Typecast much? 😉

Work has been busy, and I’ve spent more time providing updates on external and internal social media, but I’m never too busy to call attention to once again, a simpler time when we fall back in much of North America.

Daylight Saving Time ends on Sunday, November 3, 2012 at 2:00AM local time in much of the U.S and Canada, except in parts of the countries (including Hawaii and Arizona). Although many would like to abolish DST, and the venerable National Geographic magazine makes the case against it, I like to get the extra hour of sleep on Sunday. Our friends in much of Europe have already bid goodbye, adieu, auf wiedersehen, gesundheit, farewell to European Summer Time, as they fell back on the last Sunday in October each year. (Not to worry, they’ll get back up and Spring forward again on the last Sunday in March.)

As noted here, you can thank candy makers for some of the politics behind DST. There’s a rich history as to why we have daylight saving time, and you can read more than you’ll ever want to know about DST here and on our official Microsoft Daylight Saving Time Help and Support Center at http://www.microsoft.com/time. DST in much of the US and Canada ends in accordance with the US Department of Energy’s Energy Policy Act of 2005 that was passed into law. DST ends later than it did prior to 2007, on the first Sunday of November; more details on the new DST start and end times can be found here). This results in a new DST period that is approximately three to four weeks longer than in past years.

Also important to note, but often ignored: the switch to daylight saving time also means the time zone suffix changes in North America, now using Daylight Time: for example, Pacific Standard Time is now Pacific Daylight Time (aka PDT). The other time zones move to Mountain Daylight Time (MDT), Central Daylight Time (CDT), and Eastern Daylight Time (EDT).

Last year I noted the National Geographic article on “Daylight Saving Time – Why and When Does It End” – it’s still there, along with the very cool photo of the display model of the inner workings of a clock at the China Science and Technology Museum in Beijing. One of the Founding Fathers, Benjamin Franklin, is responsible for the concept of daylight saving time, as noted in David Prerau’s book Seize the Daylight: The Curious and Contentious Story of Daylight Saving Time. I personally liked TaylorBigler’s piece on the Daily Caller earlier this year…

Franklin, however, never actually meant that we should actually turn our clocks back in the fall and forward in the spring. According to research done by the geeks over at Geek.com, Franklin — who was living in Paris at the time — brought up the idea of daylight saving time in a letter to a friend who happened to be the editor of Journal de Paris. The letter, which satirically suggested that something could be done to better light one’s home, was subsequently published in the Journal on April 26, 1784.

Franklin wrote that one morning he was abruptly woken by a noise at 6 a.m., but that if that hadn’t happened he would have slept through six more hours of daylight. To combat this, Franklin satirically wrote up an analysis of how much people could get accomplished if they used more daylight and less candles. He also wrote up a series of punishments and requirements so that people would wake their <e.d.> up.

According to Geek.com, Franklin wrote that there should be a tax on people who had shutters on their windows to keep the sun out, church bells — or even a cannon  — should go off every day at sunrise, and in order to conserve one’s energy for the day, guards would monitor the streets and forbid any carriages from driving after sunset — with the exception of doctors and midwives. 

So what does this have to do with the price of tea on K Street?

As I noted in this article, Microsoft strongly recommends that DST and time zone updates be installed on all affected systems, devices and applications to ensure consistency with current DST rules and time zone settings worldwide. Customers should review the product updates available and posted on this site and at http://support.microsoft.com/gp/dst_prodlist for the latest and updated information of Microsoft products affected by daylight saving time. For the most part, customers on our Windows platform won’t need to do anything, as updated time zone definitions are already included in the products.

Here’s more coverage on DST this year from Bing News. I hope that you have a glitch-free, uneventful fall back.

On a personal note, remember to keep things in perspective. Time is a precious thing. Never waste it…

 

Tags: Microsoft, Daylight Saving Time, Daylight Savings Time, DST.

References to DST on Bing: 1,270,000.

Share this post:

Also available via https://t.co/1yQ0OTgenT