Drupal compliance overview of ATAG 2.0

PART A. Make the Drupal user interface accessible

Part A Conformance Applicability Notes:

1. Scope of "authoring tool user interface": The Part A success criteria apply to all aspects of the Drupal user interface that are concerned with producing the web content technologies. This includes views of the web content being edited and features that are independent of the content being edited, such as menus, button bars, status bars, user preferences, documentation, etc.
2. Reflected content accessibility problems: Drupal is responsible for ensuring that editing-views display the web content being edited in a way that is accessible to authors with disabilities (e.g. ensuring that text alternatives in the content can be programmatically determined. However, where an accessibility problem is caused directly by the content being edited (e.g. if an image in the content lacks a text alternative), then this would not be considered a deficiency in the accessibility of the Drupal interface.
3. Developer control: The Part A success criteria only apply to the Drupal user interface as it is provided by the developer. They do not apply to any subsequent modifications by parties other than the authoring tool developer (e.g. by plug-ins, user modifications, etc.).
4. User agent features: Web-based authoring tools may rely on user agent features (e.g. keyboard navigation, find functions, display preferences, undo features, etc.) to satisfy success criteria. If a conformance claim is made for a web-based authoring tool, the claim must cite the user agent.
5. Features for meeting Part A must be accessible: The Part A success criteria apply to the entire Drupal interface, including any features added to meet the success criteria in Part A (e.g. documentation, search functions, etc.). The only exemption is for preview features, as long as they meet the relevant success criteria in Guideline A.3.7. Previews are treated differently than editing-views because all authors, including those with disabilities, benefit when preview features accurately reflect the functionality of user agents that are actually in use by end users.

PRINCIPLE A.1: Drupal user interfaces must follow applicable accessibility guidelines

Guideline A.1.1: (For the Drupal user interface) Ensure that web-based functionality is accessible.

[Implementing A.1.1]

Rationale: When authoring tools (or parts of authoring tools) are web-based, conforming to WCAG 2.0 will facilitate access by all authors, including those using assistive technologies.

A.1.1.1 Web-Based Accessible (WCAG):

Web-based Drupal user interfaces meet the WCAG 2.0 success criteria. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

Implementing A.1.1.1

Guideline A.1.2: (For the Drupal user interface) Ensure that non-web-based functionality is accessible.

[Implementing A.1.2]

Rationale: When authoring tools (or parts of authoring tools) are non-web-based, following existing accessibility guidelines and implementing communication with platform accessibility services facilitates access by all authors, including those using assistive technologies.

A.1.2.1 Accessibility Guidelines:

Non-web-based Drupal user interfaces follow user interface accessibility guidelines for the platform. (Level A)

• Note: If a conformance claim is made, then the claim must cite the accessibility guidelines followed.

Implementing A.1.2.1

A.1.2.2 Platform Accessibility Services:

Non-web-based authoring tools implement communication with platform accessibility services. (Level A)

• Note: If a conformance claim is made, then the claim must cite the platform accessibility service(s) implemented.

PRINCIPLE A.2: Editing-views must be perceivable

Guideline A.2.1: (For the Drupal user interface) Make alternative content available to authors.

[Implementing A.2.1]

Rationale: Some authors require access to alternative content in order to interact with the web content that they are editing.

A.2.1.1 Text Alternatives for Rendered Non-Text Content:

If an editing-view renders non-text content with programmatically associated text alternatives, then the text alternatives can be programmatically determined. (Level A)

Implementing A.2.1.1

A.2.1.2 Alternatives for Rendered Time-Based Media:

If an editing-view renders time-based media, then at least one of the following is true: (Level A)

• (a) Alternatives Rendered: Alternatives for the time-based content are also rendered; or
• (b) User Agent Option: Authors have the option to preview the time-based content in a user agent that is able to render the alternatives.

Implementing A.2.1.2

Guideline A.2.2: (For the Drupal user interface) Editing-view presentation can be programmatically determined.

[Implementing A.2.2]

Rationale: Some authors need access to details about the editing-view presentation, via their assistive technology, when that presentation is used to convey status information (e.g. underlining misspelled words) or provide information about how the end user will experience the web content being edited.

A.2.2.1 Editing-View Status Information:

If an editing-view modifies the presentation to convey status information, then that status information can be programmatically determined. Status information conveyed by modifying the presentation of editing-views may include, but is not limited to, spelling, grammar and syntax errors. (Level A)

Implementing A.2.2.1

A.2.2.2 Access to Rendered Text Properties:

If a text property is both rendered and editable and the text property is supported by the implemented platform accessibility service, then the property is programmatically determinable. (Level A)

Implementing A.2.2.2

PRINCIPLE A.3: Editing-views must be operable

Guideline A.3.1: (For the Drupal user interface) Provide keyboard access to authoring features. [Implementing A.3.1]

Rationale: Some authors with
limited mobility or visual disabilities are not able to use a mouse, and instead require keyboard access to all of the functionality of Drupal.

A.3.1.1 Keyboard Access (Minimum):

All functionality of Drupal is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)

