W3C

ATAG 2.0 Implementation Report

12 May 2011

Editors:
Jan Richards - IDRC, OCAD University

Authoring Tools

IMPORTANT NOTES:

Handle Details Notes and URIs Contributor(s)
Lotus Tools     Sueann N.
Amaya     Jeanne Spellman
Dreamweaver CS5    

Greg Pisocky

Acrobat 9     Greg Pisocky
Defacto CMS Web application http://www.nomensa.com/web-design/defacto-content-management-system Alastair Campbell
TinyMCE3.2
  • TinyMCE v.3.2.x
  • with Accessibility plugin
  • producing XHTML 1.0
  • tested on IE8

 
  • Base application (http://tinymce.moxiecode.com/download.php)
  • Accessibility plugin (http://wiki.moxiecode.com/index.php/TinyMCE:Accessibility)
Jan Richards
Google Docs (Text) - 13Aug2010 HTML I looked at Google Docs but it seems to have quite a few issues (no keyboard access to menus, no ability to add alt, longdesc, no table captions, equations become images, real headings are not used, etc., etc.). Jan Richards
Drupal, Moodle, SAKAI ???     ???
DreamWeaver8 Producing HTML4   Jan Richards
Flash8 Producing Flash   Jan Richards
XStandard2.1 XStandard 2.1 used to produce XHTML 1.0   Vlad Alexander, Roberto Scano
WebAIM WAVE Checking HTML4 http://wave.webaim.org/ Jan Richards
AChecker Checking HTML4 http://achecker.ca/ Greg Gay, Jan Richards
Office2010   http://blogs.technet.com/office2010/archive/2010/01/07/office-2010-accessibility-investments-document-accessibility.aspx Jan Richards

Implementations by Checkpoints and Success Criteria

Conformance Applicability Notes:

For PART A: Make the authoring tool user interface accessible:

  1. Scope of "authoring tool user interface": The Part A success criteria apply to all aspects of the authoring tool user interface that are concerned with producing the "included" 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: The authoring tool 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 authoring tool user interface.
  3. Developer control: The Part A success criteria only apply to the authoring tool user interface as it is provided by the developer. It does 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, 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 authoring tool user 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.

For PART B: Support the production of accessible content :

  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 the authoring tool as it is provided by the developer. This does not include subsequent modifications by parties other than the authoring tool 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 authoring tool 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 the authoring tool 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.

Numbers of Implementations

Level A Success Criteria

Guideline Success Criteria Implementations Info
A.1.1 (For the authoring tool user interface) Ensure that web-based functionality is accessible. A.1.1.1 Web-Based Accessible (WCAG A): Web-based authoring tool user interfaces meet the WCAG 2.0 success criteria. @Several
  • TinyMCE3.2
  • Defacto CMS
  • MoodleLMS?, DrupalCMS?, ATutorLCMS?
A.1.2 (For the authoring tool user interface) Ensure that non-web-based functionality is accessible. A.1.2.1 Accessibility Guidelines: Non-web-based authoring tool user interfaces follow user interface accessibility guidelines for the platform.
Note: If a conformance claim is made, then the claim must cite the accessibility guidelines followed. 		@At-least-one
  • XStandard2.1
  • iPhone apps? Annotate (Steve H)? MS2010?
A.1.2.2 Platform Accessibility Services: Non-web-based authoring tools implement communication with platform accessibility services.
Note: If a conformance claim is made, then the claim must cite the platform accessibility service(s) implemented.		 @At-least-one
  • XStandard2.1 (MSAA support)
  • iPhone apps? Annotate (Steve H)? MS2010?
A.2.1 (For the authoring tool user interface) Make alternative content available to authors. 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. @Several
  • TinyMCE3.2 (via browser)
  • DreamWeaver8
  • XStandard2.1
  • Defacto CMS
  • MoodleLMS?, DrupalCMS?, ATutorLCMS?
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 agents that is able to render the alternatives.		 @None-confirmed
A.2.2 (For the authoring tool user interface) Editing view presentation can be programmatically determined. 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. @At-least-one
  • WAVE (adds information icons throughout the checked webpage)
  • XMetal? Office2010 spelling?
A.2.2.2 Access to Rendered Text Properties: If a text property is both rendered and editable and the property can be communicated by the supported platform accessibility service, then the property is programmatically determinable. @At-least-one
  • TinyMCE3.2 (via browser)
  • MoodleLMS?, DrupalCMS?, ATutorLCMS? (note: Use MSAA Inspect tool to test on Windows)
A.3.1 (For the authoring tool user interface) Provide keyboard access to authoring features. A.3.1.1 Keyboard Access (Minimum): All functionality of the authoring tool 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.
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.		 @Several
  • TinyMCE3.2
  • Dreamweaver8
  • Defacto CMS
  • MS2010? AtutorLCMS? Sakai3.0?
A.3.1.2 No Keyboard Traps: Keyboard traps are prevented as follows: (Level A)
(a) In the Authoring Tool 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).		 @Several
  • TinyMCE3.2 (relying on browser for (b))
  • Dreamweaver8
  • Flash8
  • Defacto CMS
  • MoodleLMS?, DrupalCMS?, ATutorLCMS? (relying on browser for (b))
A.3.2 (For the authoring tool user interface) Provide authors with enough time. A.3.2.1 Content Edits Saved (Minimum): If the authoring tool includes authoring session time limits, then the authoring tool saves all edits made by authors. @At-least-one
  • TinyMCE3.2
  • ATutorLCMS (Scorm mode?)? DrupalCMS? MoodleLMS? Wikis?
A.3.2.2 Timing Adjustable: If a time limit is set by the authoring tool, then at least one of the following is true: (Level A) [Implementing A.3.2.2]
(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.		 @None-confirmed
  • ATutorLCMS (Scorm mode?)?
  • DrupalCMS?MoodleLMS? Wikis?
A.3.2.3 Static Pointer Targets: Authoring tool user interface components that accept pointer input are either stationary or authors can pause the movement. @Many
  • MS2010
  • Dreamweaver8
  • Acrobat
  • etc.
A.3.3 (For the authoring tool user interface) Help authors avoid flashing that could cause seizures. 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. @At-least-one
  • Flash8 (Timeline only plays on user request)
  • Maybe some web-based tools if rendering of dynanic objects turned off in browser
A.3.4 (For the authoring tool user interface) Enhance navigation and editing via content structure. 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. @Several
  • TinyMCE3.2 (using "Path" feature)
  • DreamWeaver8 ("Edit>Select Parent Tag", "Edit>Select Child")
  • Amaya? (JS)
A.3.6: (For the authoring tool user interface) Manage preference settings. A.3.6.1 Independence of Display: Authors can set their own display settings for editing-views without affecting the web content to be published. @Many
  • TinyMCE3.2 (since browser display settings are used)
  • Defacto CMS (via browser display settings)
  • XStandard2.1
  • DreamWeaver8
  • GoogleDocs
A.3.7 (For the authoring tool user interface) Ensure that previews are as accessible as existing user agents. A.3.7.1 Preview (Minimum): If a preview is provided, then at least one of the following is true: (Level A) [Implementing A.3.7.1]
(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].		 @Many (by (a))
  • XStandard2.1 (by (a))
  • TinyMCE3.2 (by (a))
  • DreamWeaver8 (by (a))
  • ATutorLCMS? (by (a))
  • Amaya? (JS)
A.4.1 (For the authoring tool user interface) Help users avoid and correct mistakes. A.4.1.1 Content Changes Reversible (Minimum): For authoring actions, one of the following are true: (Level A) [Implementing A.4.1.1]
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. (a) Reversible: The authoring action can be immediately reversed; or (b) Warn and Confirm: The authoring tool includes a warning to authors that the action is irreversible and requires authors to confirm the action before proceeding.		 @Many
  • XStandard2.1
  • TinyMCE3.2
  • DreamWeaver8 ("Edit>Undo")
  • Defacto CMS (warns before deleting content)
A.4.1.2 Setting Changes Reversible: If actions modify authoring tool settings, then one of the following are true:
(a) Reversible: The authoring tool setting can be reversed by the same mechanism that made the change; or
(b) Warn and Confirm: The authoring tool includes a warning to authors that the action is irreversible and requires authors to confirm the action or save the current settings before proceeding. 		@Many
  • XStandard2.1
  • TinyMCE3.2
  • DreamWeaver8 ("Edit>Undo")
  • Defacto CMS (warns before deleting content)
A.4.2 (For the authoring tool user interface) Document the user interface including all accessibility features. A.4.2.1 Document Accessibility Features: All features that must be present to meet Part A of ATAG 2.0 (e.g. keyboard shortcuts, text search, etc.) are documented.
Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.		 @At-least-one
  • MS2010
  • DreamWeaver8?
B.1.1: Ensure automatically specified content is accessible. B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG A): 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).
Note: 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.		 @At-least-one:
  • Defacto CMS (developer created templates display content listings)
  • ATutorLCMS?
