Apple and balance/motion accessibility — yelling into the wind

As a writer, even in an age of social media, it’s hard to tell whether anything you pen affects people in any serious way. In truth, much of what I write is opinion-based: thought pieces and reviews that might briefly help and/or entertain a certain section of a site’s or magazine’s readership, but that relationship between words and results is typically fleeting.

One major exception in my writing career centres around accessibility. When Apple’s iOS 7 for iPad and iPhone arrived, it made a lot of people sick. Aggressive animations became motion-sickness triggers for a surprisingly large range of people. I was fortunate enough to write about the subject for Stuff and twice for The Guardian. Apple rumbled into gear. Changes were eventually to iOS made via the introduction of Reduce Motion, which switched slides and zooms for cross-fades. I have it on good authority that what I and others wrote did have an impact on Apple’s decision-making.

Although motion/balance accessibility remains poorly understood, and third-party developers remain largely ignorant of these issues, merrily peppering apps with animated interface components, I and others are now broadly safe when using iOS. The same is not true for OS X. It’s been three years since I first wrote about the subject on this blog, and I’ve penned articles elsewhere, including for major tech publications. It’s hard to believe that Apple’s listening. The company, despite making great strides in vision/hearing/motor accessibility, appears either ignorant of or uncaring about motion/balance problems.

That might seem like an extreme statement, but I think it’s entirely fair. Major triggers, such as full-screen slides/morphing transitions, and also slide transitions within Preview and Safari, arrived in OS X Lion, and we’ve since seen three major updates to OS X without a single setting for overriding these animations. There’s no Reduce Motion in OS X, despite Mac screens being larger than iOS ones, which means the transitions displayed are more — not less — likely to cause problems.

Today, I fired up the new OS X Photos app. Within five minutes, I felt ill. I shouldn’t have been surprised that a motion/balance trigger is built right into the interface, with the main pane zooming while it crossfades. Presumably, someone at Apple thought this looked pretty. There’s no way to turn it off. For anyone who finds this animation problematic, their choices are to avoid Photos entirely or remember to close their eyes every single time they click a tab.

This is just not good enough. Apple is a company that prides itself on making its technology accessible. Given that a somewhat throwaway setting in a third-party utility can override or entirely disable the majority of full-screen animations, it’s hard to believe Apple couldn’t fit a Reduce Motion system into OS X if it wanted to. If developers could hook into that, most motion/balance issues would disappear in an instant, without affecting the majority of users, who could happily continue watching interface components zoom about before their eyes.

As I wrote today in an email to accessibility@apple.com, I’m sick of the current situation, figuratively and — in a fortunately fairly mild way — literally. Highly animated interfaces may be the ‘in thing’ right now, and sometimes have potential benefits in providing a sense of place; but that doesn’t mean Apple should overlook people for which these often aesthetic additions cause major usability, accessibility and health problems. I’ve no confidence anything will change. Every email sent feels like yelling into the wind, but I’ll be delighted to see and experience a change in direction should that happen in OS X Yosemite’s successor.

April 9, 2015. Read more in: Apple, Opinions, Technology

No Comments

Apple Watch is the worst thing ever, and here’s why

Yeah, sorry about that link-bait title, but I figured I’d best get in on the current wave of tech stupid before my tech journo credentials are snatched away from me. Mind you, perhaps escaping would be a smart move while the majority of the industry loses its collective mind.

I mentioned tech writers tending towards bile last week, but the latest stick to smack Apple with appears to be the accusation that the company has lost focus and no longer understands the value of simplicity.

Jason Hiner’s piece for ZDNet is fairly typical of this latest raft of Apple Watch moanery, calling it “too ambitious” and “a bit of a mess”. He argues:

the fact that Apple released the product in its current form says something. In fact, it says a lot about Apple under the new leadership regime because it’s the first new product category of the Cook-Ive era. And as far as innovation and discipline goes, this is a wobbly start.

His core complaint seemingly revolves around a belief that all Apple products start out simple and then layer greater functionality as they evolve. He’s right that Apple builds on products (notably software, adding richer features) over time, but what is simple?