• Note 1: The path exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input, but the underlying function (text input) does not. The path exception encompasses other input variables that are continuously sampled from pointing devices, including pressure, speed, and angle.
• Note 2: This success criterion does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

Implementing A.3.1.1

A.3.1.2 No Keyboard Traps:

Keyboard traps are prevented as follows: (Level A)

• (a) In the Drupal user interface: If keyboard focus can be moved to a component using a keyboard interface, then focus can be moved away from that component using only a keyboard interface and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away; and
• (b) In Editing-Views that Render Content: If an editing-view renders content (e.g. WYSIWYG view), then a documented keyboard command is provided that moves the editing-view keyboard focus to a known location (e.g. the start of the editing-view).

Implementing A.3.1.2

A.3.1.3 Efficient Keyboard Access:

The Drupal user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access . (Level AA)

Implementing A.3.1.3

A.3.1.4 Keyboard Access (Enhanced):

All functionality of Drupal is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA)

Implementing A.3.1.4

A.3.1.5 Customize Keyboard Access:

Keyboard access to Drupal can be customized. (Level AAA)

Implementing A.3.1.5

A.3.1.6 Present Keyboard Commands:

Drupal user interface components can be presented with any associated keyboard commands. (Level AAA)

Implementing A.3.1.6

Guideline A.3.2: (For the Drupal user interface) Provide authors with enough time.

[Implementing A.3.2]

Rationale: Some authors who have difficulty typing, operating the mouse, or processing information can be prevented from using systems with short time limits or that require fast reaction speeds, such as clicking on a moving target.

A.3.2.1 Auto-Save (Minimum):

If Drupal includes authoring session time limits, then Drupal can be set to automatically save web content edits made using Drupal before the session time limits are reached. (Level A)

Implementing A.3.2.1

A.3.2.2 Timing Adjustable:

If a time limit is set by Drupal, then at least one of the following is true: (Level A)

• (a) Turn Off: Authors are allowed to turn off the time limit before encountering it; or
• (b) Adjust: Authors are allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
• (c) Extend: Authors are warned before time expires and given at least 20 seconds to extend the time limit with a simple action (e.g. "press the space bar"), and authors are allowed to extend the time limit at least ten times; or
• (d) Real-time Exception: The time limit is a required part of a real-time event (e.g. a collaborative authoring system), and no alternative to the time limit is possible; or
• (e) Essential Exception: The time limit is essential and extending it would invalidate the activity; or
• (f) 20 Hour Exception: The time limit is longer than 20 hours.

Implementing A.3.2.2

A.3.2.3 Static Pointer Targets:

Drupal user interface components that accept
pointer input are either stationary or authors can pause the movement. (Level A)

Implementing A.3.2.3

A.3.2.4 Content Edits Saved (Extended):

Drupal can be set to automatically save web content edits made using Drupal. (Level AAA)

Implementing A.3.2.4

Guideline A.3.3: (For the Drupal user interface) Help authors avoid flashing that could cause seizures.

[Implementing A.3.3]

