Posts Tagged ‘Applications’

Google Glass is a clear winner for the blind

Robin Christopherson, AbilityNet‘s Head of Digital Inclusion, on the accessibility angle of Google Glass:

I myself as a blind person, for example, could really do with a pair of eyes that are always looking where I’m looking and, at the same time, applying some significant smarts to what’s in front of me. OK, so Google Glass only has one eye – but one eye’s better than none believe me!

Inspiring videos edited by kid with cerebral palsy

A lovely little article from the Verge about the videos created by a young boy who has cerebral palsy:

This is Christopher Hills. He’s an Apple fan. He also has cerebral palsy, and as you’ll see in the first video below, he can’t control his muscles easily. The incredible thing about Christopher, though, is despite that, he edited these three videos himself. Not unlike Stephen Hawking, he uses a single button to manipulate his computer, which he presses with his head, connected to a device called a Discover Switch.

As well as being very inspiring and life-affirming, these videos also highlight the fact that with the appropriate assistive technology and software which is accessible, wonderful things can be created by people who are severely disabled. Remember, this is a kid who uses a single switch to work with a video editing application: technology proving to be truly empowering.

“Accessibility is not a right; it’s a feature”

This .net opinion piece by Drew Neil is the most disappointing thing I’ve read about web accessibility in a while. The central argument is based around the idea of abandoning progressive enhancement to advance the evolution of modern web apps. I’m not opposed to exploring alternative development models to build online apps — after all, web apps can be very different beasts from a traditional web sites — but Drew takes it a step too far:

The web is composed of documents, mostly the written word. Accessibility comes practically for free, but only because of the intrinsic nature of text, and the accessibility features of the software with which we consume it. Since text documents are so readily accessible, we’ve come to think that everything else should be too.

Applications and documents are different. Accessibility is not a right; it’s a feature. The first features to be implemented are the ones that define an application and determine its success.

“Accessibility is not a right”.

Really? Are we still thinking like this?

I’ve watched the web community spend years working for good standards and improved access for people with disabilities, and when I read this kind of thing it really disappoints me.

Javascript and all sorts of other emerging web technologies can work so well in tandem with progressive enhancement, providing granular and selective control over content and features for different display and input devices. Not everything needs to be implemented, not everything needs to work the same. But by excluding accessibility as a feature entirely, you exclude the people who rely on accessibility standards and progressive enhancement to navigate the online world

By taking the view that accessibility is just a feature, you’re saying that people with disabilities are just not important. In my view that’s a very dangerous standpoint.

Native iPad accessibility: is it enough?

I’m writing this on a shiny new iPad, having finally made the leap from laptop to tablet. I’m finding the experience generally wonderful & it’s certainly proving a much more comfortable and convenient way to navigate online spaces. I’ve yet to really get to grips with using the keyboard for any serious amounts of writing – touch typing is a while new learning curve – but I think practice will make perfect in the department.

One of the reasons I was keen to give this device a proper road test was to explore the accessibility features. I need to work up close a lot of the time and regularly use the built-in zoom tool on my desktop and notebook Macs. I also tend to vary the screen brightness depending on the task at hand and the lighting conditions. So seeing how I could adapt my iPad experience to make it as comfortable as I could was top of my priority list.

Being able to selectively zoom the whole screen using simple three finger gestures is great, and is a welcome complement to the two finger pinch-and-zoom functionality found in Mobile Safari. And being to invert the screen colours can be a helpful aid when contrast is making my reading or writing experience uncomfortable or tirimg.

Here’s an example to help you understand what I mean.

I’m currently writing this with the WordPress iPad app, which would ordinarily look like this:

The WordPress iPad app as it appears by default

I’ve tweaked the UI though, by switching to “White on black” through the accessibility settings – so my screen actually looks like this:

The WordPress iPad app, with the native "White on black" setting activated

It’s a simple, but really useful feature, which eases the strain on my eyes and makes for a more productive and comfortable experience. It’s not perfect though: the setting simply applies a filter to the whole screen to invert all colours. So although black on white, or greyscale interface elements like the keyboard translate well, the contrast of other UI elements is actually reduced. Just compare the “Save” and “Publish” buttons in the top of those previous screenshots for an example of what I mean.

These little quibbles are bearable when it’s just text-related content, but it becomes a very disorienting experience when it comes to using apps which feature more graphical and illustrative elements. Browsing my Twitter stream, as an example, shows everybody’s avatars in a strange, inverted x-ray fashion:

The iPad Twitter app, with the native "White on black" setting activated

Notice too that because the whole screen is inverted, the subdued dark background which frames the central stream is now hemmed in by two large zaps of light, which detract from the high contrast of the main content.

Page zooming is also great in many situations, but starts to have failings when it comes to creating content, as opposed to just consuming it. Using the WordPress app as an example again, the very clever screen zooming can start to prove cumbersome. The default text size in the app is pretty small, and can’t be changed. Ideally, I’d prefer to be able to zoom in on it while I type – look what happens though:

The WordPress iPad app using the native Zoom controls

Because the entire screen has been enlarged, the keyboard is now practically unusable. So, I just have to guess-type and proofread later on.

