ATAG

ATAG is one of three core accessibility standards from the W3C's Web Accessibility Initiative, alongside WCAG (for web content) and UAAG (for browsers and media players). The logic behind ATAG is simple: the overwhelming majority of web content is created through tools, not hand-written. If those tools produce inaccessible markup by default, or lock out authors with disabilities, accessibility problems get manufactured at industrial scale before anyone even audits a website.

ATAG 2.0 defines an "authoring tool" broadly: any software that authors use to create or modify web content. That covers obvious cases like WordPress, Squarespace, Wix, and Drupal, but also learning management systems, wikis, forums with post editors, email builders, video platforms with caption editors, and "what you see is what you get" (WYSIWYG) components embedded inside other products.

ATAG itself is a voluntary technical standard — there is no "ATAG police." Its practical reach comes from who adopts it and where it gets referenced.

Part A of ATAG 2.0 asks whether people with disabilities can actually use the tool to create content. Its principles will feel familiar if you know WCAG: the editing interface must be perceivable, operable, understandable, and compatible with assistive technology such as screen readers.

Concretely, that means things like full keyboard access to every editing function, text alternatives within the editing view, no keyboard traps in dialogs or media pickers, support for the author's platform accessibility settings, and features like undo and autosave that reduce the cost of errors. If the tool has a preview mode, the preview should be at least as accessible as an ordinary browser rendering of the content.

Part B is where ATAG gets unique. It requires the tool to make accessible content production possible, and then to actively enable, guide, and promote it. The standard organizes this into four principles: the tool must fully support automatic production of accessible content, support authors in producing it, support them in improving existing content, and promote and integrate its accessibility features rather than burying them.

In practice, a strongly Part B-conformant tool generates valid semantic markup on its own, prompts authors for alt text when they insert images (without auto-filling junk placeholders), preserves headings, labels, and other accessibility information during copy-paste and format conversion, ships accessible templates that are identified as such, and offers accessibility checking with repair suggestions as a first-class feature — not a hidden plugin.

ATAG does not define its own notion of accessible content — it delegates that entirely to WCAG. When Part B says a tool must support the production of accessible content, it means content that conforms to WCAG success criteria. Similarly, the accessibility of the authoring interface in Part A is measured with WCAG-style requirements adapted to software.

Like WCAG, ATAG has three conformance levels — A, AA, and AAA — and a tool can claim conformance to Part A, Part B, or both. For most organizations, the pragmatic takeaway is this: WCAG tells you whether your published pages are accessible; ATAG tells you whether your publishing pipeline will keep them that way. Fixing a website while continuing to author in a tool that strips alt text or generates div-soup markup is a treadmill, not a solution.

Nobody gets fined for "violating ATAG" directly, because it is a standard rather than a statute. The legal exposure is indirect but real. In the United States, federal procurement under Section 508 requires authoring-tool accessibility support, so vendors who ignore it can lose government contracts. In the EU, EN 301 549's authoring-tool clause applies to public-sector procurement and to products covered by the European Accessibility Act, where national enforcement bodies can order corrective action and impose penalties under member-state law.

There is also downstream exposure: if an inaccessible authoring tool causes your organization to publish inaccessible content, the resulting website can still trigger complaints or litigation under laws like the ADA in the US or the AODA in Ontario. The tool vendor's shortcomings are rarely a defense for the site operator.

Whether you build authoring software or simply rely on it, a few concrete moves capture most of ATAG's value.