- From: Litchfield Sharon <Sharon.Litchfield@smartservice.qld.gov.au>
- Date: Tue, 2 Aug 2011 10:28:08 +1000
- To: "Ian Sharpe" <isforums@manx.net>, <w3c-wai-ig@w3.org>
Try Squiz CMS (http://www.squiz.net/), this is being used by a few Queensland Government agency websites, and I am fairly sure the output is accessible as this is a requirement for us too. If you look at the features(http://www.squiz.com.au/products/squiz-matrix/features-checklist) it mentions this, but you may need to contact them for more details. It's also open source. Thanks, Sharon. ------------------------------------------------------------------------- Sharon Litchfield A/ Senior Online Analyst Online Services Unit smartservice QUEENSLAND Phone: 07 3008 8271 Extension: 38271 Fax: 07 3006 2404 Email: sharon.litchfield@smartservice.qld.gov.au Internet: www.qld.gov.au, www.getinvolved.qld.gov.au -----Original Message----- From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On Behalf Of Ian Sharpe Sent: Monday, 1 August 2011 11:23 PM To: w3c-wai-ig@w3.org Subject: Accessible content management system Does anyone have any suggestions on an accessible CMS please? I've spent some time researching this, particularly open source CMSs, but can't seem to find a definitive solution. I've seen a review of some of the leading CMS systems from an accessibility perspective that was dated 2006 but nothing since then. There are 2 sides to this question, firstly how accessible the platform is to set up and manage (user permissions, available modules, page creation and maintenance and module or widget maintenance etc), and how accessible is the output to people using the site. >From what I've seen, most of the leading open source CMSs (Drupal, Joomla, WordPress, DotNetNuke) seem to provide a mechanism for "skinning" a site and I have come across some "themes" that say they are accessible, although haven't found any examples to verify these claims. But these typically only affect the generated site, rather than the site administration interface. Obviously how accessible a module or widget might be is likely to depend on how much consideration the developers of the module or widget gave to accessibility, but I would be very interested if anyone has any experience or recommendations for an accessible CMS or CMS/Skin/Theme combination. Cheers ian _______________________________________________________ The contents of this electronic message and any attachments are intended only for the addressee and may contain privileged or confidential information. They may only be used for the purposes for which they were supplied. If you are not the addressee, you are notified that any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. The privilege of confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of mistaken delivery to you. If you receive this message in error please notify the sender by return e-mail or telephone. PLEASE NOTE: The Department of Public Works carries out automatic software scanning, filtering and blocking of the Internet, E-mails and attachments (including emails of a personal nature) for detection of viruses, malicious code, SPAM, executable programs or content it deems unacceptable. All reasonable precautions will be taken to respect the privacy of individuals in accordance with the Information Privacy Act 2009 (Qld). Personal information will only be used for official purposes, e.g. monitoring Departmental Personnel's compliance with departmental Policies. Personal information will not be divulged or disclosed to others, unless authorised or required by Departmental Policy and/or law. _______________________________________________________
Received on Tuesday, 2 August 2011 00:28:48 UTC