spiral - 1:16 pm on Dec 14, 2010 (gmt 0)
I'm consulting for a site that wants to meet the WCAG 2.0 for "A" level conformance.
It's being built by a third party and I am giving SEO and accessibility advice, but my core competence is in SEO.
I've been going over the new site and checking it against the WCAG guidelines. Everything seems fine/fixable, except the WYSIWYG editor, which the client will then use to upload new pages to the site.
The WYSIWYG editor creates lots of "junk" HTML used for presentation. This seems to have the potential to destroy much of the site's accessibility as new content is added. Since all the new pages will not have Content and Presentation separated (HTML and CSS).
The site designer claims that he can't modify the existing WYSIWYG editor. Technically, the client will get an accessible site, but it will degrade with every new page added.
Any simple solutions? Does this sort of problem come up often? I can dig my heels on this, but the client will probably end up paying a ridiculous amount of money for changes to the WYSIWYG editor.