For Apple Watch, Hiner complains that the device tries to do too much and that there are a load of new functions for a user to figure out, which are

unlike any other Apple or tech product so they aren’t naturally intuitive.

But what is intuitive? What is fully natural? My dad recently admitted to me he’d never used copy and paste, and he’s been using Macs for well over a decade. He’d just been dragging selections around, muddling through. With Watch, you imagine quite a few people will do something similar, perhaps chancing across functionality. Others will dig deeper. But the point is that many pieces of functionality that tech pundits consider simple and natural are only so to them because they use these things every day.

Consider the mouse and the original Mac. Back then, the windows/icons/mouse/pointer interface wasn’t unique, but it certainly wasn’t commonplace. Then there’s the iPhone, with its gestural interface that had a fair number of elements that felt natural, but also elements users had to learn, in order to access all of the device’s functionality.

Of course, people slammed those things too, saying they’d fail, because that’s what you do with Apple. And perhaps Apple Watch will be a faceplant, but I think the tech industry would be a better place if writers actually started to spend a bit of time with kit before deciding that it was a waste of time, a mess, or too ambitious. (And you can bet that had Apple released a much more locked-down Watch, with a razor-sharp focus and far fewer functions, ZDNet would have been whining about Apple’s closed nature, and how the device was a rip-off for the few things it enabled you to do.)

March 16, 2015. Read more in: Apple, Opinions, Technology

3 Comments

Maclash: the unfortunate modern tendency of tech reporting to spew bile rather than inform readers

Regular readers of Revert to Saved — and indeed my other writing — will be well aware I can be opinionated. But something I aim to do — even here — is ensure snark and rants are underpinned by facts and reason. Of late, it appears tech reporting has vanished down a rabbit-hole of link-bait madness.

On watching Apple’s latest event, where it unveiled the new MacBook, more details about Apple Watch, and my personal favourite new Apple thing, ResearchKit, I knew people would fire up their gripe cannons. I just wasn’t entirely prepared for how far they’d go.

First came a piece in the Guardian, where Hannah Jane Parkinson helpfully suggested that “only a tool would buy the Apple Watch”. The feature’s clearly open-minded approach defined, she went on to offer a load of ridiculous interpretation, spin and FUD about Apple’s new product that reminded me of the kind of garbage you’d read on a mindless Apple blog, rather than a supposedly respectable publication like The Guardian.

Next, TechCrunch’s Matt Burns referred to Apple’s new MacBook as the company’s “latest betrayal”, because Apple has had the audacity to do what it’s done only loads of times before and omit what it considers soon-to-be-obsolete technology. If anything, the piece injects even more stupid sauce into the mix than The Guardian’s. Gems included arguing the new MacBook has “more in common with a tablet than most laptops”, and the ridiculous suggestion the Intel chipset inside the machine “likely doesn’t provide enough oomph to play computer games, but it should render GIFs just fine”. Ooh, you BURN, Burns! Plus that will come as a shock to all the professionals I know doing highly complex work on older and far less powerful Mac notebooks.

As the internet and tech coverage evolves, it feels like we’re witnessing a shift from survival of the fittest to survival of the inane. Pieces more often resemble personal soapboxes, omitting facts to fit agendas, and punching intelligence until it’s bloodied and broken. This does readers a disservice, and should be left for personal blogs.

March 11, 2015. Read more in: Apple, Technology, Writing

No Comments

We’ve already paid $billions

Barry Collins has written a piece for Expert Reviews on Björk’s reluctance to release her new music on Spotify. She says it simply doesn’t feel right to essentially give away something you’ve spent years working on. It’s a point of view that aligns with my own, and while revenue from streaming services is better than nothing, there are plenty of reports online that showcase how little bands and artists actually receive from the likes of Spotify.

Naturally, Spotify itself was bullish in response. CEO Daniel Ek argued:

We’ve already paid more than $2 billion in royalties to the music industry and if that money is not flowing to the creative community in a timely and transparent way, that’s a big problem

