- From: Eric Eklund <eeklund@umn.edu>
- Date: Wed, 3 Aug 2011 07:42:06 -0500
- To: Ian Sharpe <isforums@manx.net>
- Cc: "<w3c-wai-ig@w3.org>" <w3c-wai-ig@w3.org>
Hey Ian, I would recommend that you check out Contao, the accessible open source CMS (http://www.Contao.org). This project was formally known as TYPOlight. It is a relatively small user base compared to a program like Drupal, but one of the main design tenets is accessibility (both in the front and back end). Disability Services at the University of Minnesota currently uses Contao to manage their sites at http://ds.umn.edu and http://accessibility.umn.edu. One of the primary content managers is the University's Adaptive Technology Specialist, who is blind himself. I was part of the CMS selection team but have since moved positions. If you desire more information, feel free to contact me off list. I'd be happy to introduce you to the people that work on those projects. Eric Eklund Web Programmer/Analyst Academic Support Resources University of Minnesota On Aug 1, 2011, at 8:22 AM, "Ian Sharpe" <isforums@manx.net> wrote: > 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 > > > > > > > >
Received on Wednesday, 3 August 2011 12:42:40 UTC