-
Notifications
You must be signed in to change notification settings - Fork 11
Links
Hidde de Vries edited this page May 21, 2021
·
18 revisions
Things Hidde read about making authoring tools better.
- The Umbraco Backoffice accessibility initiative - Microsoft Industry Blogs
- FEAT project
- Tweet: “Has anyone used a CMS that's actually accessible for things like keyboard navigation or using a screen reader?”
- Plone 5 announcement with ATAG 2.0 support
- How to Create Custom WordPress Editor Blocks in 2020 - good explanation of what exactly “Blocks” are and how to create them
- #47456 (Improve the user interface to ensure correct usage of the image alt text) – WordPress Trac
- JAMstack CMSs Have Finally Grown Up! | CSS-Tricks
- How to Fix Higher Ed’s Accessibility Problem - Modus
- My thoughts on Gutenberg Accessibility – Marco's Accessibility Blog
- Customer Servant Consultancy : The web is for people, not corporations (on Gutenberg accessibility; call to leadership)
- Blocks UI - page builder that uses JSX blocks
- Slack introduced a new WYSIWYG editor but will bring back the old one
- Media embedding in Drupal 8.8 | Wim Leers
- Drupal 8: best authoring experience for structured content? | Wim Leers; this post is from 2013, but has useful points about WYSIWYG (CKEditor)
- When a platform works against people's disability needs: What Tumblr Taught Me About Accessibility by Nic Chan:
Tumblr as a platform has blatantly ignored the requests of it’s disabled users, and was hostile to third-party developers that made it’s platform usable. While Tumblr as a platform has very much served as a lesson for what not to do, Tumblr’s disability community has developed unique strategies in order to cope with the inaccessibility of the platform, modelling what we might now call ‘inclusive design’ before the term was coined.