-
Notifications
You must be signed in to change notification settings - Fork 11
Defining authoring tools
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).
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
- 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 in frameworks
- form generators
- static site generators
- GitHub wikis
- Wix
- Wordpress.com
- Squarespace
- Godaddy website builder
- Medium
- dev.to
- GitHub wiki builder
- Weebly
- Draft.js from Facebook (used both by Twitter and Facebook for content creation)
- Twitter
- Note: “draft tweet” uses Draft.js
- Buffer
Pattern libraries (often seen in design systems, also called front-end style guides) are collections of reusable patterns (bits of HTML, CSS and JS). Organisations large and small use them so that their team(s) can quickly put together websites without reinventing the wheel.
If a CMS has a multiplier effect, maybe pattern libraries do too.
Examples of pattern libraries that mention accessibility or having it “built-in”:
- BBC Gel (“Guidance for developers building accessible websites based on BBC GEL.”)
- Sainsbury's
- Australian government
- Deque Cauldron