Hawking toolbar.

I just discovered this fantastic little application for FireFox that helps people with severe mobility impairments. Historically, switch access users haven't been able to get to the toolbar of their browser without help from someone else, so even simple actions like using the 'Back' button have been impossible. One of the best tools on a website for this group of users is the breadcrumb trail which helps them navigate back to points in their browsing history, but many sites don't feature these and may leave some users a bit stuck.

The Hawking toolbar allows some simple controls to be available to the user including the essential 'Back' function. It's free to download and has some really useful features such as grouping links based on proximity to each other and switching between groups rather than tediously highlighting each individual link. It will then switch between links in that group. Very neat.

You can find out more about the toolbar from the Oatsoft website.

While we're talking about tools for people with mobility impairments, I noticed Karl Dawson posted a link that he found which featured people using software called 'Keystrokes'. There's a whole bunch of videos on there that are mind boggling. I never imagined that you would be able to play first person shooters with only your thumb but you can, and people do.

Text size widgits - quite useful actually

I think the accessibility community has become bored of late. Sites are getting much better, code is getting much cleaner and that leaves us twiddling our thumbs a bit.

But recently there's been a fair bit of discussion over text resize widgits over at 456Berea St. Popular opinion has it that these widgits are not only unnecessary but harmful in that people come to rely on these widgits rather than find out how to resize text in the browser.

This argument baffles me. I hear "Teach a man to fish..." but I don't think that's a good analogy at all. We have to accept that some people will never learn to fish; either because they can't or they don't want to. If they don't want to, who are we to say that they have to?

Those who can't/won't may include:

1. People who are mobility impaired, particularly those using switch access
   
2. People who have learning difficulties


3. People with cognitive disabilities


4. People who won't realise the benefit until someone has actually shown them
   
5. Infrequent web users


6. People who aren't confident with technology

I think the last group mentioned here is probably the group that technologists often don't understand very well and have little empathy for. It includes many who are elderly and who are learning about technology later in life. It also includes those who just aren't confident period. I was in a room the other day talking with a colleague and there was a tiny tap on the door. Not sure we'd heard anything at all we kept talking until the door opened slightly and someone shyly and quietly asked something. Not catching what she said the first time I walked to the door and heard her ask "Is this the confidence building class?" I'd never heard of such a thing and was humbled at the thought of it. Naturally I helped her out the best I could and didn't feel inclined to slam the door on her fingers and tell her that she should have been better prepared.

Don't get me wrong, showing people how to resize text in the browser is a great feature. Those who can learn how to do it may benefit enormously. But not everyone will or can learn, and I don't think it's for the designer or developer to say that they have to. It is only their responsibility to make sites accessible and usable.

In summary I'd like to say that both approaches are sound and it's fine to use either (or both). I just don't understand why anyone would say that either is a waste of time.

Update: I meant to post a link to Ian Lloyd's "Teach a man to fish..." demonstration. My esteemed colleague has produced a very nice video demonstration of how to re-size text in a browser.

Hello again.

Apologies for the long absence, a lot has been happening over the past couple of months, it's been holiday season, so I took a holiday, very nice it was too, and also I have a bit of news:

I became freelance.

I'm officially my own man and this allows me to explore some new ventures. I'm still working closely with CDSM who are still in my opinion the best corporate accessibility specialists in the UK, even though they are focussing more and more on e-Learning and continuing to break new ground there. I'm also still very much in touch with the Shaw Trust who, in partnership with CDSM still produce the most comprehensive accessibility testing service in the world. So I'm very lucky in that regard.

I've been talking with Jim Byrne about being more involved with GAWDS and also to a few other individuals about another venture.

I've also got a book coming out in the new year.

Web accessibility is still at the heart of everything I do and plan to do in the future. It's exciting times.

Voice Activation and Flash

Just a quick one, I just thought I'd post a note for accessible Flash developers regarding Voice activation software. Not everyone has had the chance to test using this software so This may be helpful to a few.

Flash applications are typically tricky terrain for Voice activation users (think Dragon Naturally Speaking (DNS)). The most common voice commands for HTML pages such as "link" and "image" don't work. In HTML these commands will identify the links or forms on the page and put a little number next to them. By speaking this number you can follow the link or activate the form control. Neat.

Flash reveals the controls via MSAA but Dragon does not seem to have a method of displaying them accurately yet. In fact it seems to struggle with matching links with numbers in simple CSS.

