Accessibility update

Here’s a quick update of the main open accessibility activities that are on my radar. Do drop me a line if any are of interest to you.

This has been a very busy time, especially as our new company [pre]activity takes off (more soon). I’ve not been so closely active with Mozilla and GNOME lately, but am keeping a keen eye on the interesting activity in both of these key open accessibility projects.

Electronic ciruit board wired up to a joystick controller switch
Teckla shield connected to a joystick

The big story at the moment is proposed submission of the Open Office code by Oracle and IBM to the Apache Incubator. The frantic flurry of discussion has quietened down a bit and the vote is now on. As far as open accessibility is concerned, having the OOo code in the incubator has great potential in fostering collaboration between the many interested parties. Not only does incubation develop community diversity and strength, but the use of the permissive neutral Apache licence enables engagement by all, including those interested in commercial use. This is important given the number of derived works (see the proposal link above for a chart). Thus, for example, both IBM and LibreOffice will be able to use and contribute to the core code (if they so choose). One possible benefit that’s been mentioned is the contribution of Symphony’s more mature IA2 api implementation, allowing for example, NVDA screen reader users to use OOo without sighted assistance. In addition Apache could offer a good home for the various a11y add-ons to OOo such, as those from AEGIS project.

Project Realise is nearing the end of the JISC funded period and the web site for encouraging open innovation in accessibility software is up in prototype form. As it stands it has a way to go to fully support the vision of mentoring projects to the point of open innovation through maturity in open development, but after a workshop and debriefing, many of the critical ‘people’ focussed features should be soon appearing.

The Mulberry symbol set from Straight Street has surpassed 3,000 symbols and we’re working on partner support and internationalisation with a crowdsourcing element.

Maavis simplified access to media and communications is progressing steadily, with various possible uses and collaborations being investigated. There was considerable interest generated by the Mail article with Sylvia Syms, including some commercial. One of the top priorities is to replace Skype with something that transparently does video calls without getting in the way. We’ve also be thinking about a web version. What’s interesting is that since we started the approach to consumer interfaces has rapidly embraced simpler touch interfaces, thus making it easier to implement Maavis features.

Portable accessibility of and through web apps and widgets is fast becoming very interesting indeed. Rave in Context is creating widget templates, Tekla is providing switch access via bluetooth. Both Straight Street projects and Maavis are also heading in this direction. Tablet apps are being enthusiastically snapped up at grass roots by end users and their supporters as a way to provide low cost innovative AT need solutions. This self-service is proving disruptive in the AT provision services, and raising some serious questions. Open development of web apps can have a big impact here, especially in portability and quality.

On the European front, the eAccess+ and ATIS4All thematic networks are active and spreading knowledge. Another large project to implement some parts of the GPII vision is under review by the EC and we hope will receive funding soon.

Finally, in events, I’m excited about the DevCSI & Full Measure a11y hackday that will take place on the 21/22 June. I hope we’ll see some interesting hacking and collaborations happening. We’ve certainly got a great mixture of people registered, and excellent keynote speaker in David Banes, Sandi Wassmer and Julian Harty. I’ve ordered a Tekla prototype from Komodo OpenLab and hopefully it will arrive in time for us to play with it.

Upgraded to HTML5 themes

I just installed Richard Sheperd’s TwentyTenFive HTML5 version of the default WordPress theme and Sylvia Egger’s Accessible Five accessibility enhancing child theme.

There was a slight glitch with the name of the TwentyTenFive folder name having changed, but all seems well now after I renamed it back to ‘TwentyTenFive’.

We can just hope these both quickly make into WP core. Especially as there was a recent call for WP accessibility contributions.

Safari tab key navigation disabled by default

For some bizarre reason tab key navigation is turned off by default in the Mac Safari web browser. By this I mean hitting the tab key repeatedly does not visit each interactive element on the page.

This lack is a pain for keen keyboard users as it’s the only guaranteed way to access all links and form elements. Even if  websites were to apply the AccessKey attribute to all links and fields, browsers in general do not provide a way to discover what allocations have been made. Browsers do provide a useful default tab order, assuming the HTML markup has a reasonable element flow.

Another group of users that need tab key access  are users of simple alternative input like switches. The overlay assistive technology that such users often use translate simple gestures into tab and enter key events, thus allowing access to most of the web app doc. This is slow and painful in many cases. especially if the tab order is not well designed. However it does provide access. The common exceptions are any ‘clever’ javascript custom controls that forget to provide any keyboard access, assuming pointer only is used. This is more common than it should be and is yet another good reason to use an established accessible toolkit like jQuery UI , Dojo or Fluid Infusion for your web app.

Screen reader user also benefit from tab navigation, though screen readers provide do more useful ways to navigate the screen. For example they can list headings (assuming the document has been well structured, as screen readers can’t work miracles).

So I wonder why this is turned off by default? I use Firefox as my default browser on my Mac Book Pro, but when setting up this blog I ran Safari for a quick test of a guest user. I used the tab key to check the Accessible 2 sub theme was doing its stuff. It was broken and tab skipped straight to the search box (the first form input element), missing all the links.

There has long been an option in system prefs – > keyboard that enables tab to all fields, but even though this was on I had no joy. Eventually after a twitter discussion, I stumbled across a new (?) similar option in Safari -> Prefs -> Advanced that also need to be turned on in order to enable basic tab navigation.

Does anyone know the logic for having tab navigation turned off in Safari by default? I’m guessing someone with influence had an issue of some sort. In Windows and Linux, tab navigation is a fundamental of any UI whether it’s a dialog or an app. HTML5 allows any item to be focusable either programmatically or by the user. So having tab navigation off is a bad move.

Back in the blogsphere last

So I’ve finally set up a new blog to replace that which was lost when EduSpaces pulled the plug on the old Elgg community where I hung out. I should have moved on anyway given my focus is now open accessibility, whereas at that time I was working in education (Exeter College MIS). Unfortunately my blog export turns out to be corrupt so it will be some time before I can resurrect some of those old posts.

Since then I’ve been pretty active on Twitter as @SteveALee and whilst being socially powerful, doing so really depletes the blogging muse. Still at times there is more I want to say than can be pared down to fit the lean and mean 140.

I also work  for UK JISC funded FE/HE educational advisory service OSS Watch and I occasionally blog there as well.

So now I’m all set to go. I had intended this to be a Drupal blog, partly to gain familiarity with the excellent CMS with a view to using it for a refresh of fullmeasure.co.uk, and partly as the Drupal Accessibility community are doing great things, many of which have landed in Drupal 7.  However, my otherwise excellent and open source friendly hoster, UKFSN are still using a version of PHP that is too old for Drupal 7. So for now I knocked up a quick WordPress install. It’s such an easy out-of-the-box blog setup and it’s fresh in my mind as I’ve just used it for a couple of websites for a client.