Support forums - WAI and Web Accessibility Cute Editor failing all over

Support forums » Products » Cute Editor for .NET » Re: WAI and Web Accessibility Cute Editor failing all over

WAI and Web Accessibility Cute Editor failing all over

Last post 01-25-2008, 10:11 AM by GWax. 2 replies.


	Sort Posts: Previous Next

01-24-2008, 12:45 PM 36536

GWax
Joined on 01-24-2008
Posts 43

WAI and Web Accessibility Cute Editor failing all over

Reply Quote

According to Total Validator Cute Editor fails with these errors:

E007 Found '&' within 'style'. You should use '&' instead: CuteSoft_Client/CuteEditor/Load.ashx?type=theme&theme=Custom&file=all.png is all over the place and fails left and right. When I view source some of your code is properly marked up and then you have cases like this where it is not.

W001 There should not be any white space at the start or end of an attribute's value:

<DIV class=" CuteEditorToolbar". Throughout the loader.js there are what appears to be these unnecessary spaces.

E822 [WAI 3.4 (AA)] Use relative, rather than absolute units:

There is also a side issue of being able to set a <label for=""> in a simple manner for cute editor

Filed under: 508, accessibility, wai

01-25-2008, 12:29 AM 36541 in reply to 36536

Adam
Joined on 09-23-2003
Aurora, ON
Posts 18,678

Re: WAI and Web Accessibility Cute Editor failing all over

Reply Quote

GWax,

CuteEditor right now can output well-formed XHTML. But the CuteEditor istself still can't render well against XHTML 1.0.

http://cutesoft.net/example/xmloutput.aspx

asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
asp wysiwyg html editor: http://cutesoft.net/ASP
asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
Live Support: http://cutesoft.net/live-support/default.aspx

01-25-2008, 10:11 AM 36558 in reply to 36541

GWax
Joined on 01-24-2008
Posts 43

Re: WAI and Web Accessibility Cute Editor failing all over

Reply Quote

Adam:

GWax,

CuteEditor right now can output well-formed XHTML. But the CuteEditor istself still can't render well against XHTML 1.0.

http://cutesoft.net/example/xmloutput.aspx

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.