I have just been reviewing Adobes CS3, the built in accessibility standards to WCAG A and AA standards in xhtml are for me a breath of fresh air. I don't suppose there is any chance of something similar being incorporated into my favorite editor is there?

Regards John.

I first bought the CC editor in 1996 and found it admirable. But I have to confess I haven't really got much use out of it since about 2000 when I had to start taking accessibility seriously, and particularly when Section 508 came into force. I don't think CC or the VisualSite Designer products have ever really gotten hardball standards-compliant web page coding. I need absolute compliance to XHTML 1.1 and CSS2 and I don't want to see any tables in my code unless I'm arraying data in tabular form. I don't want to see any inline style declarations when I'm already running an external CSS sheet. I certainly don't want to see any tainted old deprecated tags or any tags that don't need to be there. As I work outside the typographically parochial USA I need to support utf-8 and handle numeric character references in a way that many locales and browser and OS combinations can receive them, not just Windows and IE users in the Lower 48. Everytime there's a new release of CC or VSD I rush to give it a go and see if the elephant in the room (accessibility) has finally been noticed, but sadly this never comes to pass. I still call up CC from time to time to tweak something, but it just isn't good enough to build the pages the way I want them built. I had hoped that VSD would allow me to import my own clean XHTML to create templates but was disappointed to find it can't import real pages as templates, only its own non-accessible proprietory pages. It's all such a pity, really.

Eamon,
Couldn't agree more! I still use the VSD to create but then go to CS3 to get the coding right. Could you imagine what a tour de force it would be if they incorporated it into VSD!

Keep in mind that XHTML 1.1 should only ever be used when the page is actually going to be served as xhtml. This may be the case with an internal server, but public websites actually have their xhtml served as regular html because IE doesn't support xhtml.

Hi,
On the subject of web accessibility standards, has CC addressed this either application? I am curious as I also want to use their software for creating accessible sites.
Kirk