For the time being voice activation users can either rely on the mouse grid method of navigation (very slow) or spoken keyboard commands such as "tab" and "enter". this allows the user to methodically move through the Flash controls and as Flash doesn't tend to have so many links etc. this should be fine. The one thing I haven't been able to test with the guys at the Shaw Trust yet is whether DNS is capable of accessing Flash controls that are "below the fold" either because of a browser scrollbar or a Flash scrollbar. Once I get that info I'll pass it on.

Sorry for the lack of detail/illustrations but I just wanted to share this info before I forgot all about it. If you want some clarification feel free to leave a comment or send me a mail.

Real World Accessibility

Following the success of their last event of the same name, Public Sector Forums are running a second event which is designed to highlight practical considerations for providing accessible web sites.

The event will include all the original speakers, so I’ll have the pleasure of once again sharing the platform with:

Bruce Lawson
Anne McMeekin
Patrick Lauke
Dan Champion
Ian Lloyd

Dan Champion has some more details including presentation overviews up on the Champion Internet Solutions website.

The event is organised by Public Sector Forums, but it is open to anyone, public sector or otherwise. All are welcome.

I’ll be tackling the accessibility of PDF, GIS, Flash, and I’ll be providing some guidance on how and when they should be used. Between us we'll be tackling a diverse range of practical accessibility considerations.