Of course, these are just restrictions of these particular assistive tools, and I’m trying to push them beyond what they were designed for. They’re assistive, and can’t be expected to fix the varied needs of different users for every application – one size doesn’t fit all.

But I think it does highlight the number of mainstream apps which are being developed without the consideration of simple, adaptive accessibility features.

Perhaps that’s because Apple have done such a good job of implementing OS-level accessibility: developers don’t see the need to worry about it, safe in the knowledge that at least a basic level of access will be baked right in. I also suspect that in some cases, it’s due to a certain amount of preciousness over pixel-perfect design treatments (and if you remember the terrible trend for pixel fonts on the web at the turn of the century, you’ll know just what kind of route to hell that can lead you down).

But I think it’s important for developers of these apps to consider extra features which allow users to adapt their experience to suit their particular needs or preferences. Simple things like allowing users to choose text sizes, change colour palettes, adjust white space and remove clutter are all simple and effective ways to allow more granular control, enabling the user to adapt their experience so that it’s more comfortable and enjoyable.

Twiiter for iPad is just one example of an app which could quite easily be improved in this respect. Twitter for iPhone allows me to change the font size for tweets throughout the app; but the iPad app is missing that feature, and I would really like to have it. It wouldn’t compromise the design of the app, but with that one simple feature, it would allow me to enhance my experience while using the app.

This post was prompted by the fact that I was considering a purchase of the iA’s Writer app, which is an absolutely awesome distraction-free writing application: simple, elegant and impeccably designed. But when I was trying to find out more about it, I noticed that all of the screenshots showed black text on a White background. I wanted to know if the app supported a setting for white text on black – I really don’t want to spend lengthy periods of time staring at so much whiteness.

Turns out that it doesn’t have that feature, but I bought it anyway because I can use the “white on black” setting built in to the OS – despite it’s annoyances.

But why not include that feature? Why should I have to use generic assistive features when more granular, app-specific settings would do a much better job? The lack of this kind of feature was almost a deal-breaker for me, but when I considered the alternatives, I decided that iA Writer was best-suited to my approach to working, even with the clunky white-on-black compromise.

But I think that summarises my point quite nicely: why compromise? Despite all of it’s little idiosyncrasies and faults, The iPad is a wonderful, enabling device. But I wonder if a lack of imagination amongst the developers of its apps might be stifling that enabling power for a huge number of people looking for a more assistive experience?

Notes

  1. I’m not singling out the iA Writer app for criticism here – I think it’s a wonderful application. I’m just using it as a real-world example of where I’ve had a desire for a feature which would improve my personal experience of their product. And the iA team were very forthcoming with feedback when I contacted them about it on Twitter.
  2. While writing this post, I found that the WordPress app was just too cumbersome and buggy for serious writing, and so switched over to using the iA Writer app in earnest instead. It proved a much more comfortable experience, and the default font size is just perfect for my needs: not too small, not too large. The distraction-free approach really does suit the iPad’s form factor and will prove to be particularly beneficial for many disabled users who are overwhelmed by the usual breed of text editors.
  3. As I’ve written previously, when considering accessibility features, it’s not just disabled users who benefit. Thinking of accessibility as something which only helps people with disabilities is very misguided.

Developers don’t rush to new platforms

Great analysis from Marco Arment about the misconception that developers will instantly flock to a new platform:

A common fallacy is assuming that any new platform in an exciting market — recently, smartphones and tablet computers — will be flooded with developers as soon as it’s released, as if developers are just waiting outside the gates, hungrily waiting to storm in.

In two recent cases, that’s exactly what happened: the iPhone and the iPad. (And probably the Mac App Store next.) So important people, including the tech press, consumers, and many hardware manufacturers themselves, assume that every new hardware platform will be greeted with the same rush of high-quality software.

It’s really worth reading the full article, which proposes that the iPhone and iPad development ecosystem is thriving so much for three reasons: dogfooding, install base and profitability. And he concludes with this question:

Now, consider this fall’s tablet computers. Can you say with confidence thatany of them will address these three needs well enough, and for enough developers, to ensure a steady supply of quality software?

Khoi Vinh on iPad magazine apps

Khoi Vinh on the rush of publications hitting the iPad:

My opinion about iPad-based magazines is that they run counter to how people use tablets today and, unless something changes, will remain at odds with the way people will use tablets as the medium matures. They’re bloated, user-unfriendly and map to a tired pattern of mass media brands trying vainly to establish beachheads on new platforms without really understanding the platforms at all.

The fact of the matter is that the mode of reading that a magazine represents is a mode that people are decreasingly interested in, that is making less and less sense as we forge further into this century, and that makes almost no sense on a tablet. As usual, these publishers require users to dive into environments that only negligibly acknowledge the world outside of their brand, if at all — a problem that’s abetted and exacerbated by the full-screen, single-window posture of all iPad software. In a media world that looks increasingly like the busy downtown heart of a city — with innumerable activities, events and alternative sources of distraction around you — these apps demand that you confine yourself to a remote, suburban cul-de-sac.