Principle B2: Authors are supported in producing accessible content

Guideline B2.1: Ensure that accessible content production is possible

B2.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.0 success criteria from being met.

The intent of this success criterion is to make sure that authors who want to and are capable of producing accessible content, are not prevented from doing so by restricting what they can do. For example, they should be able to select and use attributes that support accessibility.

Guideline B2.2: Guide authors to produce accessible content

B2.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.

The intent of this success criterion is to enable authors to use default workflow options to create accessible content. For example, in Word, headings can be styled from the Home ribbon and the Heading Styles are also on the Home ribbon, and are just as easy to see and access.

B2.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).

The intent of this success criterion is that authoring tools provide accessibility-related attribute options in things like pop-up dialogues, if these are available for general tasks. For example, if there is a dialogue box for table attributes, it should allow users to give the table a name or caption, and to assign column and row headers.

Guideline B2.3: Assist authors with managing alternative content for non-text content

B2.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.

The intent of this success criterion is to allow authors to add and edit alt text and other alternatives for non-text content.

B2.3.2 Automating Repair of Text Alternatives (Level A)

The authoring tool does not attempt to repair text alternatives for non-text content or the following are all true:

No Generic or Irrelevant Strings

Generic strings (e.g. "image") and irrelevant strings (e.g. the file name, file format) are not used as text alternatives; and

In-Session Repairs

If the repair attempt occurs during an authoring session, authors have the opportunity to accept, modify, or reject the repair attempt prior to insertion of the text alternative into the content; and

Out-of-Session Repairs

If the repair attempt occurs after an authoring session has ended, the repaired text alternatives are indicated during subsequent authoring sessions (if any) and authors have the opportunity to accept, modify, or reject the repair strings prior to insertion in the content.

The intent of this success criterion is to prevent alt text from being generated, which is not useful. This would include automatically generated alt text, which may include generic words like image, or a file name. Any automatically generated alt text should be checked and accepted by the author where possible.

I think a good example of this is the automatically generated alt text that Facebook creates. It always begins with the phrase, May be an image of..., which is generic and not useful.

Guideline B2.4: Assist authors with accessible templates

B2.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.

The intent of this success criterion is to ensure that accessible templates are available (if templates are provided). Authors should not be in a situation where they have to select a template which is not accessible.

B2.4.2 Identify Template Accessibility (Level AA)

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

The intent of this success criterion is to make it easy for authors to know which templates are accessible and which are not. They should be able to make an informed choice and select an accessible template if they want to.

B2.4.3 Author-Created Templates (Level AA)

If the authoring tool includes a template selection mechanism and allows authors to create new non-accessible templates (WCAG), then authors can enable the template selection mechanism to display distinctions between accessible and non-accessible templates that they create.

The intent of this success criterion is to ensure that any templates that authors create, which may then be used by other authors, can be identified as accessible or inaccessible.

Guideline B2.5: Assist authors with accessible pre-authored content

B2.5.1 Accessible Pre-Authored Content Options (Level AA)

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

The intent of this success criterion is to ensure that authors can select accessible pre-authored content, where pre-authored content exists. For example, Articulate 360 has an extensive range of royalty-free images and video. At least some of these should have appropriate alt text and captions.

B2.5.2 Identify Pre-Authored Content Accessibility (Level AA)

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.

The intent of this success criterion is to ensure that authors know which pre-authored content is and isn't accessible.