B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG A): Authors have the default option that, when web content is automatically generated during an authoring session, then one of the following is true:
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.
(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. 		@At-least-one:
  • TinyMCE3.2
  • Defacto CMS (developer created templates display content listings)
  • ATutorLCMS? Dreamweaver8?
B.1.2: Ensure accessibility information is preserved. B.1.2.1 Restructuring and Recoding Transformations (WCAG A): If the authoring tool provides restructuring transformations or re-coding transformations, then at least one of the following is true:
Note: This success criteria only applies to transformations in which the output technology is an "included" technology for conformance.
(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, the authoring tool prompts authors to perform accessibility checking. 		@None-confirmed
B.1.2.2 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. @None-confirmed
B.1.2.3 Text Alternatives for Non-Text Content are Preserved: If the authoring tool provides web content transformations that preserve non-text content in the output, then any text alternatives for that non-text content are also preserved, if equivalent mechanisms exist in the web content technology of the output. @Several
  • Atutor (transformations from IEEE LOM to SCORM package etc.)
  • Acrobat (when exporting PDF from MS Word format)
  • TinyMCE when copying from MS Word? Final Cut Pro preserving captions?
B.2.1: Ensure accessible content production is possible. B.2.1.1 Accessible Content Possible (WCAG A): If the authoring tool places restrictions on the web content that authors can specify, then those restrictions do not prevent WCAG 2.0 success criteria from being met @Many
  • XStandard2.1
  • TinyMCE3.2
  • DreamWeaver8
  • Defacto CMS (Partly via TinyMCE, partly via templates)
B.2.2: Guide authors to produce accessible content. B.2.2.1 Accessible Option Prominence (WCAG A): 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. @At-least-one
  • Dreamweaver
  • Defacto CMS
B.2.2.2 Setting Accessibility Properties (WCAG A): If the authoring tool 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):
Note: Success Criterion B.4.1.4 addresses the prominence of the mechanisms.		 @None-confirmed
B.2.2.3 Technology Decision Support: If the authoring tool provides the option of producing a 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:
(a) Warning: Authors are warned that the authoring tool 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 the authoring tool does provide support for the production of accessible content.		 @None-confirmed
B.2.3: Assist authors with managing alternative content for non-text content. B.2.3.1 Alternative Content is Editable (WCAG A): Authors are able to modify programmatically associated text alternatives for non-text content. (Level A).
 @Many
  • TinyMCE3.2
  • Dreamweaver8
  • MS2010
  • XStandard2.1
  • Defacto CMS
B.2.3.2 Conditions on Automated Suggestions: During the authoring session, the authoring tool may only automatically suggest programmatically associated text alternatives for non-text content under the following conditions:
(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).		 @At-least-one
  • A-Prompt 1.0
B.2.3.3 Let User Agents Repair: The authoring tool avoids repairing programmatically associated text alternatives for non-text content using any text value that would also be available to user agents (e.g. do not use the image filename). @Many
  • TinyMCE3.2
  • Dreamweaver8
  • MS2010
  • XStandard2.1
B.2.4: Assist authors with accessible templates. B.2.4.1 Accessible Template Options (WCAG A): If the authoring tool provides templates, then there are accessible template options for a range of template uses. @Several
  • AtutorLCMS
  • Dreamweaver8
  • Defacto CMS
B.3.1: Assist authors in checking for accessibility problems. B.3.1.1 Checking Assistance (WCAG): If the authoring tool 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).
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, the authoring tool 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. 		@Several
  • TinyMCE3.2 (via button launching AChecker (WCAG 2.0 A option, including "Potential Problems" display))
  • WAVE
  • Acrobat Accessibility Checker
  • MSOffice2010
    Screenshot of MS2010 checker pane. The top section of the pane lists errors and warnings. Once an issue receives focus, the bottom area displays information about why it should be repaired and how.
