Comments on: Accessibility Webcast on Plone http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/ Working together for standards Wed, 27 Mar 2013 12:19:03 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Roman Novak http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/comment-page-1/#comment-50728 Roman Novak Sat, 24 Feb 2007 12:51:25 +0000 http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/#comment-50728 Hola a todos, we also use Drupal. Maybe we would try Plone too if I knew about it before (anyway, only if it is also in czech language..., I did not find it at Plone's website, ok). I think that open source CMS will be preferred because for users - clients there is no different between "open" and "close" CMS. If you need some application to make it at your open source CMS, you can make it by yourself if you know how. Maybe if some company making own CMS for sale would do some marketing and many people would know about their CMS, people would buy it, I think. But Im not sure if the investing the money would be returnable. Hola a todos, we also use Drupal. Maybe we would try Plone too if I knew about it before (anyway, only if it is also in czech language…, I did not find it at Plone’s website, ok).
I think that open source CMS will be preferred because for users – clients there is no different between “open” and “close” CMS. If you need some application to make it at your open source CMS, you can make it by yourself if you know how.
Maybe if some company making own CMS for sale would do some marketing and many people would know about their CMS, people would buy it, I think. But Im not sure if the investing the money would be returnable.

]]> By: Jesús Quintana http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/comment-page-1/#comment-31975 Jesús Quintana Tue, 09 Jan 2007 23:41:14 +0000 http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/#comment-31975 with <a href="http://www.drupal.org" rel="nofollow">Drupal.org</a> you can create a site that is fully accessible, clean url's, and much more the code is clean and perfectly structured, greetings with Drupal.org you can create a site that is fully accessible, clean url’s, and much more

the code is clean and perfectly structured,

greetings

]]> By: Libby http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/comment-page-1/#comment-6107 Libby Tue, 26 Sep 2006 15:54:54 +0000 http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/#comment-6107 We've been using plone within our company to develop CMS for ourselves and clients for over a year now. Of course we've had some teething problems and as its open source you're continually waiting for updates and solutions from other users - but on the most part things move smoothly. As long as we develop the project properly I find the sites it produces very accessible compiling to w3c standards and it works very well with css which means we can always offer different and sometimes challenging designs without compromising on accessibility issues. My clients are always happy with the end result and often surprised at how easy it is for them to use - especially when they have been used to using different types of CMS that are difficult to use for the masses. Because its open source another big bonus (for us and the client) is the projects become much more cost effective with us only charging for the work we've done rather then for a licence fee. We’ve been using plone within our company to develop CMS for ourselves and clients for over a year now.

Of course we’ve had some teething problems and as its open source you’re continually waiting for updates and solutions from other users – but on the most part things move smoothly. As long as we develop the project properly I find the sites it produces very accessible compiling to w3c standards and it works very well with css which means we can always offer different and sometimes challenging designs without compromising on accessibility issues.

My clients are always happy with the end result and often surprised at how easy it is for them to use – especially when they have been used to using different types of CMS that are difficult to use for the masses.

Because its open source another big bonus (for us and the client) is the projects become much more cost effective with us only charging for the work we’ve done rather then for a licence fee.

]]> By: Mark http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/comment-page-1/#comment-6022 Mark Mon, 25 Sep 2006 17:41:05 +0000 http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/#comment-6022 At the moment I am using MODx to run my site, good its small at the mo but it will grow in time. The issues with accessibility and open source software is a problem that has been there for some considerable time. With the system that I use I can to a point create a site that is fully accessible. The problem with open source software is that they are not bespoke. Changes are made on a rapid scale and trying to keep up isnt easy. A site built using <a href="http://www.w3c-standards.com" rel="nofollow">w3c standards</a> and <acronym title="Cascading Style Sheets">CSS</acronym> is always on the correct path to succeed with accessibility issues. The one major problem is where do you start and where do you stop. There are lots of arguments saying that a site cannot be accessible if it uses an extensive amount of JavaScript or Flash. Creating a site that is fully accessible can be very expensive, using some form of content management system can help, but no system is perfect and someone who has no knowledge of <acronym title="Hypertext Markup Language">HTML</acronym> or programming will have problems. At the moment I am using MODx to run my site, good its small at the mo but it will grow in time. The issues with accessibility and open source software is a problem that has been there for some considerable time.

With the system that I use I can to a point create a site that is fully accessible. The problem with open source software is that they are not bespoke. Changes are made on a rapid scale and trying to keep up isnt easy.

A site built using w3c standards and CSS is always on the correct path to succeed with accessibility issues.

The one major problem is where do you start and where do you stop. There are lots of arguments saying that a site cannot be accessible if it uses an extensive amount of JavaScript or Flash. Creating a site that is fully accessible can be very expensive, using some form of content management system can help, but no system is perfect and someone who has no knowledge of HTML or programming will have problems.

]]> By: worklog » Accessibility and Plone http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/comment-page-1/#comment-4494 worklog » Accessibility and Plone Wed, 06 Sep 2006 18:44:11 +0000 http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/#comment-4494 [...] There is a summary at webstandards.org http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/. For the full webcast, checkout The National Center on Access and Education’s full webcast: Accessibility and the Open Source Content Management Movement. [...] [...] There is a summary at webstandards.org http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/. For the full webcast, checkout The National Center on Access and Education’s full webcast: Accessibility and the Open Source Content Management Movement. [...]

]]> By: Jon Stahl’s Journal » Blog Archive » links for 2006-09-06 http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/comment-page-1/#comment-4459 Jon Stahl’s Journal » Blog Archive » links for 2006-09-06 Wed, 06 Sep 2006 00:31:37 +0000 http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/#comment-4459 [...] Accessibility Webcast on Plone - The Web Standards Project nice demonstration of accessibility features in Plone (tags: plone accessibility nptech) [...] [...] Accessibility Webcast on Plone – The Web Standards Project nice demonstration of accessibility features in Plone (tags: plone accessibility nptech) [...]

]]> By: Richard Conyard http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/comment-page-1/#comment-4399 Richard Conyard Mon, 04 Sep 2006 14:36:13 +0000 http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/#comment-4399 Interesting article, also interesting by the lack of ATAG mention in the associated guide. Not being a great fan of ATAG I'm not suprised. I'm glad that the issue of accessible content management is being raised; there is some good work being done in both the open and closed source communities. Should WASP look to set-up a task force in this area and requires any help please count me in :-) Interesting article, also interesting by the lack of ATAG mention in the associated guide. Not being a great fan of ATAG I’m not suprised.

I’m glad that the issue of accessible content management is being raised; there is some good work being done in both the open and closed source communities. Should WASP look to set-up a task force in this area and requires any help please count me in :-)

]]> By: CMS Planet » Accessibility Webcast on Plone http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/comment-page-1/#comment-4335 CMS Planet » Accessibility Webcast on Plone Sat, 02 Sep 2006 21:04:57 +0000 http://www.webstandards.org/2006/09/02/accessibility-webcast-on-plone/#comment-4335 [...] Original post by The Web Standards Project. To read the full article visit: The Web Standards Project [...] [...] Original post by The Web Standards Project. To read the full article visit: The Web Standards Project [...]

]]>