ATAG (Authoring Tool Accessibility Guidelines)

The Authoring Tool Accessibility Guidelines (ATAG) is a W3C standard developed by the Web Accessibility Initiative that addresses the accessibility of authoring tools, the software applications and services people use to create web content. ATAG 2.0, the current version, reached W3C Recommendation status in 2015. ATAG is unique among W3C accessibility standards because it has a dual focus. Part A addresses making the authoring tool's own user interface accessible so that people with disabilities can use the tool to create content. Part B addresses the tool's ability to support and encourage the production of accessible web content by all authors, regardless of their accessibility knowledge. Authoring tools span a wide range of software: content management systems like WordPress, Drupal, and Joomla; website builders like Wix and Squarespace; WYSIWYG editors like TinyMCE and CKEditor; code editors like VS Code; social media platforms; email marketing tools; learning management systems; and any other tool that produces web content.

The web is only as accessible as the content published on it, and the vast majority of web content is created using authoring tools, not hand-coded HTML. If those tools make it difficult to produce accessible content, or if they actively generate inaccessible output, the accessibility of the web suffers at scale. Consider a content management system that doesn't prompt authors to add alt text to images, generates heading structures that skip levels, or produces non-semantic HTML. Even authors who care about accessibility will struggle to produce accessible content if their tools work against them. Conversely, a tool that automatically prompts for alt text, enforces proper heading hierarchy, and generates clean semantic markup makes accessible content the default. ATAG Part A matters because authors with disabilities need to be able to use the tools of their trade. A blind developer using a code editor, a motor-impaired content creator using a CMS, or a deaf video editor all need their tools to be accessible. Inaccessible authoring tools exclude these professionals from content creation entirely. ATAG Part B matters because it leverages tools as force multipliers for accessibility. One authoring tool can influence the accessibility of millions of web pages. Improving the tool improves everything it produces.

ATAG 2.0 is organized into two parts, each containing principles and guidelines: **Part A: Make the authoring tool user interface accessible** - **Principle A.1:** The authoring tool user interface follows applicable accessibility guidelines. The tool's own interface should meet WCAG criteria. - **Principle A.2:** Editing views are perceivable. Authors can perceive the content they are editing, including accessibility information. - **Principle A.3:** Editing views are operable. Authors can navigate and operate the editing interface using keyboard and assistive technologies. - **Principle A.4:** Editing views are understandable. The interface is consistent and helps authors avoid mistakes. **Part B: Support the production of accessible content** - **Principle B.1:** Fully automatic processes produce accessible content. When the tool generates content automatically (templates, boilerplate, auto-formatting), that content should be accessible by default. - **Principle B.2:** Authors are supported in producing accessible content. The tool provides features like alt text prompts, heading level selectors, accessible color contrast checking, and form label fields. - **Principle B.3:** Authors are supported in improving the accessibility of existing content. The tool includes accessibility checking and repair functionality. - **Principle B.4:** Authoring tools promote and integrate their accessibility features. Accessibility features are prominent, documented, and not hidden away in obscure settings. **Practical examples of ATAG conformance:** - A CMS that requires alt text when uploading images (B.2) - A WYSIWYG editor that provides heading level selection instead of just font size changes (B.2) - A website builder whose templates all meet WCAG AA out of the box (B.1) - An email builder with a built-in accessibility checker that flags color contrast issues (B.3) - A code editor with accessible autocomplete and keyboard navigation (A.3) The W3C provides an ATAG Report Tool that helps evaluators assess authoring tools against ATAG criteria. The tool generates structured reports that tool vendors can use to identify and prioritize improvements.