Rationale: Flashing can cause seizures in authors with photosensitive seizure disorder.

A.3.3.1 Static View Option:

Editing-views that render visual time-based content can be paused and can be set to not play automatically. (Level A)

Implementing A.3.3.1

Guideline A.3.4: (For the Drupal user interface) Enhance navigation and editing via content structure.
[Implementing A.3.4]

Rationale: Some authors who have difficulty typing or operating the mouse benefit when authoring tools make use of the structure present in web content to simplify the tasks of navigation and editing the content.

A.3.4.1 Navigate By Structure:

If editing-views expose the markup elements in the web content being edited, then the markup elements (e.g. source code, content renderings, etc.) are selectable and navigation mechanisms are provided to move the selection focus between elements. (Level AA)

Implementing A.3.4.1

A.3.4.2 Navigate by Programmatic Relationships:

If editing-views allow editing of programmatic relationships within web content, then mechanisms are provided that support navigation between the related content. Depending on the web content technology and the nature of Drupal, relationships may include, but are not limited to, element nesting, headings, labeling, programmatic definitions, and ID relationships. (Level AAA)

Implementing A.3.4.2

Guideline A.3.5: (For the Drupal user interface) Provide text search of the content.
[Implementing A.3.5]

Rationale: Some authors who have difficulty typing or operating the mouse benefit from the ability to use text search to navigate to arbitrary points within the web content being authored.

A.3.5.1 Text Search:

Editing-views enable text search, such that all of the following are true: (Level AA)

• (a) All Editable Text: Any text content that is editable by the editing-view is searchable (including alternative content); and
• (b) Match: Matching results can be made visible to authors and given focus; and
• (c) No Match: Authors are informed when no results are found; and
• (d) Two-way: The search can be made forwards or backwards; and
• (e) Case Sensitive: The search can be in both case sensitive and case insensitive modes.

Implementing A.3.5.1

Guideline A.3.6: (For the Drupal user interface) Manage preference settings.
[Implementing A.3.6]

Rationale: Some authors need to set their own display settings in a way that differs from the presentation that they want to define for the published web content. Providing the ability to save and reload sets of keyboard and display preference settings benefits authors who have needs that differ over time (e.g. due to fatigue).

A.3.6.1 Independence of Display:

If Drupal includes display settings for editing-views, then Drupal allows authors to adjust these settings without affecting the web content to be published. (Level A)

Implementing A.3.6.1

A.3.6.2 Save Settings:

If Drupal includes display and/or control settings, then these settings can be saved between authoring sessions. (Level AA)

Implementing A.3.6.2

A.3.6.3 Apply Platform Settings:

Drupal respects changes in platform display and control settings made by authors. (Level AA)

Implementing A.3.6.3

A.3.6.4 Multiple Sets:

If Drupal includes display and/or control settings, then authors can save and reload multiple sets of these settings. (Level AAA)

Implementing A.3.6.4

A.3.6.5 Assistance with Preferences:

If Drupal includes display and/or control settings, then Drupal includes a mechanism to help authors configure these settings. (Level AAA)

Implementing A.3.6.5

Guideline A.3.7: (For the Drupal user interface) Ensure that previews are as accessible as existing user agents.
[Implementing A.3.7]

Rationale: Preview features are provided in many authoring tools because the workflow of authors often includes periodically checking how user agents will display the web content to end users. Authors with disabilities need the same opportunity to check their work.

A.3.7.1 Preview (Minimum):

If a preview is provided, then at least one of the following is true: (Level A)

• (a) Pre-existing User Agent: The preview makes use of a pre-existing user agent; or
• (b) UAAG (Level A): The preview conforms to the User Agent Accessibility Guidelines Level A [UAAG].

Implementing A.3.7.1

A.3.7.2 Preview (Enhanced):

If a preview is provided, then authors can specify which user agent performs the preview. (Level AAA)

Implementing A.3.7.2

PRINCIPLE A.4: Editing-views must be understandable

Guideline A.4.1: (For the Drupal user interface) Help authors avoid and correct mistakes.