B.3.2: Assist authors in repairing accessibility problems 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:
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, the authoring tool 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. 		@Several
  • TinyMCE3.2 (via button launching AChecker (WCAG 2.0 A option, including "Potential Problems" display)) (manual repair instructions)
  • MSOffice2010 (manual repair instructions with pointed to some semi-automated repair functionality)
    Screenshot of MS2010 checker pane. The top section of the pane lists errors and warnings. Once an issue receives focus, the bottom area displays information about why it should be repaired and how.
  • WAVE (Manual repair instructions are provided)
B.4.1: Ensure the availability of features that support the production of accessible content. B.4.1.1 Features Active by Default: All accessible content support features are turned on by default. @Several
  • TinyMCE3.2
  • Dreamweaver8
  • Defacto CMS
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. @Many
  • Dreamweaver8 (e.g., "Accessibility" preferences page)
  • TinyMCE3.2
  • AtutorLCMS
  • SAKAI 3.0 HTML Authoring Component?
B.4.2: Ensure that documentation promotes the production of accessible content B.4.2.1 Model Practice (WCAG A): A range of examples in the documentation (e.g. markup, screen shots of WYSIWYG editing-views) demonstrate accessible authoring practices that meet the WCAG 2.0 success criteria: @At-least-one
  • Defacto
