Category:ATAG Guidelines

From perpendicular angel knowledgebase
Revision as of 21:54, 20 July 2020 by Kirabug (talk | contribs) (Created page with "Authoring Tool Accessibility Guidelines or ATAG Guidelines, ensure that not only is the experience of using an authoring tool accessible, so is the experience of using the out...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Authoring Tool Accessibility Guidelines or ATAG Guidelines, ensure that not only is the experience of using an authoring tool accessible, so is the experience of using the output of an authoring tool.

In other words, the ATAG ensure that:

  • A low-vision author can navigate a blogging application (for example), identify where she's created typos, and correct them, all using a screen reader and keyboard.
  • An able-bodied author who may not be thinking about accessibility will get prompted to enter alt text or form labels that a blind reader will need to read the blog post.

These guidelines apply to any part of a web application that allows a user to create web content -- whether it's a Google Drive-like app, a WYSIWYG editor in a content management system, an online vector drawing application, or anything else that produces web content.

The ATAG Guidelines are broken up into two parts.

Part A: Make the authoring tool accessible

A.1. Authoring tool user interfaces follow applicable accessibility guidelines A.1.1. (For the authoring tool user interface) Ensure that web-based functionality is accessible A.1.2. (For the authoring tool user interface) Ensure that non-web-based functionality is accessible A.2. Editing-views are perceivable A.2.1. (For the authoring tool user interface) Make alternative content available to authors A.2.2. (For the authoring tool user interface) Ensure that editing-view presentation can be programmatically determined A.3. Editing-views are operable A.3.1. (For the authoring tool user interface) Provide keyboard access to authoring features A.3.2. (For the authoring tool user interface) Provide authors with enough time A.3.3. (For the authoring tool user interface) Help authors avoid flashing that could cause seizures A.3.4. (For the authoring tool user interface) Enhance navigation and editing via content structure A.3.5. (For the authoring tool user interface) Provide text search of the content A.3.6. (For the authoring tool user interface) Manage preference settings A.3.7. (For the authoring tool user interface) Ensure that previews are at least as accessible as in-market user agents A.4. Editing-views are understandable A.4.1. (For the authoring tool user interface) Help authors avoid and correct mistakes A.4.2. (For the authoring tool user interface) Document the user interface, including all accessibility features

Part B: Support the production of accessible content

B.1. Fully automatic processes produce accessible content B.1.1. Ensure that automatically-specified content is accessible B.1.2. Ensure that accessibility information is preserved B.2. Authors are supported in producing accessible content B.2.1. Ensure that accessible content production is possible B.2.2. Guide authors to produce accessible content B.2.3. Assist authors with managing alternative content for non-text content B.2.4. Assist authors with accessible templates B.2.5. Assist authors with accessible pre-authored content B.3. Authors are supported in improving the accessibility of existing content B.3.1. Assist authors in checking for accessibility problems B.3.2. Assist authors in repairing accessibility problems B.4. Authoring tools promote and integrate their accessibility features B.4.1. Ensure the availability of features that support the production of accessible content B.4.2. Ensure that documentation promotes the production of accessible content

This category currently contains no pages or media.