[Implementing A.4.1]

Rationale: Some authors with disabilities may be more susceptible to input errors due to factors such as difficulty making fine movements and speech recognition system errors.

A.4.1.1 Content Changes Reversible (Minimum):

For authoring actions, one of the following is true: (Level A)

• (a) Reversible: The authoring action can be immediately reversed; or
• (b) Warn and Confirm: Drupal provides a warning to authors that the action is irreversible and requires authors to confirm the action before proceeding.

• Note 1: Reversing actions (e.g. an "undo" function) are also considered authoring actions, meaning they must also meet this success criterion (e.g. a "redo" function).
• Note 2: It is acceptable to collect a series of text entry actions (e.g. typed words, a series of backspaces) into a single reversible authoring action.
• Note 3: It is acceptable to clear the authoring action history at the end of authoring sessions.

Implementing A.4.1.1

A.4.1.2 Setting Changes Reversible:

If actions modify authoring tool settings, then one of the following is true: (Level A)

• (a) Reversible: Drupal setting can be reversed by the same mechanism that made the change; or
• (b) Warn and Confirm: Drupal provides a warning to authors that the setting change is irreversible and requires authors to confirm or save the current settings before proceeding.

Implementing A.4.1.2

This seems to need a rewrite of the admin interface of Drupal as many settings doesn't provide a warning or reversible mechanism that settings will be overwritten.
In most (all?) cases a warning/cancel is implemented for deleting elements.

A.4.1.3 Content Changes Reversible (Enhanced):

Authors can sequentially reverse a series of reversible authoring actions. (Level AAA)

• Note: The notes for A.4.1.1 still apply.

Implementing A.4.1.3

Guideline A.4.2: (For the Drupal user interface) Document the user interface including all accessibility features.

[Implementing A.4.2]

Rationale: Some authors may not be able to understand or operate the Drupal user interface without proper accessible documentation.

A.4.2.1 Document Accessibility Features:

All features of Drupal that must be present to meet Part A of ATAG 2.0 (e.g. keyboard shortcuts, text search, etc.) are documented. (Level A)

• Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.

Implementing A.4.2.1

A.4.2.2 Document All Features:

Drupal includes documentation for its author-level user interface features. (Level AA)

• Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.

Implementing A.4.2.2

PART B: Support the production of accessible content

Part B Conformance Applicability Notes:

1. Author availability: Any Part B success criteria that refer to authors only apply during authoring sessions.
2. Developer control: The Part B success criteria only apply to Drupal as it is provided by the developer. This does not include subsequent modifications by parties other than Drupal developer (e.g. by plug-ins, user-defined templates, user modifications of default settings, etc.).
3. Applicability after the end of an authoring session: Authoring tools are responsible for the accessibility of web content that they automatically generate after the end of an author's authoring session (see Success Criterion B.1.1.1). For example, if the developer changes the site-wide templates of a content management system, these would be required to meet the accessibility requirements for automatically-generated content. Authoring tools are not responsible for changes to the accessibility of content that the author has specified, whether it is author-generated or automatically-generated by another system that the author has specified (e.g. a third-party feed).
4. Authoring systems: As per the ATAG 2.0 definition of authoring tool, several software tools (identified in any conformance claim) can be used in conjunction to meet the requirements of Part B (e.g. an authoring tool could make use of a third-party software accessibility checking tool).
5. Features for meeting Part B must be accessible: The Part
   A success criteria apply to the entire Drupal user interface, including any features that must be present to meet the success criteria in Part B (e.g. checking tools, repair tools, tutorials, documentation, etc.).
6. Multiple author roles: Some authoring tools include multiple author roles, each with different views and content editing permissions (e.g. a content management system may separate the roles of designers, content authors, and quality assurers). In these cases, the Part B success criteria apply to Drupal as a whole, not to the view provided to any particular author role. Accessible content support features should be made available to any author role where it would be useful.

PRINCIPLE B.1: Fully automatic processes must produce accessible content

Guideline B.1.1: Ensure automatically specified content is accessible. [Implementing B.1.1]