B.4.2.2 Feature Instructions: Instructions for using the accessible content support features appear in the documentation. @Many
  • TinyMCE3.2
  • Dreamweaver8
  • AtutorLCMS
  • SAKAI 3.0 HTML Authoring Component?

Level AA Success Criteria

Guideline Success Criteria Implementations Info
A.1.1 (For the authoring tool user interface) Ensure that web-based functionality is accessible. A.1.1.1 Web-Based Accessible (WCAG AA): Web-based authoring tool user interfaces meet the WCAG 2.0 success criteria. @At-least-one
  • Defacto CMS (a couple of error messages to improve, but it's almost there assuming that TinyMCE passes as well)
  • TinyMCE3.2?
A.3.1 (For the authoring tool user interface) Provide keyboard access to authoring features. A.3.1.3 Efficient Keyboard Access: The authoring tool user interface includes mechanisms to make keyboard access more efficient than sequential keyboard navigation. @Many
  • TinyMCE3.2
  • Dreamweaver8
  • AtutorLCMS
  • Flash8?
A.3.4 (For the authoring tool user interface) Enhance navigation and editing via content structure. 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) @Several
  • TinyMCE3.2 (using "Path" feature)
  • DreamWeaver8 ("Edit>Select Parent Tag", "Edit>Select Child")
  • Amaya? (JS)
A.3.5 (For the authoring tool user interface) Provide text search of the content. A.3.5.1 Text Search: Authors can perform text searches of web content that meet the following:
(a) Search All Editable: Any information that is text and that the authoring tool can modify is searchable, including: text content, text alternatives for non-text content, metadata, markup elements and attributes; and
Note: If the current editing-view is not able to display the results of a search, then the authoring tool may provide a mechanism to switch to a different editing-view to display the results.
(b) Two-way: The search can be made forwards or backwards; and
(c) Case Sensitive: The search can be in both case sensitive and case insensitive modes; and
(d) No Match: Authors are informed when no results are found.		 @Many
  • DreamWeaver8
  • MS2010?
A.3.6: (For the authoring tool user interface) Manage preference settings. A.3.6.2 Save Settings: Authoring tool display settings and control settings can be saved between authoring sessions. @Many
  • Dreamweaver8
  • MS2010
  • XStandard2.1
  A.3.6.3 Apply Platform Settings: The authoring tool applies platform display settings and control settings. @Several
  • TinyMCE3.2 (respects browser display settings)
  • Defacto
  • Dreamweaver (for Mac)? Desire2Learn? SAKAI?
