Using Editoria11y to solve content accessibility issues
Developers and designers can work to integrate accessibility into their websites by considering color choices and ensuring keyboard navigability. However, the weakest link can be the content, particularly when editors don't use appropriate alt tags for images and enter generic links like "click here." We can't expect editors to be experts on WCAG standards or have access to tools such as SiteImprove. Checkers like WAVE can be overwhelming and cumbersome for them. It's essential to provide editors with clear and easy guidance on how to address potential content issues.
This is where Editoria11y Accessibility Checker comes in. It's a Drupal module that empowers content editors to review their pages and correct accessibility issues when they find them.
I will share insights gained from implementing Editoria11y for over 275 editors on a major healthcare website. I'll demonstrate the tool and the types of issues it can detect. I'll also talk about our strategy for tackling the cleanup and how we used Editoria11y and SiteImprove reports to address these issues before the full rollout.
This is where Editoria11y Accessibility Checker comes in. It's a Drupal module that empowers content editors to review their pages and correct accessibility issues when they find them.
I will share insights gained from implementing Editoria11y for over 275 editors on a major healthcare website. I'll demonstrate the tool and the types of issues it can detect. I'll also talk about our strategy for tackling the cleanup and how we used Editoria11y and SiteImprove reports to address these issues before the full rollout.