While looking for Web accessibility statements on some content management system (CMS)-blog engines, several searching methods have been tried. Keyword "accessibility" followed by CMS-web-blog engine’s name and
accessibility site:[cms or web/blog engine name].com queries are also applied on Google. Do they really care of it?
Drupal accessibility statement has this:
This initiative started with advancements with Drupal 7 accessibility. We have committed to ensuring that all features of Drupal core conform with the Worldwide Web Consortium (W3C) guidelines: WCAG 2.0 and ATAG 2.0. Where possible we will also update the previous version of Drupal core, version 6, to enhance its accessibility…
Accessibility – WordPress Codex:
Accessibility is for everyone, even WordPress users. But what is it?
This page has a lot of useful resources related to universal accessibility and usability concepts.
Joomla accessibility statement (last updated in 2006):
This statement addresses three main areas of accessibility for Joomla!: Sites produced using Joomla! (front end and back end), and the Joomla.org site.
Sites produced using Joomla!
Front end (website)
We will provide a solution capable of delivering accessible websites that comply with WCAG 1.0 Priority 2 and Section 508 requirements by release 1.5 of Joomla!
Back end (admin)
While we will incorporate as many accessibility "features" in the back-end as possible, the technical changes required to reach WCAG compliance at this point would involve an extensive re-write of the code. It would be counter-productive to do this now, as a such a re-write is planned for the 2.x series.
ATutor includes a variety of features designed to ensure that content is accessible to all potential users, including those with slow Internet connections, older Web browsers, and people with disabilities using assistive technologies to access the Web. These features are described in detail below. Depending on the theme being used, ATutor may include all or some of the features listed here. The default theme includes them all.
It has 16 features listed, such as: bypas/skip links, accesskeys, accessibility verifier, alternative text and navigation, resume/continue feature, hide menus, form labels, form field focus, etc.
For the Textpattern (Txp), I only find this FAQ – Is Textpattern search engine friendly?:
- Question: Can I use Textpattern for SEO?
- Answer: Yes. Textpattern employs many recommended usability and accessibility techniques, which are friendly to both users and search engines, right out of the box. The default page template is clean, minimal XHTML, with CSS stylesheets linked externally. Textile automatically generates valid XHTML for page content.