So it’s the fault of the labels in not getting money to artists, apparently. But what stood out to me more is the figure. Apple plays this trick too: talk about the BILLIONS that have been paid out, but entirely remove the context. A billion sounds like a lot when you’re talking about US dollars, Sterling or Euros. To the individual, a billion is a lot. But when that amount is divided up among every artist or developer on a service, across the entire amount of time the service has been running, a swift bit of maths leads you to a very different conclusion.

March 2, 2015. Read more in: Opinions, Technology

No Comments

Access all areas — why even Apple needs to rethink regarding accessibility

The recent Flipboard discussion and my ongoing issues with OS X Yosemite and accessibility brought to mind a piece I wrote for the dearly departed MacUser last year. It’s still very relevant (sadly), in part relating to major accessibility issues I’ve been writing to Apple’s accessibility team about since 2012, and so I’m republishing it here.

 

Apple might be a tech champion when it comes to accessibility, but it still has blind spots and a propensity to frustrate by using accessibility settings as a fix for contentious design

Perhaps the most laudable goal throughout Apple’s history has been a desire to make its products accessible to everyone who wants to use them. A combination of technological leaps and advancements in understanding wider user needs has resulted in astonishing accessibility controls lurking at the heart of OS X and iOS. Chances are, if you’ve poor vision, hearing or motor control, you’ll still be able to use Apple’s products. Given that you interact with an iPhone by pawing at a pane of glass, it’s quite something you can do so even if you’re unable to see the interface.

But for all of Apple’s success in terms of accessibility, the company still has work to do. It stubbornly retains an odd and frustrating tendency to erect barriers that make the going tougher than it needs to be for many users. It’s unclear why this is the case, but recent changes to iOS and OS X suggest a combination of ignorance and arrogance.

With iOS, Apple created a mobile operating system second-to-none when it comes to accessibility. A quick glance at relevant options in the Settings app compared to the equivalents in vanilla Android show just how far ahead Apple is. And yet when iOS 7 appeared, many users found it made them feel sick and dizzy, because of excessive zooming and swiping animations that could not be disabled; others complained of headaches, due to the brighter, starker interface.

On OS X, similar balance/motion concerns have existed since OS X Lion, and elsewhere the ‘iOSification’ of OS X has introduced further problems: ditching scroll bar arrows has made things tough for some people with motor issues; the upcoming OS X Yosemite includes transparency that dramatically reduces contrast for many interface components, bringing to mind ‘trendy’ (i.e. unreadable) grey-on-grey early-2000s web design; and several updated apps boast toolbars with tiny hit areas, meaning they can only be dragged if you have the dexterity to precisely aim and grab.

But perhaps the most disturbing trend is Apple’s inclination to seemingly use accessibility settings as a kind of band-aid for questionable and divisive design decisions. Not happy about iOS using a spindly font? Change that in accessibility! Hate the fact you can barely read menu items in OS X Yosemite’s dark mode? Change that in accessibility! And so on.

It’s hard to argue Apple should adjust the default state of everything that could potentially reduce accessibility. The swooping, zoomy nature of iOS 7 provides a sense of place if it doesn’t make you throw up, and Yosemite’s revamp has generally gone down very well (at least with anyone who’s forgotten about Mac users laughing at Windows Vista’s transparency seven years ago).

However, if Apple won’t make smarter design decisions and avoid giving into the temptation to sometimes push the shiny over the usable, it should make the means to adjust irksome pain-points more readily available and not bury them in a System Preferences pane or Settings section relatively few people are aware of. For remaining issues, Apple must be faster to address concerns. It’s great iOS now boasts a ‘Reduce Motion’ option, but unacceptable OS X doesn’t after several major revisions, nor properly old-school scroll-bars for those who truly need them.

If accessibility is a checklist, Apple still ticks more boxes than most, but the list is huge, and some of Apple’s nagging reminders date back to 2011. It’s time ‘access for all’ really meant that, especially when the changes would barely affect the majority yet improve the OS X and iOS experience for many thousands of people beyond measure.

February 18, 2015. Read more in: Apple, Opinions, Technology

Comments Off

« older posts