You can read more about the event on the Public Sector Forums Website and you can use the booking form to reserve your place at the event. Oh, and make sure you give me a mention when you book because everyone who doesn't will get a sloppy kiss from Bruce Lawson. So don't forget (unless you're into that kind of thing).

Defining Keyboard Access

Back in May I attended a Becta event which launched their"Making Software Accessible" guide. I also wrote a blog entry that covered the Becta event.

I was pleased to see David Colven from the Ace Centre presenting. David brought along some short video clips that illustrated the need for single key access for some applications.

These videos left quite an impression on me as they illustrate so very well how important technology has become to overcoming physical impairment, and how easy we can miss things if we don't take a holistic view. It's easy for us sometimes to limit our concept of "access" to filling out an online form or navigating a web page, but these activities only represent part of what we can achieve with our computers.

The videos feature Peter Harris. He was 14 at the time these videos were taken. Peter wanted to draw, and In the first video he has been given a drawing package and a mouse to try:



In the video, you can see how Peter struggled with the mouse interface. He produces a picture, but it's not what he had intended. So the guys at the Ace Centre looked to keyboard control to overcome Peter's Athetosis.

The next video shows Peter using a specially adapted keyboard that has a mask that helps to prevent multiple keys being pressed accidentally. But Peter's posture suffers because of the position he needs to be in to be able to press 2 keys simultaneously:



Again, the results aren't what Peter had hoped for.

In this last clip, the guys at Ace modify the package so that it can be used with just a single key press. Basically it's space to start a line, arrow keys to move, and space again to finish.



You can immediately see that the results are much better. Peter lived on a farm and really enjoyed farm machinery. With a little patience, Peter was able to produce the following drawing of a Landrover:

When I saw this on the screen I was amazed. Having seen what Peter had produced previously, I did not expect him to be able to draw like this. But Peter's results where limited not by his own ability, but by the limitations and inflexibility of the tools he previously had access to. In response to Peter's specific needs, the practitioners at the Ace Centre provided him with a method to produce this wonderful drawing.

Summary:
People's experience with disability differs a great deal. I'm quite privileged in being able to work so closely with the team at the Shaw Trust as part of my job, but even so, these videos really opened my eyes to the way we as a community tend to think of disability and technology. Particularly:

1. We're often guilty of categorising disability in our approach to accessible services in using terms such as "keyboard accessible" without truly considering the different modes of operation.


2. We often limit our idea of access to standard applications, web pages etc. We need to give more thought to improving enjoyment of life through technology. A new approach can lead to someone discovering in themselves a new skill and enhance their lives.


3. Giving people access is not the same as providing people with an equal experience. It's the latter that we need to focus on.


4. On the web, there's too much emphasis on the limitations of User Agents. Yes, it's an important aspect that needs to be considered, but If the guys at the Ace Centre thought "Oh, this package doesn't offer single key operation. What a shame." Then maybe nobody would have found out that Peter could draw.

I'd like to thank David, Peter and the Ace Centre team first for introducing me to these videos and allowing me to use them on this blog.

The software that Peter is using was developed by the Ace Centre. It's called AccessMaths 4.2 and, as the name suggests was actually designed for teaching Mathematics.

WCAG Samurai Errata released

The WCAG Samurai are a mysterious team of web accessibility warriors (mysterious because nobody is supposed to know who they are) led by Joe Clark. The purpose of this secret group was to write an Errata for WCAG 1.0; the oft quoted, but well worn guidelines for web accessibility that have been around since 1999. Joe's contention is that there is no need for WCAG 2.0, largely because the whole process has been dominated by industry and that with a few tweaks here and there, WCAG 1.0 + Samurai is all that is needed to assure accessibility.

Well the first draft of the WCAG Samurai Errata is here.

The process of developing the Samurai errata has been going on over the past year and the draft errata were released at last week's @media event in London.

The Review
There are already a number of reviews popping up as people have found the time to read and review. There were two peer reviews requested by the Samurai:

By Gian Sampson-Wild
By Alastair Campbell

A few more can be found by:

Steve Green
Mel Pedley
Joe Dolson
It only matter is you care
Roger Johansson

...and I'm sure that a few others are being written at this very moment.

The reviewers tend to agree on most things, particularly the overly optimistic dependence on User Agents to get it right (when we know they don't). This is a big problem throughout the Errata as the only people that will lose out because of this poor postulation are the very people that it is designed to help.

Counter productive?

On the whole though, the document is pretty good as it contains some very detailed and practical advice on the treatment of video and audio content. These parts alone make the document a worthwhile read, and I hope that the guys behind WCAG 2.0 are paying attention.

Now while Joe has been quite vocal about WAI and WCAG 2.0, I can't help thinking that there's a little too much WAI bashing in the document itself. Some of the info is useful, but has a deliberate contrary tone. While this makes for good reading, it's not so good for a standards-type document. It tends to leave me wondering whether parts of it are simply based on good practice, or whether it's just a snipe at someone. Additionally, there is an overly sympathetic tone used towards PDF production which probably sprouts from Joe's personal involvement with the PDF/UA Universal Accessibility Committee

There's also a blanket bombing of Priority 3 requirements, which as Steve Green points out in his review includes Checkpoint 2.2:

2.2 Ensure that foreground and background color
combinations provide sufficient contrast when viewed by someone having color
deficits or when viewed on a black and white screen. [Priority 2 for
images, Priority 3 for text].

And also includes the abolition of access keys, something, that I've been fighting hard against based on the fact that I work with people who find access keys useful (a discussion for another time). But the point here is that the errata are very black and white (deliberately) but some shades of grey need to be thought about more carefully.

There are lots of other things I don't agree with, most of which have already been pointed out by others but there is one item though that sticks out as a really, really bad piece of advice:

Do not cause pop-ups or other windows to
appear and do not change the current window without informing the user. (Plain
text is the preferred method of informing the user. The title attribute on a
hyperlink a element can suffice.)

A couple of things,

1. The title attribute should NEVER be relied upon to convey any information. EVER


2. "Plain text" rather than "The link text itself" is no-where near enough to inform a user that a link is about to open in a new window.

Steve Faulkner, comprehensively covers the issue in his presentation "The Title attribute - what is it good for?"

I'm surprised that Joe et al feel that title is an adequate device, or perhaps it is seen as a UA issue (which it is not, the issue is far more complex and involves many different considerations including work flow, usability, and modes of activation - a topic for another time maybe).

Political impetus
There's a bit of a space race on at the moment, the community is waiting for a set of workable standards that before the last draft, WCAG 2.0 looked like it was going to fail to deliver, since then, WCAG 2.0 has had a fairly positive reception, although it still has a way to go, it seems to be at least heading back in the right direction. I'm sure that both parties are keen to get their documents out first. I do believe that it's unlikely that the Samurai Errata will get much attention if a workable WCAG 2.0 is released ahead of it. Apart from a few die hard fans, I can't imagine many sites sporting a WCAG + Samurai logo. So early adoption at this stage seems to be the errata's best hope.

Conclusion
I'm glad that the Samurai's errata has been written, It provides a lot of very useful information that can't be had via WCAG 2.0. The style of writing is refreshing and it's an alternative to WCAG 2.0. I'd encourage those that are new to accessibility to read it as it contains so much useful advice, I'd go as far as to say that it will probably help me to form a clearer opinion on some things, particularly where sound and video are concerned, although I'd also feel inclined to point out that the tone of the document is a little political and opinionated and therefore needs to be read with some caution.