Geoff Deering skrev:
Anders Nawroth wrote:
What about Amaya? http://www.w3.org/Amaya/
I think it's important to make CMS integrate with different authoring tools, so that users can make a choice according to their needs. Adding support for Amaya really isn't difficult.
Amaya is an authoring tool that runs as a native applications. Using HTML/CSS/Scripting in web forms as the authoring front end is what I am refering to, which is different, and is what we find in most CMSs. In those cases, the CMS itself is the authoring tool which should try to comply with ATAG.
My thought was more "how to make web authoring accessible" than that it has to be a HTML/CSS/JS authoring front end. The JS-based solutions gets more and more features (and they do need this), wich results in increasing download times. They also rely on browser features like "content-editable" wich AFAIK isn't part of any W3C-standard. That is, the JS-solutions are based on native apps like IE and Moz/FF, not on standards. You can't use them in Opera, for instance.
/Anders ********************************************************* The CMS discussion list for http://webstandardsgroup.org/ *********************************************************
