Autism, the Internet (and Antelopes)

The second talk for Standards.Next. Jamie Knight (iMetLion.com) is a special kind of web person, he does design and development, and he does both well. See Jamie’s presentation notes and slides – I’m afraid to say I can’t remember what the Antelope reference was about, however I’m sure the Lion would approve :)

He started off by explaining from personal experience, how autism affects the way people use the web. Autism is about processing. It’s just a different way of thinking. Most people with autism are affected by changes in sensory input. For example, Jamie sometimes can’t read when there’s a background sound. So having an audio file play when your site loads is not only irritating it’s inaccessible.

Language processing can also be a challenge. When people talk very quickly he often can’t keep up. For example, when web videos cut quickly from scene to scene he finds he gets left behind, he has to rewatch them over and over. This can be stressful.

Following a theme from the previous presentation, Jamie expressed an issue with literal commands. His experience is, early in his life when asked to wash his hands ‘in the toilet’, that’s literally what he did. Subtleties in life and on the web can cause problems. For example, when adding friends in Facebook, the function performed by the site can be different depending on the context. On some pages the functionality is to simply add people who are already registered, on other pages you’re expected to enter their email addresses.

After this initial section the presentation changed format. Seeing as it seemed to have worked in the past, Jamie then struck up an interview dialogue with Henny. She posed questions along with the rest of the audience. The next bit follows that format (with a stream of consciousness thrown in).

Q. You said with video you have to rewind. This would be awful when streaming video (e.g. iPlayer), how can this be made more comfortable?

A. Captioning and transcripts. The BBC now has a nice live text captioning system using HTML5. However, sometimes he uses a screen reader when he gets stressed, Jamie explained. In fact, to help him process information he built his own screen reader using a Mac, the inbuilt VoiceOver and some AppleScript. His reader uses Microformats and embedded semantics. He built it because he uses non-sighted navigation quite often to understand a page, but can find this difficult because the visual and code order of the page are often different. This means unmodified VoiceOver can be difficult to understand. Using AppleScript he gets the website to read in the order he wants. Snow Leopard now has intelligent select so VoiceOver has caught up with what he needs.

Q. Is his screen reader source available?

A. Err… Yes but it’s hacky and built specifically for him.

Jamie is keen to break down assumptions on assistive technology, it’s not just blind people who use screen readers. With this in mind, his opinion is that web designers should not use the title attribute. He’s noticed an obsession with using nice long titles. Often web designers use title and ALT text plus the usual copy all at the same time. Jamie hears all of them. An example of this is the Amazon website. It’s really accessible with all of these attributes, perhaps too accessible.

The discussion moves to VoiceOver and any specific features that make it easier for Jamie to use:

  • Detection, one to one representation of movement on the keyboard and movement on the screen, this is new with the Mac gestural track pad.

Of note, screen readers can be too fast for Jamie. Also there are some that try to sound clear and others that go for a human voice. So which does he choose? His answer was enlightening, he chooses a human sound if the page is written in a human voice, this helps his understanding. Concatenative speech engines sound better but are less responsive. Most developers are not even aware that there’s more than one voice. One problem with VoiceOver is it can take too long to read keywords.

Q. Did he create his own presentation design?

Yes. ;)

Posted on Thursday 1 October 2009.

Posted in accessibility, apple, browsers (UA), cognitive, facebook, usability | Add a comment »

Leave a Reply