Adam:
CuteEditor right now can output well-formed XHTML. But the CuteEditor istself still can't render well against XHTML 1.0.
That doesn't exactly help my company. How can Cute Editor make this claim:
Support accessibility according to W3C WAI and section 508 accessibility
guidelines.
Cute Editor optional accessibility settings ensure your site complies with
Section 508, so people with disabilities can have full access to your content.
It seems you're bending the semantics of the sentence to say that the output of Cute Editor supports WAI and 508, while in reality people do not have full access to our site.