ifacethoughts

Accessible CMSs

Most of the times we consider accessibility of only the published content. Not of the interface where the content is created or managed. Most popular reason being that the published content is where the meat is, the administration interface of content management interface or the backend is only the means, not the output itself. And that the userbase of content management can be controlled. However, in this user generated content era, we are seeing the user has entered the administration interface.

Roger Johansson points to a small study done by Joshue O Connor on testing accessibility of certain CMSs, including that of the content management interface. Roger Johansson rightly says that usually the administration interface is full of JavaScript tricks, including for the ones created using the RAD tools. In such a scenario, accessibility is usually forgotten.

A good article to read and understand what to look for in an accessible CMS.

Say your thought!

If you want to use HTML you can use these tags: <a>, <em>, <strong>, <abbr>, <code>, <blockquote>. Closing the tags will be appreciated as this site uses valid XHTML.

freshthoughts

contactme

Abhijit Nadgouda
iface Consulting
India
+91 9819820312
My bookmarks

badgesand...

This is the weblog of Abhijit Nadgouda where he writes down his thoughts on software development and related topics. You are invited to subscribe to the feed to stay updated or check out more subscription options. Or you can choose to browse by one of the topics.