Posts tagged with "accessibility"

Understanding Night Shift’s Impact on Accessibility

To my knowledge, the release of Night Shift in iOS 9.3 is only the second time in recent history Apple has updated iOS to include a change or feature that has potential accessibility ramifications. The other occurrence, in my mind, was iOS 7.1 beta 2, released in 2013. In it, Apple added a Button Shapes option to Accessibility as a way to assuage users who have trouble distinguishing an actionable button from a text label. Generally, however, any significant additions or changes to the Accessibility feature set comes included with a major new version of iOS. That is to say, the version Craig Federighi talks about at the annual WWDC keynote.

Before getting into Night Shift’s accessibility merit, it’s worth examining why it exists. The impetus for Night Shift is better sleep. Apple explains in its marketing material for iOS 9.3 that a person’s circadian rhythm can be disrupted by the “bright blue light” emitted from an iPhone or iPad’s screen, making it difficult to fall asleep. What Night Shift does to combat this, according to Apple, is “use your iOS device’s clock and geolocation to determine when it’s sunset in your location.” After gathering that data, the software then “automatically shifts the colors in your display to the warmer end of the spectrum.” The end result is a display that’s easier on the eyes, thus hopefully making it easier to fall asleep. (The display settings will revert to normal in the morning. There’s an option to schedule Night Shift as well.) For more on why Night Shift is important and how it works, iMore has posted a good explainer on the feature.

Read more

iOS 9 and Accessibility: My 5 Favorite Details

I’ve made the case more than once that accessibility, conceptually, is not a domain exclusive to the disabled. Certainly, persons with disabilities will always be the target market for accessibility features, but I think many fully-abled people overlook the fact that accessibility features can help them too. To me, the canonical example is larger text. Yes, something like Large Dynamic Type is a boon to the visually impaired, but it can also benefit someone with aging or tired eyes.

In a similar vein, accessibility isn’t solely about discrete Accessibility features. While a big part of my writing involves reporting on iOS’ (and watchOS’) Accessibility features and how they affect users, I do make an effort to focus and write on the smaller aspects of accessibility. That is to say, I try to find accessibility in less obvious places – for instance, how technologies like Touch ID and Force Touch impact the disabled.

This concept has extended to my testing of the iOS 9 public beta throughout the summer. As I’ve gotten used to the new operating system on my iPhone 6 and iPad Air, I’ve come to notice several details that aren’t intentionally for accessibility, but nonetheless make the experience more accessible (and more enjoyable).

With that in mind, here are five “little things” in iOS 9 that stand out the most.

Read more

How iOS’ Switch Control Is Changing Lives→

Great story by Charlie Warzel for BuzzFeed on Christopher Hills, Apple-certified Final Cut Pro editor who overcame the difficulties of using touch screens and modern software thanks to Apple’s Switch Control:

Maybe most important though — at least for Hills — it’s about a feeling of liberation that’s hard for any company to measure in an earnings report or tech specs sheet. “These tools have allowed me to come out of my shell and make my own way in the world,” he wrote in an email to BuzzFeed News. “From communication and environmental control, to work and learning, and recreation and entertainment. Combined with the internet, Switch Control has allowed me to engage with the world more than ever before and to participate and contribute in ways that I never really thought would be possible.” Ultimately for Hills, it’s about a personal sense of dignity that comes from being able to share his voice and passion with the world.

Beautiful and inspiring.

Permalink

Accessibility at WWDC 2015→

Fantastic coverage from Steven Aquino on Accessibility at WWDC 2015:

To me, the labs were one of the most exciting part of my visit. It seemed to me that the labs are where the action is at WWDC. Developers want to visit the labs because they’ve gone to sessions and want to implement accessibility (among other things) the right way.

The room was full of enthusiasm, which warmed my heart to see. As a person with disabilities, it’s thrilling for me to see others make concerted efforts to ensure that their apps are usable by all.

Permalink

Accessibility Helps App Store Sales→

Craig Hockenberry, writing on The Iconfactory blog:

We’re not in this business just to make money: all of us at the Iconfactory hope that our products will make people’s lives better. We’ve worked hard to make Twitterrific work well with the accessibility features in iOS. Hearing that these efforts make things easier for customers with disabilities is rewarding beyond words. (Listen to the podcast file in that last link to get a great idea of what life is like for a VoiceOver user.)

But now there’s another incentive for thinking about accessibility: helping others also helps your downloads […]

Implementing features that make an impact is also a good business. Twitterrific and Workflow are great examples.

Permalink

The Accessibility of Apple Watch Bands

Last summer, I wrote an article for iMore in which I stress the importance of looking at hardware in accessibility terms. I wrote, in part:

Assessing the kinesthetic, tactile value of using an iPhone or iPad is just as important as assessing the software it runs. Speaking from personal experience, not only am I visually impaired but I also suffer from a mild form of cerebral palsy. What this means is, for me, the strength in my hands and fingers are substantially less than that of a fully-abled person. Hence, it takes much more effort to hold things — in this case, my iOS devices — as well as do things on my devices, like typing. Because of this, my approach to buying a new iPhone or iPad depends not only on 64-bit systems-on-a-chip and improved cameras, but also how the device feels in my hands: the weight, width, thinness, etc.

What applies to iPhones and iPads also applies to Apple Watch. In the context of the Watch, the hardware that is most crucial, accessibility-wise, are the bands. To folks like me who suffer from motor delays, the ability to successfully get the Apple Watch on and off is as key to a positive user experience as the quality of the software it runs.

Read more

Why Force Touch Matters for Accessibility

Editorial Preview

Aside from keeping our iPhones in our pocket more, I think the Apple Watch is compelling for another reason: communication. The ways in which Apple is allowing people to communicate via Apple Watch – taps, doodles, and, yes, even heartbeats – is a clever, discreet new paradigm that epitomizes the company’s mantra that the Watch is the most intimate and personal device they’ve ever created. I, for one, am very much looking forward to trying these features.

What’s even more compelling, though, in my view, is the engine that’s powering the delivery of said communication – namely, the Taptic Engine. Beyond its use for notifications and communication on the Watch, Apple has implemented its Taptic Engine in one other form: trackpads. Apple has put the tech into the new MacBook and the refreshed 13-inch Retina MacBook Pro. I had an opportunity to play with the Force Touch trackpad (about 30 minutes) at my favorite Apple Store here in San Francisco, and came away very, very impressed.

I find Apple’s embrace of haptic feedback fascinating and exciting, because the use of haptic technology has some very real benefits in terms of accessibility.

Read more

iOS 8, Accessibility, and Third-Party Keyboards

In the overview I wrote for MacStories of the new Accessibility features of iOS 8, I said this about the operating system’s support for third-party keyboards:

This topic (as well as QuickType) is worthy of its own standalone article, but the accessibility ramifications of iOS 8’s third party keyboard API are potentially huge for those with special needs.

Four months later, that statement still holds true.

Over the past few weeks, I’ve been using two such keyboards — Fleksy and Keedogo — in an effort to not only simply test-drive a new feature, but also to gauge the accessibility merits of the keyboards. While I’ve found Fleksy and Keedogo to be fine in terms of accessibility, even in the midst of testing them, I’ve found myself going back to Apple’s stock keyboard. In the end, that I don’t use any third-party keyboard as a replacement for the default one on my iOS devices is no fault of either developer — it’s Apple’s.

Before explaining why it’s Apple’s fault, though, it’s important to discuss the virtues of Fleksy and Keedogo.

Read more