The accessibility of the interface is just as important as the accessibility of the code the editor outputs. The key aspects to focus on are the ‘perceptability’ of controls (e.g. alt text) and ease of using a keyboard only.

After releasing another website accessibility survey (this one global in nature), the topic of ‘reporting’ on accessibility issues has come up again. Frankly I don’t think there’s a right answer, but if anyone can think of a better method, I’m all ears.

Recently I noticed that Google will be supporting audio as well as visual CAPTCHA tests. This is so that those who can’t see the screen can listen to a sound clip and fill in a code to prove they are human. Given the more effective alternatives, why is Google taking this approach?

Each of the editors I’ve been looking at allows the addition of tables, but none of them allow the easy insertion & manipulation of a data table, i.e. one with headings. I deal with data tables quite a lot for windsurfing results, and the only program I’ve found for decent table editing is Dreamweaver.

At this stage, fund raising to allow fund raising! Joe Clark is starting the Open & Closed Project, dedicated to writing a set of standards (how-to manuals) for four fields of accessibility – captioning, audio description, subtitling, and dubbing.

There are several options available for increasing the apparent size of web pages, from simple increases in text size, to full screen magnification. Focusing on browsers, I’ll examine what options suit different people, and what implications this can have for web development.

Adding images in an easy and accessible way is a vital part of a modern WYSIWYG editor, and one of the things the almost all of the implementations I’ve come across get wrong. There are several levels of implementation, from adding images from other locations, to creating and choosing from a library of images and other assets.

The Roadmap for Accessible Rich Internet Applications (ARIA) outlines the technologies to map controls, AJAX live regions, and events to accessibility APIs, including custom controls used for Rich Internet Applications. This post just draws attention to things I (and Iperhaps other people) could do with some further explanation on.

There was a question on the Voiceover list recently about links just being read out as ‘link’ on a particular site: freeverse. It turned out to be due to an image replacement technique.

You see a lot of links on sites which are for “Accessibility”, to provide both help for those with accessibility issues, and state what levels of accessibility the site is aiming for. However, I believe that this content should be split up between two different pages.