-
Notifications
You must be signed in to change notification settings - Fork 11
CMS comparison
I talked to people from various CMSes about how accessibility works in their organisation and what kind of resources/guidance could help them push accessibility forward.
- Presentation: Joe Dolson tested WordPress against ATAG from Accessing Higher Ground
- Some WordPress a11y problems can be patched with plugins like WP Accessibility and autotested with Tenon via Access Monitor
- Talked to Rian Rietveld (former WordPress accessibility team lead) and Andrea Fercia (currently in WordPress accessibility team)
- Accessibility statement: https://www.drupal.org/about/features/accessibility \
Drupal 7 is designed to support the development of sites that comply with WCAG 2.0 and ATAG 2.0. The Drupal accessibility community will be involved in adopting best practices in Drupal 8 as they evolve.
- Drupal A11y project
- ATAG 2 compliance review from 2011
- Accessibility pledge that theme designers can use
- Blog post: Drupal: Accessible CMS - WCAG 2.0 and ATAG 2.0 Compliant
- Accessibility Features
- Accessibility handbook
- Drupal voor Gemeenten is an initiative of over 30 Dutch cities who work together on a Drupal theme that is very suitable for cities
Mike Gifford in WAI-ig mailing list:
We wanted to see that a person with a disability can install, develop, administer, edit, publish and view their site. In Drupal 8 we’ve improved upon the default accessibility in Drupal 7. Jumping to HTML5 & adding WAI-ARIA has helped a great deal, as most admin interfaces are considerably more complex than the static pages. Most other CMS’s haven’t really even thought about the accessibility of their admin tools.
From their accessibility statement:
Joomla! should be an accessible tool and provide a solid out of the box base for building accessible websites.
Since the birth of Joomla, we have made efforts to make our software meet accessibility requirements. With Joomla! 4.0, our next milestone, we are determined to push further down the road to accessibility. With this in mind, we will strive to ensure full accessibility of all modern dynamic user interface elements. We will, first and foremost, ensure full accessibility of Joomla’s backend so that those with disabilities can use Joomla to create, administer and maintain sites in barrier-free
- Community audit (Improving the Accessibility of the Umbraco CMS Back Office - News - Sigma) found 151 issues, which they are working through in a Trello board
- GitHub issues tagged accessibility
- A Dutch agency worked with Accessibility Foundation to make Umbraco more accessible and work towards ATAG and WCAG compliance: Making Umbraco ATAG and WCAG-compatible