WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: FW: HTML - <abbr> and <acronym> settings

for

From: Christian Heilmann
Date: Mar 24, 2006 8:10AM

> It would be nice if major authoring tools (*cough* Apple iWeb, Google
> Page Creator *cough*) created valid, semantic, accessible code, but
> it's not an easy thing to achieve. If Google can solve search, I'm
> sure they could solve WYSIWYG -> semantic/structured HTML.

Having dabbled with some WYSIWYG editors myself I must say that is not
that easy and is quite a different task from writing a search /
spidering algorhithm.

The whole idea of the web and contributing to it as it is is flawed
because of the low threshold you have rightfully brought up. WYSIWYG
does not only create bad markup in a lot of cases but also bad
content.

I've spend far too many hours telling editors that "click the links in
the blue panel on the left" is not good page copy, and I have found
one project where that piece of content is still in there although the
navigation is now a green strip on the top.

Content does not get better by adding smileys animations or laying it
out while you type it, writing and layout are different skill sets
that don't always mix.

That said, I must say I am impressed how clean the code of Googlepages
is compared to other products (contained in CMS costing >