This morning, I had a conversation that highlighted for me one of the challenges WordPress faces in shaking off the label “not accessible”. It was a conversation with a large university system that was considering deploying WordPress as a resource for faculty blogs, within the institutional requirements that the site had to comply with WCAG 2.0 at level AA. They’d had the test installation reviewed by an expert blind user with JAWS, who had come back with a number of problems, including: Problems with navigation and information sharing with the content slider Problems with user feedback in the contact form Problems with missing alt attributes These weren’t the only problems cited, but that doesn’t change the nature of the problem. The problem is that none of these are characteristics of WordPress. The slider might have been from the theme, or from a plug-in. The contact form was probably a plug-in. The alt attributes? A user input problem, ultimately. One of Drupal’s advantages in accessibility is that it does provide a core mechanism for generating forms – and while not all forms in Drupal are generated by Drupal core, many of them are – at the minimum, a basic contact form is almost
Share This

We are using cookies on our website

Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.