Now that the web standards ‘battle’ is being won, and web developers are taking more care with their markup, a regular question is “should I use the address tag?”. This questions comes in various guises, but the fundamental problem is that the address element doesn’t have the meaning that people think it does.

Having cut down what authors can use, they can just about edit regular text articles. However, I haven’t met many clients who would be happy with just that! There are certain things that require the addition of code, this is how to do it.

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.

Generally I delete phishing emails without a second glance, but this one caught my eye for being so realistic, and using a interesting method intended for accessibility to disguise a fraudulent link.

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.

With a WYSIWYG interface, there has to be an area that appears as it will when published, which means to change bits within it, you need one or more toolbars. This is an exploration of what those toolbars should do.

Floating ideas onto the CSS working group can be a frustrating experience, possibly almost as frustrating as seeing the same questions come up every few months! I take a look at why it would be useful to be able to identify text nodes.

The second building block of a modern WYSIWYG editor is how the styles are defined and added. Styles should be applied by class to standard HTML, but what kind of import methods would be best, and how would they surface in the interface?