Anders Nawroth wrote:
Geoff Deering skrev:
But there is a fundamental problem with ATAG. ATAG rightly requires WCAG P1 compliance, it has to on principle. But it is actually quite unreasonable to ask this of web based front ends that operate as Web Authoring Tools because none of them can function properly if scripting is turned off.
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.
ATAG1 (http://www.w3.org/TR/ATAG10/) does not clarify this as much as ATAG2 (http://www.w3.org/TR/ATAG20/#intro-def-au), which is still in draft process, attempts to do. http://www.w3.org/TR/ATAG20-TECHS/
I haven't looked at these specifications for a while, but just a brief look gives me the feeling that these drafts are quite an improvement on clarifying many issues.
Regards Geoff Deering
********************************************************* The CMS discussion list for http://webstandardsgroup.org/ *********************************************************
