What is ATAG?
ATAG comes from the W3C's Web Accessibility Initiative, the same group behind WCAG. The current version, ATAG 2.0, is a W3C Recommendation published in 2015.
WCAG is about the web content people read and use. ATAG is about the tools used to make that content.
What are the two parts of ATAG?
| Part | What it asks | Example |
|---|---|---|
| Part A | Make the authoring tool itself accessible, so people with disabilities can create content | A page editor that works with a keyboard and a screen reader |
| Part B | Help authors produce accessible content | An editor that asks for alt text when you add an image |
Who is ATAG for?
ATAG is mainly for the people who build authoring tools. That includes:
- Visual HTML editors.
- Content management systems.
- Learning management systems.
- Office apps that save as HTML or EPUB.
- Platforms where people add content, such as blogs and forums.
It is also useful for managers and buyers who want to compare tools or ask a vendor for improvements.
How does ATAG help website owners?
You probably don't build authoring tools, but you use them. The tool you choose affects how accessible your pages turn out. When you compare website builders or content systems, ask:
- Can people with disabilities on your team use the editor?
- Does it prompt for alt text on images?
- Does it let you use real headings and lists?
- Do its templates produce accessible pages?
Our checklist covers what to check on your published pages.
Frequently asked questions
Is ATAG a law?
No. ATAG is a technical standard from the W3C. It sets out good practice for authoring tools.
What's the difference between ATAG and WCAG?
WCAG applies to web content. ATAG applies to the tools that create that content, and its Part B aims to help authors produce content that conforms to WCAG.
Do website owners need to follow ATAG?
ATAG is mainly for people who build authoring tools. If you run a website, it is most useful as a guide to what to look for when you choose those tools.