Defining authoring tools

Definitions

From normative ATAG glossary:

Any web-based or non-web-based application(s) that can be used by authors (alone or collaboratively) to create or modify web content for use by other people (other authors or end users).

Mike Gifford:

Web accessibility is complicated. Building a CMS that supports solid accessibility defaults is more complicated. Creating an authoring environment that makes it easier to create accessible content for authors is even more difficult still. This is the challenge that ATAG presents to those who are making web authoring environments.

Examples, according to normative glossary:

• WYSWIYG editors
  • TinyMCE accessibility, email: v3 used to be ATAG 2 compliant
  • CKEditor (IBM leads ATAG/WCAG for CKEditor)
• software that edits source code
• “Save as HTML” features
• CMSes
• tools to create online courses

Other ways to phrase it

• a tool that multiplies the effect of accessibility

Other examples we could consider:

• components
• form generators
• static site generators
• GitHub wikis

Websites that make websites

• Wix
• Wordpress.com
• Squarespace
• Godaddy website builder

Social Media

• Twitter
• Buffer

Education: course builders

---

CMSs

Most popular CMSes: WordPress, Joomla and Drupal

Joomla

Joomla! should be an accessible tool and provide a solid out of the box base for building accessible websites.

Since the birth of Joomla, we have made efforts to make our software meet accessibility requirements. With Joomla! 4.0, our next milestone, we are determined to push further down the road to accessibility. With this in mind, we will strive to ensure full accessibility of all modern dynamic user interface elements. We will, first and foremost, ensure full accessibility of Joomla’s backend so that those with disabilities can use Joomla to create, administer and maintain sites in barrier-free

WordPress