The Authoring Tool Accessibility Guidelines (ATAG) 2.0 help make web authoring tools accessible to users with disabilities, and help authors create accessible web content. ATAG applies to all tools involved in creating, editing, or publishing web content, including WYSIWYG (“what you see is what you get”) editors, content management systems, and multimedia production software.
The Authoring Tool Accessibility Guidelines (ATAG) 2.0 are a standard that helps ensure web authoring tools are accessible to users with disabilities, and that these tools enable authors to create accessible web content. ATAG was developed by the Worldwide Web Consortium (W3C), the same organization that developed the Web Content Accessibility Guidelines (WCAG). By aligning with ATAG, providers of authoring tools can serve the broadest possible user base, and make it easier for authors to produce inclusive content.
What ATAG 2.0 says
ATAG explains how authoring tools can enable, encourage, and assist users in the creation of accessible web content through proper standards, designs, prompts, alerts, quality assurance (QA) and repair functions, help files, and other automated and self-assist capabilities.
The guidelines are based on the principle that all people must have the ability to author content (ATAG) and access content (WCAG). The tools used to create this information must, therefore, be accessible.
Tools covered by ATAG guidelines
ATAG guidelines are relevant for any tool involved in creating, editing, or publishing web content, including:
- Tools designed to produce web content (e.g., WYSIWYG HTML and XML editors).
- Tools that save content in web formats (e.g., word processors or desktop publishing apps).
- Tools that convert documents into web formats (e.g., DOCX to HTML converters).
- Tools that produce multimedia that is used on the web (e.g., video editors).
- Tools for website management, including CMS platforms and website publishing tools (e.g., WordPress, Wix, SquareSpace).
- Tools for layout design and formatting (e.g., CSS authoring tools).
Why ATAG conformance matters
ATAG conformance (sometimes called “ATAG compliance”) benefits both tool developers and content authors.
Developers create products that serve a broader user base, including authors with disabilities who need accessible interfaces to create content. This translates to greater product success and helps expand overall market share.
Authors with disabilities gain access to essential functionality for content creation. And all authors can more easily produce accessible websites, documents, and multimedia without requiring specialized accessibility knowledge–for example, through built-in features that automate accessibility checks, suggest improvements, and prevent common accessibility errors before content is published.
The widespread adoption of ATAG conformant (or “ATAG-compliant”) tools strengthens the entire web accessibility ecosystem. As more authoring tools incorporate accessibility features by default, the overall quality and accessibility of web content improves, creating better experiences for all users, including people with disabilities.
Frequently asked questions
How does ATAG differ from WCAG?
ATAG focuses on the tools used to create web content, while WCAG focuses on the content itself. ATAG provides guidance for making authoring tools accessible to users with disabilities, and ensuring these tools help authors create WCAG-conformant content. WCAG provides guidance for designers, developers, and content authors to create accessible websites, applications, and other digital experiences. Both standards work together: ATAG-conformant tools make it easier to produce WCAG-conformant content.
Who needs to meet ATAG guidelines?
Developers of web authoring tools, including content management systems and website builders, should align with ATAG to support accessibility. This includes companies that create WYSIWYG editors, CMS platforms like WordPress or Drupal, website builders like Wix or SquareSpace, word processors with web export features, and multimedia authoring software. While conformance with ATAG guidelines is not a legal requirement, doing so will help any organization that produces tools for creating web content serve the broadest possible audience.
What are examples of ATAG-compliant features?
Because ATAG is not a law, the term “ATAG-compliant” is a misnomer–the accurate term is “ATAG-conformant.” Examples of ATAG-conformant features include automated prompts for alt text when images are uploaded, heading structure validation tools, and built-in accessibility checkers. Other examples include color contrast analyzers, keyboard navigation testing, caption editors for video content, and semantic HTML suggestions. These features help authors identify and fix accessibility issues during the content creation process rather than after publication.
Do CMS platforms like WordPress need to follow ATAG?
While not legally mandated, CMS platforms like WordPress, Drupal, Joomla, and similar tools should follow ATAG guidelines to provide an accessible experience and support accessible content creation. These platforms are authoring tools that enable users to create and publish web content. ATAG conformance means the CMS interface itself must be accessible to authors with disabilities, and the platform should include features that help authors create accessible content, such as alt text fields, heading structure tools, and accessibility validation.