A.4.2 (For the authoring tool user interface) Document the user interface including all accessibility features. A.4.2.2 Document All Features: All features of the authoring tool are documented.
Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.		 @At-least-one
  • Dreamweaver8
  • MS2010?
B.1.1: Ensure automatically specified content is accessible. B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG AA): 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).
Note: 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.		 @At-least-one:
  • Defacto CMS (developer created templates display content listings)
  • ATutorLCMS?
B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG AA): Authors have the default option that, when web content is automatically generated during an authoring session, then one of the following is true:
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.
(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. 		@At-least-one:
  • TinyMCE3.2
  • Defacto CMS (developer created templates display content listings)
  • ATutorLCMS? Dreamweaver8?
B.1.2: Ensure accessibility information is preserved. B.1.2.1 Restructuring and Recoding Transformations (WCAG AA): If the authoring tool provides restructuring transformations or re-coding transformations, then at least one of the following is true:
Note: This success criteria only applies to transformations in which the output technology is an "included" technology for conformance.
(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, the authoring tool prompts authors to perform accessibility checking. 		@None-confirmed
  • @@examples needed - Jan (in general), Greg (New dreamweaver html5 extension, Adobe Encore?)
  • @@video converters?
Guideline B.2.1: Ensure accessible content production is possible. B.2.1.1 Accessible Content Possible (WCAG AA): If the authoring tool places restrictions on the web content that authors can specify, then those restrictions do not prevent WCAG 2.0 success criteria from being met @Many
  • XStandard2.1
  • TinyMCE3.2
  • DreamWeaver8
  • Defacto CMS (Partly via TinyMCE, partly via templates)
B.2.2: Guide authors to produce accessible content. B.2.2.1 Accessible Option Prominence (WCAG AA): 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. @None-confirmed
B.2.2.2 Setting Accessibility Properties (WCAG AA): If the authoring tool 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):
Note: Success Criterion B.4.1.4 addresses the prominence of the mechanisms.		 @None-confirmed
B.2.3: Assist authors with managing alternative content for non-text content. B.2.3.1 Alternative Content is Editable (WCAG AA): Authors are able to modify programmatically associated text alternatives for non-text content. (Level A).
 @Many
  • TinyMCE3.2
  • Dreamweaver8
  • MS2010
  • XStandard2.1
  • Defacto CMS
B.2.4: Assist authors with accessible templates B.2.4.1 Accessible Template Options (WCAG AA): If the authoring tool provides templates, then there are accessible template options for a range of template uses. @None-confirmed
B.2.4.2 Template Selection Mechanism: If authors are provided with a template selection mechanism, then both of the following are true:
(a) Indicate: The selection mechanism indicates the accessibility status of templates (if known); and
(b) Prominence: Any accessible template options are at least as prominent as other template options.		 @None-confirmed
B.2.4.3 New Templates: If authors can use the authoring tool to create new templates for use by a template selection mechanism, they have the option to record the accessibility status of the new templates. @None-confirmed
B.2.5: Assist authors with accessible pre-authored content. 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:
(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.

@At-least-one

  • Defacto
B.3.1: Assist authors in checking for accessibility problems. B.3.1.1 Checking Assistance (WCAG AA): If the authoring tool 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).
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, the authoring tool 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. 		@Several
  • TinyMCE3.2 (via button launching AChecker (WCAG 2.0 AA option, including "Potential Problems" display))
  • Acrobat Accessibility Checker
  • WAVE
  • MS2010 Document Finisher?
B.3.1.4 Status Report: Authors can receive an accessibility status report based on the results of the accessibility checks.
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. 		@Several
  • TinyMCE3.2 (via button launching AChecker (WCAG 2.0 AA option, including "Potential Problems" display))
  • WAVE
  • Acrobat Accessibility Checker
B.3.1.5 Metadata Production: Authors have the option of associating accessibility checking results with the web content as metadata.
Note: The metadata format that is implemented will dictate the nature of the associated results (e.g. specific check results, summary conformance claims, etc.)		 @At-least-one
  • AChecker (AccessForAll metadata)
  • EARL producing checkers?
B.3.2: Assist authors in repairing accessibility problems. B.3.2.1 Repair Assistance (WCAG AA): 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:
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, the authoring tool 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. 		@Several
  • TinyMCE3.2 (via button launching AChecker (WCAG 2.0 AA option, including "Potential Problems" display))
  • WAVE
  • Acrobat Accessibility Checker
B.4.1: Ensure the availability of features that support the production of accessible content. B.4.1.3 Feature Deactivation Warning: If authors turn off an accessible content support feature, then the authoring tool informs them that this may increase the risk of content accessibility problems. @None-confirmed
  • Acrobat? MS2010? AtutorLCMS?
B.4.1.4 Feature Prominence: Accessible content support features are at least as prominent as comparable features related to other types of web content problems (e.g. invalid markup, syntax errors, spelling and grammar errors). @At-least-one
  • TinyMCE3.2
B.4.2: Ensure that documentation promotes the production of accessible content. B.4.2.1 Model Practice (WCAG AA): A range of examples in the documentation (e.g. markup, screen shots of WYSIWYG editing-views) demonstrate accessible authoring practices that meet the WCAG 2.0 success criteria: @None-confirmed
  • Acrobat?

Level AAA Success Criteria

Guideline Success Criteria Implementations Info
A.1.1 (For the authoring tool user interface) Ensure that web-based functionality is accessible. A.1.1.1 Web-Based Accessible (WCAG AAA): Web-based authoring tool user interfaces meet the WCAG 2.0 success criteria. @None-confirmed
  • TinyMCE3.2?
A.3.1 (For the authoring tool user interface) Provide keyboard access to authoring features. A.3.1.4 Keyboard Access (Enhanced): All functionality of the authoring tool is operable through a keyboard interface without requiring specific timings for individual keystrokes. @Several
  • TinyMCE3.2
  • AtutorCMS
  • Defacto CMS
  • DrupalCMS? Fluid tools (Decapod coversion, Collection space)
A.3.1.5 Customize Keyboard Access: Keyboard access to the authoring tool can be customized. @At-least-one
  • DreamWeaver8
    Screenshot of Dreamweaver MX2004 keyboard shortcut editor.
  • MS2010, Web-based tools customized from browser?
A.3.1.6 Present Keyboard Commands: Authoring tool user interface components can be presented with any associated keyboard commands @Several
  • MS2010
  • DreamWeaver8 (underlines access keys in the menus when "alt" key is pressed)
    Screenshot of Dreamweaver MX2004 keyboard shortcut editor.
A.3.2 (For the authoring tool user interface) Provide authors with enough time. A.3.2.4 Content Edits Saved (Extended): The authoring tool can be set to automatically save all content edits made by authors. @Several
  • Photoshop
  • Google Docs document editor
  • Dreamweaver?
A.3.4 (For the authoring tool user interface) Enhance navigation and editing via content structure. 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 the authoring tool, relationships may include, but are not limited to, element nesting, headings, labeling, programmatic definitions, and ID relationships.

@Several

  • IDE's?
A.3.6 (For the authoring tool user interface) Manage preference settings. A.3.6.4 Multiple Sets: Authors can save and reload multiple sets of any authoring tool display settings and control settings. @Several
  • Dreamweaver8
  • Indesign
A.3.6.5 Assistance with Preferences: The authoring tool includes a mechanism to help authors configure authoring tool display settings and control settings. @Several
  • MS2010
  • Dreamweaver8
A.3.7: (For the authoring tool user interface) Ensure that previews are as accessible as existing user agents. A.3.7.2 Preview (Enhanced): If a preview is provided, then authors can specify which user agent performs the preview.

@Several

  • Dreamweaver8
  • Defacto
A.4.1: (For the authoring tool user interface) Help authors avoid and correct mistakes. A.4.1.3 Content Changes Reversible (Enhanced): Authors can sequentially reverse a series of reversible authoring actions.
Note: The notes for A.4.1.1 still apply.		 @None-confirmed
B.1.1: Ensure automatically specified content is accessible. B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG AAA): 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).
Note: 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.		 @Several
  • TinyMCE3.2
  • Defacto CMS
