Quote Originally Posted by remi View Post
A knowledged (X)HTML/CSS expert would use the following simple markup:

....

But, no you're on your WYSIWYG absolute position trip, don't care about semantic HTML and prefer to export a tag soup par excellence:

....

The problem is, you're lost in the idea to export a page the same as it's shown on Xara's canvas (the so often discussed WYSIWYG principle).
The first one is a plain unformatted text which you can easily insert into placeholder. You don't need to use wysiwyg tools to enter unformatted text.
First one will look unpredictably in a browser, second one will look exactly how you want it too.
So what's the point of using first one if it has no advantages from the designers point of view?

Now back to the accessibility. Let's take an example.

Here's the site exported with WD without any particular attention to the accessibility by the author:
http://webdesigner.xara.com/

Here's the NVDA, open source, free voice reader software:
http://www.nvda-project.org/

Open this site in Opera for example, and read with NVDA.
Do you hear any influence of the tag mess?
Is this inaccessible site?
Try, and you'll see. Or hear actually.