Talk by Hidde de Vries / View Slides
Your CMS plays a decisive part in creating accessible content, suggest the Authoring Tools Accessibility Guidelines (ATAG). Whenever a content designer creates content, the CMS could help with the accessibility of it. For instance, when a designer drops in an image, the CMS could point to the ideal text alternative or calculate the consequences for color contrast.
In this talk, you will learn more about what ATAG is and how, with ATAG in mind, CMSes can personally assist content editors on their way to a more accessible website.
What would be the most important feature (or correction) you must change in Gutenberg to be completely accessible?
Do you have any good tool for developers to test the different levels of accessibility A, AA, AAA?
Why are we all focusing on WCAG, and not also on ATAG?
How ready is WordPress now to serve as an Accessibility ready assistant among CMS?
What level of accessibility do you think WordPress CMS has? A, AA, AAA?
Is Craft CMS much better than WordPress in terms of the accessibility of the editor?
Have you ever tried to use ACF and a headless front end as editor (form) to get accessibility content creation?
In terms of frameworks and documentation, what you think has better a11y standards?
react.js, gatsby.js, next.js, vue.js?