B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG AAA): Authors have the default option that, when web content is automatically generated during an authoring session, then one of the following is true:
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.
(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. 		@At-least-one
  • TinyMCE3.2
  • Defacto CMS
B.1.2: Ensure accessibility information is preserved. B.1.2.1 Restructuring and Recoding Transformations (WCAG AAA): If the authoring tool provides restructuring transformations or re-coding transformations, then at least one of the following is true:
Note: This success criteria only applies to transformations in which the output technology is an "included" technology for conformance.
(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, the authoring tool prompts authors to perform accessibility checking. 		@None-confirmed
Guideline B.2.1: Ensure accessible content production is possible. B.2.1.1 Accessible Content Possible (WCAG AAA): If the authoring tool places restrictions on the web content that authors can specify, then those restrictions do not prevent WCAG 2.0 success criteria from being met @Many
  • XStandard2.1
  • TinyMCE3.2
  • DreamWeaver8
  • Defacto CMS (Partly via TinyMCE, partly via templates)
B.2.2: Guide authors to produce accessible content. B.2.2.1 Accessible Option Prominence (WCAG AAA): 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. @None-confirmed
  • Opencaps? TinyMCE?
B.2.2.2 Setting Accessibility Properties (WCAG AAA): If the authoring tool 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):
Note: Success Criterion B.4.1.4 addresses the prominence of the mechanisms.		 @None-confirmed
B.2.3: Assist authors with managing alternative content for non-text content. B.2.3.1 Alternative Content is Editable (WCAG AAA): Authors are able to modify programmatically associated text alternatives for non-text content.
 @Many
  • TinyMCE3.2
  • Dreamweaver8
  • MS2010
  • XStandard2.1
  • Defacto CMS
B.2.4: Assist authors with accessible templates B.2.4.1 Accessible Template Options (WCAG AAA): If the authoring tool provides templates, then there are accessible template options for a range of template uses. @None-confirmed
B.2.4.4 Template Accessibility Status: If the authoring tool provides a repository of templates, then each of the templates has a recorded accessibility status. @None-confirmed
  • A-Content (Div. Directorate)? Dreamweaver templates may list some accessible status info? Scholar's portal?
B.2.5: Assist authors with accessible pre-authored content. B.2.5.2 Pre-Authored Content Accessibility Status: If the authoring tool provides a repository of pre-authored content, then each of the content objects has a recorded accessibility status. @None-confirmed
  • A-Content (Div. Directorate)? Dreamweaver templates may list some accessible status info? Scholar's portal?
B.3.1: Assist authors in checking for accessibility problems. B.3.1.1 Checking Assistance (WCAG AAA): If the authoring tool 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).
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, the authoring tool 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. 		@At-least-one
  • TinyMCE3.2 (via button launching AChecker (WCAG 2.0 AAA option, including "Potential Problems" display))
  • WebAIM WAVE? Deeque? HiSoftware? CommonLook?
B.3.2: Assist authors in repairing accessibility problems. B.3.2.1 Repair Assistance (WCAG AAA): 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: [Implementing B.3.2.1]
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, the authoring tool 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. 		@At-least-one
  • TinyMCE3.2 (via button launching AChecker (WCAG 2.0 AAA option, including "Potential Problems" display))
  • WebAIM WAVE? Deeque? HiSoftware? CommonLook?
B.4.2: Ensure that documentation promotes the production of accessible content. B.4.2.1 Model Practice (WCAG AAA): A range of examples in the documentation (e.g. markup, screen shots of WYSIWYG editing-views) demonstrate accessible authoring practices that meet the WCAG 2.0 success criteria: @None-confirmed
  • OpenCaps, Atutor
B.4.2.3 Tutorial: A tutorial on an accessible authoring process that is specific to the authoring tool is provided. @At-least-one
  • Acrobat (http://www.adobe.com/accessibility/tutorials.html)
  • Atutor
B.4.2.4 Instruction Index: The documentation contains an index to the instructions for using the accessible content support features. @None-confirmed