a11yprompter – Accessibility guidance for editors
In day-to-day content editing, accessible features of a website may be inadvertedly compromised. With instant validation tools available, why not integrate them into editors’ workflow in the CMS?
- Type
- Open source plugin for Kirby CMS
- URL
- https://codeberg.org/sebastiangreger/kirby-a11yprompter
- Year
- 2021–
- Status
- active
- License
- GPL-2.0
About this project
Assisting editors to keep a website accessible: Sa11y and Editoria11y …and a plugin for Kirby
No matter how thoroughly a website is checked for accessibility by its creators, content editors play an important role in keeping it that way. Two little tools assist editors in their work, alerting them if content added through the CMS breaks certain accessibility principles. As a key building block in an inclusive publishing strategy, I look at the options and provide a turnkey solution for Kirby.
Adding BAAT to a11yprompter
While Editoria11y/Sa11y are great tools to provide content editors with direct accessibility feedback, I like to use the BAAT tool (developed by mindscreen) during website development. By adding it as an optional feature to my Kirby plugin, I can have it appear on all pages automatically. A niche feature, created to scratch my own itch, but maybe it is of value to somebody else as well.
Related
Your CMS is an accessibility assistant
talks.hiddedevries.nl/tGzZs2/your-cms-is-an-accessibility-assistant
A talk by Hidde de Vries, advocating for CMSs to take a stronger role in assisting to create and publish accessible content. Even mentioning Editoria11y, this falls right into the category of tool that I hacked together when creating the a11yprompter plugin for Kirby: making it as easy as possible for editors to spot where they may inadvertently introduce accessibility issues to an otherwise well-designed website.