Rationale: If authoring tools automatically specify web content that is not accessible, then additional repair tasks are imposed on authors.

B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG):

Authors have the default option that, when web content is automatically generated for publishing after the end of an authoring session, it is accessible web content (WCAG). (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• Note: This success criterion applies only to automatic processes specified by Drupal developer. It does not apply when author actions prevent generation of accessible web content.

Implementing B.1.1.1

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

Authors have the default option that, when web content is automatically generated during an authoring session, then one of the following is true: (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• (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, Drupal 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 Drupal developer. It does not apply when author actions prevent generation of accessible web content.

Implementing B.1.1.2

Guideline B.1.2: Ensure accessibility information is preserved. [Implementing B.1.2]

Rationale: Accessibility information is critical to maintaining comparable levels of accessibility between the input and output of web content transformations.

B.1.2.1 Restructuring and Recoding Transformations (WCAG):

If Drupal provides restructuring transformations or re-coding transformations, then at least one of the following is true: (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• (a) Preserve: Accessibility information (WCAG) is preserved in the output; or
• (b) Warning: Authors have the default option to be warned that accessibility information may be lost (e.g. when saving a vector graphic into a raster image format); or
• (c) Automatic Checking: After the transformation, accessibility checking is automatically performed; or
• (d) Checking Suggested: After the transformation, Drupal prompts authors to perform accessibility checking.

• Note: This success criteria only applies to transformations in which the output technology is an "included" technology for conformance.

Implementing B.1.2.1

B.1.2.2 Optimizations Preserve Accessibility:

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

Implementing B.1.2.2

B.1.2.3 Text Alternatives for Non-Text Content are Preserved:

If Drupal provides web content transformations that preserve non-text content in the output, then any web content technology of the output. (Level A).

Implementing B.1.2.3

PRINCIPLE B.2: Authors must be supported in producing accessible content

Guideline B.2.1: Ensure accessible content production is possible.

[Implementing B.2.1]

Rationale: For the purposes of this document, WCAG 2.0 defines the accessible web content (WCAG) requirements. To support accessible web content production, at minimum, it must be possible to produce web content that conforms with WCAG 2.0 using Drupal.

B.2.1.1 Accessible Content Possible (WCAG):

If Drupal places restrictions on the web content that authors can specify, then those restrictions do not prevent WCAG 2.0 success criteria from being met.. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

Implementing B.2.1.1

Guideline B.2.2: Guide authors to produce accessible content.
[Implementing B.2.2]

Rationale: By guiding authors from the outset toward the creation and maintenance of accessible web content (WCAG) , web content accessibility problems (WCAG) are mitigated and less repair effort is required.

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 accessible web content (WCAG) are at least as prominent as options that will not. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

Implementing B.2.2.1

B.2.2.2 Setting Accessibility Properties (WCAG):

If Drupal provides mechanisms to set web content properties (e.g. attribute values, etc.), then mechanisms are also provided to set web content properties related to accessibility information (WCAG): (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• Note: Success Criterion B.4.1.4 addresses the prominence of the mechanisms.

Implementing B.2.2.2

B.2.2.3 Technology Decision Support:

If Drupal provides the web content technology for publishing for which the authoring tool does not provide support for the production of accessible content, then both of the following are true: (Level A)

• (a) Warning: Authors are warned that Drupal does not provide support for the production of accessible content for that technology; and
• (b) List: From the warning, authors can access a list of technologies for which Drupal does provide support for the production of accessible content.

Implementing B.2.2.3

Guideline B.2.3: Assist authors with managing alternative content for non-text content.
[Implementing B.2.3]

Rationale: Improperly generated alternative content can create accessibility problems and interfere with accessibility checking.

See Also: This guideline applies when non-text content is specified by authors (e.g. inserts an image). When non-text content is automatically added by Drupal, see Guideline B.1.1.

B.2.3.1 Alternative Content is Editable (WCAG):

Authors are able to modify programmatically associated text alternatives for non-text content. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

Implementing B.2.3.1

B.2.3.2 Conditions on Automated Suggestions:

During the authoring session, Drupal may only automatically suggest programmatically associated text alternatives for non-text content under the following conditions: (Level A)

• (a) Author Control: Authors have the opportunity to accept, modify, or reject the suggested text alternatives prior to insertion; and
• (b) Relevant Sources: The suggested text alternatives are only derived from sources designed to fulfill the same purpose (e.g. suggesting the value of an image's "description" metadata field as a long description).

Implementing B.2.3.2

B.2.3.3 Let User Agents Repair:

Drupal avoids repairing programmatically associated user agents (e.g. do not use the image filename). (Level A)

Implementing B.2.3.3

B.2.3.4 Save for Reuse:

When authors enter programmatically associated text alternatives for non-text content, both of the following are true: (Level AAA)

• (a) Save and Suggest: the text alternatives are automatically saved and suggested by Drupal, 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.

Implementing B.2.3.4

Guideline B.2.4: Assist authors with accessible templates.

[Implementing B.2.4]

Rationale: Providing accessible templates and other pre-authored content (e.g. clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the accessibility of web content being edited, reducing the effort required of authors, and demonstrating the importance of accessible web content (WCAG) .

B.2.4.1 Accessible Template Options (WCAG):

If Drupal provides templates, then there are accessible template (WCAG) range of template uses. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• Note: It is recommended that the accessible options be identified, but this is not required.

Implementing B.2.4.1

B.2.4.2 Identify Template Accessibility (Minimum):

If Drupal includes a template selection mechanism and provides any non-accessible template (WCAG) templates are provided such that the template selection mechanism can display distinctions between the accessible and non-accessible options. (Level AA)

• Note: The distinction can involve providing information for the accessible templates, the non-accessible templates or both.

Implementing B.2.4.2

B.2.4.3 Author-Create Templates:

If Drupal 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. (Level AA)

• Note: The distinction can involve providing information for the accessible templates, the non-accessible templates or both.

Implementing B.2.4.3

B.2.4.4 Identify Template Accessibility (Enhanced):

If Drupal provides any non-accessible templates (WCAG) template selection mechanism, then the non-accessible templates include accessibility warnings within the templates. (Level AAA)

Implementing B.2.4.4

Guideline B.2.5: Assist authors with accessible pre-authored content. [Implementing B.2.5]

Rationale: Providing accessible templates and other pre-authored content (e.g. clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the accessibility of web content being edited, reducing the effort required of authors, and demonstrating the importance of accessible web content (WCAG).

B.2.5.1 Pre-Authored Content Selection Mechanism:

If authors are provided with a selection mechanism for pre-authored content other than templates (e.g. clip art gallery, widget repository, design themes), then both of the following are true: (Level AA)

• (a) Indicate: The selection mechanism indicates the accessibility status of the pre-authored content (if known); and
• (b) Prominence: Any accessible options are at least as prominent as other pre-authored content options.

Implementing B.2.5.1

B.2.5.2 Pre-Authored Content Accessibility Status:

If Drupal provides a repository of pre-authored content, then each of the content objects has a recorded accessibility status. (Level AAA)

Implementing B.2.5.2

PRINCIPLE B.3: Authors must be supported in improving the accessibility of existing content

Guideline B.3.1: Assist authors in checking for accessibility problems. [Implementing B.3.1]

Rationale: Accessibility checking as an integrated function of Drupal helps make authors aware of web content accessibility problems during the authoring process, so they can be immediately addressed.

B.3.1.1 Checking Assistance (WCAG):

If Drupal provides authors with the ability to add or modify web content so that a WCAG 2.0 success criterion can be violated, then accessibility checking for that success criterion is provided (e.g. an HTML authoring tool that inserts images should check for alternative text; a video authoring tool with the ability to edit text tracks should check for captions). (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• Note: Automated and semi-automated checking is possible (and encouraged) for many types of web content accessibility problems. However, manual checking is the minimum requirement to meet this success criterion. In manual checking, Drupal provides authors with instructions for detecting problems, which authors must carry out by themselves. For more information on checking, see Implementing ATAG 2.0 - Appendix B: Levels of Checking Automation.

Implementing B.3.1.1

B.3.1.2 Help Authors Decide:

For checks that require authors to decide whether a potential web content accessibility problem is correctly identified (i.e. manual checking and semi-automated checking), instructions are provided from the check that describe how to make the decision. (Level A)

Implementing B.3.1.2

B.3.1.3 Help Authors Locate:

For checks that require authors to decide whether a potential web content accessibility problem is correctly identified (i.e. manual checking and semi-automated checking), the relevant content is identified to the authors. (Level A)

• Note: Depending on the nature of the editing-view and the scope of the potential web content accessibility problem, identification might involve highlighting elements or renderings of elements, displaying line numbers, or providing instructions.

Implementing B.3.1.3

B.3.1.4 Status Report:

Authors can receive an accessibility status report based on the results of the accessibility checks. (Level AA)

• Note: The format of the accessibility status is not specified. For example, the status might be a listing of problems detected or a WCAG 2.0 conformance level, etc.

Implementing B.3.1.4

B.3.1.5 Programmatic Association of Results:

Authoring tools can programmatically associate accessibility checking results with the web content that was checked. (Level AA)

Implementing B.3.1.5

Guideline B.3.2: Assist authors in repairing accessibility problems. [Implementing B.2.3]

Rationale: Repair as an integral part of the authoring process greatly enhances the utility of checking and increases the likelihood that accessibility problems will be properly addressed.

B.3.2.1 Repair Assistance (WCAG):

If checking (see Success Criterion B.3.1.1) can detect that a WCAG 2.0 success criterion is not met, then repair suggestion(s) are provided: (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• Note: Automated and semi-automated repair is possible (and encouraged) for many types of web content accessibility problems. However, manual repair is the minimum requirement to meet this success criterion. In manual repair, Drupal provides authors with instructions for repairing problems, which authors must carry out by themselves. For more information on repair, see Implementing ATAG 2.0 - Appendix C: Levels of Repair Automation.

Implementing B.3.2.1

PRINCIPLE B.4: Authoring tools must promote and integrate their accessibility features

Guideline B.4.1: Ensure the availability of features that support the production of accessible content.

[Implementing B.4.1]

Rationale: The accessible content support features will be more likely to be used if they are turned on and are afforded reasonable prominence within the Drupal user interface.

B.4.1.1 Features Active by Default:

All accessible content support features are turned on by default. (Level A)

Implementing B.4.1.1

B.4.1.2 Option to Reactivate Features:

If authors can turn off an accessible content support feature, then they can turn the feature back on. (Level A)

Implementing B.4.1.2

B.4.1.3 Feature Deactivation Warning:

If authors turn off an accessible content support feature, then Drupal informs them that this may increase the risk of content accessibility problems. (Level AA)

Implementing B.4.1.3

B.4.1.4 Feature Prominence:

Accessible content support features are at least as prominent as features related to either invalid markup, syntax errors, spelling errors or grammar errors. (Level AA)

Implementing B.4.1.4

Guideline B.4.2: Ensure that documentation promotes the production of accessible content.

[Implementing B.4.2]

Rationale: Without documentation of the features that support the production of accessible content (e.g. prompts for text alternatives, accessibility checking tools), some authors may not be able to use them. Demonstrating accessible authoring as routine practice will encourage its acceptance by some authors.

B.4.2.1 Model Practice (WCAG):

A documentation (e.g. markup, screen shots of WYSIWYG editing-views) demonstrate accessible authoring practices that meet the WCAG 2.0 success criteria. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

Implementing B.4.2.1

B.4.2.2 Feature Instructions:

Instructions for using the accessible content support features appear in the documentation. (Level A)

Implementing B.4.2.2

B.4.2.3 Tutorial:

A tutorial on an accessible authoring process that is specific to Drupal is provided. (Level AAA)

Implementing B.4.2.3

B.4.2.4 Instruction Index:

The documentation contains an index to the instructions for using the accessible content support features. (Level AAA)

Implementing B.4.2.4