Authoring Tool Accessibility Guidelines 2.0 - ATAG

Owned by Christian Jones
Last updated: Jun 24, 2021
4 min read

Authoring Tool Accessibility Guidelines (ATAG) Overview

Authoring Tool Accessibility Guidelines (ATAG) 2.0

The Authoring Tool Accessibility Guidelines (ATAG) 2.0 provide success criteria for ensuring that content authoring tools are both more accessible to authors with disabilities (Part A) and designed to enable, support, and promote the production of more accessible web content by all authors (Part B).

Part A Success Criteria

As part of the ICT Accessibility Policy procurement process, Syracuse University relies on the Web Content Accessibility Guidelines 2.x (Levels A and AA) to assess conformance with ATAG Part A. See the WCAG 2.x A/AA Accessibility Checklist for Web-based Software (.docx)

Part B Success Criteria

The following ATAG Part B success criteria should be evaluated in addition to the WCAG 2.1 success criteria when the software being evaluated is an authoring tool. A formal evaluation checklist is still under development but will be linked from this page shortly.


B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG)

If the authoring tool provides the functionality for automatically generating web content during an authoring session, then at least one of the following is true:

a)    Accessible: The content is accessible web content (WCAG) without author input; or

b)    Prompting: During the automatic generation process, authors are prompted for any required accessibility information (WCAG); or

c)    Automatic Checking: After the automatic generation process, accessibility checking is automatically performed; or

d)    Checking Suggested: After the automatic generation process, the authoring tool prompts authors to perform accessibility checking.

Note 1: Automatic generation includes automatically selecting templates for authors.

Note 2: This success criterion applies only to automatic processes specified by the authoring tool developer. It does not apply when author actions prevent generation of accessible web content (WCAG)

B.1.2.3 Optimizations Preserve Accessibility

If the authoring tool provides optimizing web content transformations, then any accessibility information (WCAG) in the input is preserved in the output. (Level A).


 B.2.1.1 Accessible Content Possible (WCAG)

The authoring tool does not place restrictions on the web content that authors can specify or those restrictions do not prevent WCAG 2.x success criteria from being met. (Level A to meet WCAG 2.x Level A success criteria; Level AA to meet WCAG 2.x Level A and AA success criteria; Level AAA to meet all WCAG 2.x success criteria)


B.2.2.1 Accessible Option Prominence (WCAG)

If authors are provided with a choice of authoring actions for achieving the same authoring outcome (e.g. styling text), then options that will result in accessible web content (WCAG) are at least as prominent as options that will not. (Level A to meet WCAG 2.x Level A success criteria; Level AA to meet WCAG 2.x Level A and AA success criteria; Level AAA to meet all WCAG 2.x success criteria)


B.2.2.2 Setting Accessibility Properties (WCAG)

If the authoring tool provides mechanisms to set web content properties (e.g. attribute values), then mechanisms are also provided to set web content properties related to accessibility information (WCAG). (Level A to meet WCAG 2.x Level A success criteria; Level AA to meet WCAG 2.x Level A and AA success criteria; Level AAA to meet all WCAG 2.x success criteria)


B.2.3.1 Alternative Content is Editable (WCAG)

If the authoring tool provides functionality for adding non-text content, then authors are able to modify programmatically associated text alternatives for non-text content. (Level A to meet WCAG 2.x Level A success criteria; Level AA to meet WCAG 2.x Level A and AA success criteria; Level AAA to meet all WCAG 2.x success criteria)

Note: An exception can be made when the non-text content is known to be decoration, formatting, invisible or a CAPTCHA.


B.2.3.3 Save for Reuse

 If the authoring tool provides the functionality for adding non-text content, when authors enter programmatically associated text alternatives for non-text content, then both of the following are true: (Level AAA)

(a) Save and Suggest: The text alternatives are automatically saved and suggested by the authoring tool, if the same non-text content is reused; and

(b) Edit Option: The author has the option to edit or delete the saved text alternatives.


B.2.4.1 Accessible Template Options (WCAG)

If the authoring tool provides templates, then there are accessible template (WCAG) options for a range of template uses. (Level A to meet WCAG 2.x Level A success criteria; Level AA to meet WCAG 2.x Level A and AA success criteria; Level AAA to meet all WCAG 2.x success criteria)

B.2.5.1 Accessible Pre-Authored Content Options

If the authoring tool provides pre-authored content, then a range of accessible pre-authored content (to WCAG Level AA) options are provided. (Level AA)

B.2.5.2 Identify Pre-Authored Content Accessibility

If the authoring tool includes a pre-authored content selection mechanism and provides any non-accessible pre-authored content (WCAG Level AA) options, then the selection mechanism can display distinctions between the accessible and non-accessible options. (Level AA)

B.3.1.2 Help Authors Decide

If the authoring tool provides accessibility checking that relies on authors to decide whether potential web content accessibility problems (WCAG) are correctly identified (i.e. manual checking and semi-automated checking), then the accessibility checking process provides instructions that describe how to decide. (Level A)

 

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'ivy-ai' is unknown.