Comments on: Accessible Content Management Systems http://curbcut.net/accessibility/accessible-content-management-systems/ open and accessible Mon, 14 Jun 2010 11:07:43 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Christopher Steel http://curbcut.net/accessibility/accessible-content-management-systems/comment-page-1/#comment-220 Christopher Steel Sat, 03 Dec 2005 03:13:34 +0000 http://curbcut.net/2005/09/accessible-content-management-systems/#comment-220 Great comments. I have been working with Plone for a number of years and was initially attracted to it because at it's base it is very accessible, as in 100%. The problem with Plone (and any other system) is that it is very easy to break this by using WYSIWYG editors (Like kupu which comes with Plone). As soon as you use a WYSIWYG editor for your site you end up inserting a bunch of html which basically destroys your accessibility and makes it very difficult for less technical users also. Plone is a great product but it has a mighty steep learning curve. The average blogger can use it to create very accessible sites but they need to disable the WYSIWYG editor and use Structured Text or standard Text so that the site remains accessible. My sites are designed so that they are accessible to content contributors as well which also requires disabling (he he he) the WYSIWYG before it disables the users. My own site is on hold while I develop some sites for an Independant Living Center here in Canada. Nice Blog! Great comments. I have been working with Plone for a number of years and was initially attracted to it because at it’s base it is very accessible, as in 100%.

The problem with Plone (and any other system) is that it is very easy to break this by using WYSIWYG editors (Like kupu which comes with Plone). As soon as you use a WYSIWYG editor for your site you end up inserting a bunch of html which basically destroys your accessibility and makes it very difficult for less technical users also.

Plone is a great product but it has a mighty steep learning curve. The average blogger can use it to create very accessible sites but they need to disable the WYSIWYG editor and use Structured Text or standard Text so that the site remains accessible.

My sites are designed so that they are accessible to content contributors as well which also requires disabling (he he he) the WYSIWYG before it disables the users.

My own site is on hold while I develop some sites for an Independant Living Center here in Canada. Nice Blog!

]]> By: Christopher Phillips http://curbcut.net/accessibility/accessible-content-management-systems/comment-page-1/#comment-219 Christopher Phillips Tue, 20 Sep 2005 03:02:27 +0000 http://curbcut.net/2005/09/accessible-content-management-systems/#comment-219 Good points David- fortunately many blogs (and some CMS's) now completely separate content from presentation, however in my (again limited) experience with some systems there in an inaccessible presentation layer tied into the core of the system. It is those systems that I am referring to. Fortunately more and more systems are moving in the direction of separating content from presentation, but in the meantime I'll applaud efforts such as the Mambo fork with the hope that at least some of that code will be brought back into the main branch Good points David– fortunately many blogs (and some CMS’s) now completely separate content from presentation, however in my (again limited) experience with some systems there in an inaccessible presentation layer tied into the core of the system. It is those systems that I am referring to. Fortunately more and more systems are moving in the direction of separating content from presentation, but in the meantime I’ll applaud efforts such as the Mambo fork with the hope that at least some of that code will be brought back into the main branch

]]> By: david Clark http://curbcut.net/accessibility/accessible-content-management-systems/comment-page-1/#comment-218 david Clark Thu, 08 Sep 2005 20:25:41 +0000 http://curbcut.net/2005/09/accessible-content-management-systems/#comment-218 Interesting stuff... I think that CMS's are much like any other authoring tool, they are neither inherently accessible or inaccessible, its all in what one produces with them. I think that rather than accessibility compliance per se, I would look at the layouts used. If they are tableless/xhtml compliant, its a pretty good indication that accessibility will be a non-issue. I have had good luck with Drupal and Wordpress (yes, I see blogs as just low-end CMS's). The notion that Mambo created a separate fork just to address accessibility make me cringe in horror -- there is no reason why that should be necessary. Interesting stuff…

I think that CMS’s are much like any other authoring tool, they are neither inherently accessible or inaccessible, its all in what one produces with them.

I think that rather than accessibility compliance per se, I would look at the layouts used. If they are tableless/xhtml compliant, its a pretty good indication that accessibility will be a non-issue.

I have had good luck with Drupal and WordPress (yes, I see blogs as just low-end CMS’s).

The notion that Mambo created a separate fork just to address accessibility make me cringe in horror — there is no reason why that should be necessary.

]]>