May be Superseded
This version includes a major revision of Parts A and B. After a review of the entire document at the August Face to Face meeting, the working group reached consensus that major structural changes were necessary. There are a number of places where the group noted that more work was needed and these editorial notes are included in this document.
Part A has been revised to require conformance with WCAG for web technologies and accessibility standards for non-web technologies. At the this time the ISO standard for accessibility is undergoing status changes, so no specific standard for non-web technologies is specified in this version. Items in Part A that are covered by international standards have been removed, while Guidelines and Success Criteria that are unique to Authoring Tools have been maintained.
The major change with Part B has been to remove the requirements for publishing benchmark documents to claim conformance. Since many success criteria in Part B were structured to refer to these benchmark documents, these guidelines and criteria have been edited to remove those references. In most cases, they now refer to the WCAG.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
Web Accessibility Initiative
This document has been produced as part of the W3C Web
Accessibility Initiative (WAI). The goals of the AUWG are discussed
in the Working Group charter.
The AUWG is part of the WAI
Technical Activity.
No Endorsement
Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
Patents
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This section is informative, except where
noted.
This is a Working Draft of the Authoring Tool Accessibility Guidelines (ATAG) version
2.0. This document includes recommendations for assisting developers to make their authoring tools more accessible to a wide range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech difficulties, and others. However, even authoring tools that conform to ATAG 2.0 may not be able to address the needs of people with all types, degrees and combinations of disabilities.
In order to achieve accessibility, authoring tools must address the needs of two (potentially overlapping) user groups:
- authors of Web content, whose needs are met by ensuring the authoring
tool user interface itself is accessible (see Part
A of the guidelines), and
- end
users of Web content, whose needs are met by ensuring that all authors are enabled, supported, and guided towards producing accessible
Web content, with the assumption that many authors will not be familiar with the specific needs of end users with disabilities (see Part B of the guidelines).
The guidelines do not include standard usability recommendations except where they have a significantly greater impact on people
with disabilities than on other people.
Note that even content that conforms at the highest level (AAA) will not be accessible to individuals with all types, degrees, or combinations of disability, particularly in the cognitive language and learning areas. Creation of authoring tools that address the specialized needs of these communities for is encouraged, but is outside the scope of this document.
These guidelines have been written to address the requirements
of many different audiences, including, but not limited to:
- Web content authoring tool developers,
- Web content authoring tool users (authors),
- Web content authoring tool purchasers, and
- policy makers.
ATAG 2.0 defines an "authoring tool" as any application, part of an application, or collection of applications that authors interact with to create, modify or assemble Web content to be used by other people.
The definition applies to all or part of the following types of applications:
- WYSIWYG editors, plain text editors (embedded and stand-alone)
- conversion tools, software that can output Web content technologies (e.g., "Save as HTML")
- blogging tools, wikis, online forums, emailers that produce Web-content
- multimedia authoring tools
- scripting tools, widget development environment
- content management systems, courseware tools, content aggregators
- site management tools
- etc.
Notes on the Definition:
- Any guidelines that require the ability of authors to modify content in some way always assume that the person has author permission.
- Synchronous tools (e.g., chats, collaboration tools, whiteboards, etc.), especially those that archive as Web content, are considered authoring tools and can be made more accessible for both participants and users of the stored archives. While not all parts of ATAG 2.0 will usefully apply, some discussion is provided in ATAG 2.0 Techniques Appendix E: Real-time content production.
===========================
For example, in a CMS system managing a portal, the widget that selects the RSS feed would be covered by ATAG, but the data coming in on the RSS feed would not apply. In a large document management system, the components that allowed entry or selection of alternative formats would apply, but the components that displayed dynamic content where there is no editorial control, would not apply.
However, the definition excludes cases in which:
- the authoring tool lacks authoring functionality...
- authors lack permission to edit content
- authors lack knowledge about future changes to content (e.g., media files to be submitted by end users, aggregated news feeds, etc.)
For example, ATAG does not apply to a component that imports documents into a document share system, or a portal that aggregates RSS feeds. ATAG does apply to the portal management widget that selects the RSS.
assemble?
These guidelines apply to the functions in which authoring choices the authoring tool presents to the author or makes on behalf of the author.
This definition can cover components such as :
- IN
- Typing text
- Authoring choice
- Creating templates
- Setting stylesheets
- Create controls
- OUT
- Pulling in stuff that is out of control
- JT:
- Interact with human author
- Choices under control of tool
Components of Web Accessibility
Authoring tools are just one aspect of accessibility. For an overview of the different components of accessibility and how they work together see:
Organization of the ATAG 2.0 Document
Two Parts
ATAG 2.0 is divided into two parts, each reflecting a key aspect
of accessible authoring tools. Part A includes
principles and associated guidelines that are related to ensuring accessibility
of the authoring
tool user interface to authors with disabilities. Part B contains
principles and guidelines related to ensuring support by authoring tools for the creation of accessible
Web content by any author (not just those with disabilities) to end
users with disabilities.
Part A: Make the authoring tool user interface accessible
The guidelines and success criteria in Part A are organized around the following four principles, adapted from the four principles in WCAG 2.0:
- Authoring tool must facilitate access by assistive technology - Assistive technologies can only provide augmented display and control to their
users if the relevant information is made available by authoring tools using common protocols.
- Authoring tool must be perceivable - Authors with a wide range of abilities must be able to perceive its user interface components.
- Authoring tool must be operable - Authors with a wide range of abilities must be able to operate its user interface components.
- Authoring tool must be understandable - Authors with a wide range of abilities must be able to understand the user interface components that they can perceive and operate.
Part B: Support the production of accessible content
There are three principles in Part B:
- Production
of accessible content must be enabled - The creation of accessible content is dependent on the combined actions of the
authoring tool and the author. This guideline specifies the responsibilities that
rest exclusively with the tool.
- Authors must be supported
in the production of accessible content - Actions may be taken at the author's initiative that may result in accessibility
problems. The authoring tool should include features that provide
support and guidance to authors in
these situations, so that accessible
authoring practices can be followed and accessible
web content can be produced.
- Accessibility
solutions must be promoted and integrated -Authoring tools should encourage the discovery of tools, features, or functionality which support accessible authoring practices, while at the same time, integrating functions related to accessibility in order to ensure that authors make them common practice.
Note: While the requirements in Part B do not
deal with the accessibility of the authoring tool user interface per se, it should
be noted that any of the features (e.g., checker, tutorial) added to an authoring tool to meet
the Part B success criteria must also meet the user interface accessibility requirements of Part
A.
Success Criteria
Under each guideline there are success criteria that describe specifically what must be achieved in order to conform. They are similar to the "checkpoints" in ATAG 1.0. Each success criterion is written as a statement that will be either true or false when a specific authoring tool is tested against it. While all of the ATAG 2.0 success criteria are written to be testable and some test automation may be possible, human testing will usually be required. In order to meet the needs of different groups and different situations, three levels of conformance are defined: A (lowest), AA, and AAA (highest).
Each of the success criteria has a link to the Techniques document that provides:
- "Sufficient" techniques for meeting the success criteria, and @@define@@
- optional "Advisory" techniques.@@define@@
Note: Any success criteria that are judged not applicable
to a particular authoring tool are treated as satisfied for
conformance purposes, as long as a rationale is provided.
Levels of Conformance
Authoring tools may claim full conformance
to ATAG 2.0 at one of three "full" conformance levels. The level achieved depends
on the level of the success
criteria that have been satisfied. The full conformance
levels are:
- Full ATAG 2.0 Conformance at Level "A"
The authoring tool satisfies all of
the Level A success criteria.
- Full ATAG 2.0 Conformance at Level "Double-A"
The authoring tool satisfies all of
the Level A and Level
AA success criteria.
- Full ATAG 2.0 Conformance at Level "Triple-A"
The authoring tool satisfies all of
the success criteria.
@@Maybe remove partial@@
In addition, a "partial conformance" claim option is available
in cases where an authoring tool has satisfied all of the success criteria
at a specified level in one of the two Parts of the document (i.e., "Part
A: Make the authoring tool user interface accessible" and "Part
B: Support the production of accessible content"). The partial
conformance levels are:
- Partial ATAG 2.0 Conformance Level "A":
Authoring Tool User Interface
The authoring tool satisfies all of the Level
A success criteria in Part A. Nothing is claimed about Part B.
- Partial ATAG 2.0 Conformance Level "Double-A":
Authoring Tool User Interface
The authoring tool satisfies all of the Level
A and Level AA success criteria in Part A. Nothing
is claimed about Part B.
- Partial ATAG 2.0 Conformance Level "Triple-A":
Authoring Tool User Interface
The authoring tool satisfies all of the success criteria
in Part A. Nothing is claimed about Part B.
- Partial ATAG 2.0 Conformance Level "A":
Content Production"
The authoring tool satisfies all of the Level
A success criteria in Part B. Nothing is claimed about Part A.
- Partial ATAG 2.0 Conformance Level "Double-A":
Content Production"
The authoring tool satisfies all of the Level
A and Level AA success criteria in Part B. Nothing
is claimed about Part A.
- Partial ATAG 2.0 Conformance Level "Triple-A":
Content Production"
The authoring tool satisfies all of the success criteria
in Part B. Nothing is claimed about Part A.
Note: The Working Group remains committed
to the guiding principle that: "Everyone should
have the ability to create and access Web content". Therefore, it is
recommended that partial conformance be claimed as a step towards full conformance.
Relationship
to the Web Content Accessibility Guidelines (WCAG) @@rephrase@@
The ATAG 2.0 conformance relies upon
Web Content Accessibility "Benchmark" documents to precisely specify what an evaluator interprets "accessible
Web content" to mean for the particular Web content technologies that an authoring tool produces and, in the case of Web-based tools, is implemented using.
The primary recommended reference for the Web Content Accessibility "Benchmark" is a version of the
W3C Web Content Accessibility Guidelines (WCAG), due to the
quality of the documents and the process under which they were developed
(See Note on other Accessibility Standards). At the time of publication,
version 1.0 of WCAG is a W3C Recommendation [WCAG10],
and version 2.0 is a W3C Candidate Recommendation [WCAG20].
Although a Web Content Accessibility "Benchmark" document may use either version of WCAG, developers should give consideration to the following:
- The latest version of WCAG will be the most accurate with respect to
state-of-the-art technologies and accessibility best practices. Older versions
of WCAG may include requirements that are no longer necessary, due to advances
in user agent technology.
- The versions of WCAG differ with respect to the technologies for which there are published WCAG technique documents. This is important
because the techniques documents may be useful when constructing Web Content Accessibility "Benchmark" documents as required by ATAG 2.0.
- The versions of WCAG differ in the degree to which they match the legislation
and policies that drive author requirements. Many authors will be seeking
to use authoring tools to create Web content that meets legislation, corporate
policies, etc. It is likely that as WCAG progresses, so too will legislation
and policies, albeit at an uneven pace. Authoring tool developers may,
therefore, consider supporting both versions of WCAG in
the interim.
ATAG 2.0 Guidelines
The success criteria and applicability notes in this section are normative.
PART A:
Make the authoring tool user interface accessible
Applicability Notes:
Developer Responsibility: The success criteria in Part A apply to all apects of the authoring tool user interface that are under the control of the developer. This includes naturally includes functionalities that are independent of the content being edited, such as what is sometimes referred to as the authoring tool's "chrome" (e.g., menus, button bars, status bars, etc.) and also user preferences and documentation, etc. In addition, the developers' responsibility covers certain aspects of other functionalities that reflect the content being edited (e.g., ensuring that an image label present in the content is available programmatically). However, where an accessibility problem in the user interface is caused directly by an accessibility problem in the content it is reflecting (e.g., if an image in the content lacks a label), then this would not be considered a deficiency in the accessibility of the authoring tool user interface.
PRINCIPLE
A.1: Authoring tool user interfaces must follow applicable accessibility guidelines
Guideline A.1.1
[For the authoring tool user interface] Ensure that Web-based
functionality is accessible.
[Techniques]
Rationale: In
addition to generally improving the accessibility of the authoring
tool user interface, implementing Web-based functionality (e.g., editing views, documentation) using accessible Web content facilitates communication with assistive
technologies via user agents.
Applicability Notes:
Level A Success Criteria for Guideline A.1.1
Level AA Success Criteria for Guideline A.1.1
- A.1.1.2 Web-Based "AA" Accessible: Web-based authoring tool user
interfaces meet WCAG Level "AA".
Level AAA Success Criteria for Guideline A.1.1
- A.1.1.3 Web-Based "AAA" Accessible: Web-based authoring tool user
interfaces meet WCAG Level "AAA".
Guideline A.1.2
[For the authoring tool user interface] Ensure that non-Web-based functionality is accessible. [Techniques]
Rationale: Following existing accessibility standards and/or platform conventions will facilitate access by all authors, including those using assistive technologies.
Applicability Notes:
Level A Success Criteria for Guideline A.1.2
- A.1.2.1 Non-Web-Based Accessible (Level A): Non-Web-based authoring tool user interfaces follow the "Level A" requirements of standards and/or platform conventions that benefit accessibility. The "Level A" are those that are functionally equivalent to WCAG Level A success criteria.
Level AA Success Criteria for Guideline A.1.2
- A.1.2.2 Non-Web-Based Accessible (Level AA): Non-Web-based authoring tool user interfaces follow the "Level AA" requirements of standards and/or platform conventions that benefit accessibility. The "Level AA" are those that are functionally equivalent to WCAG Level AA success criteria.
Level AAA Success Criteria for Guideline A.1.2
- A.1.2.3 Non-Web-Based Accessible (Level AAA): Non-Web-based authoring tool user interfaces follow the "Level AAA" requirements of standards and/or platform conventions that benefit accessibility. The "Level AAA" are those that are functionally equivalent to WCAG Level AAA success criteria.
PRINCIPLE
A.2: Editing views must be perceivable
Guideline A.2.1
[For the authoring tool user interface] Provide access to alternative equivalents in the content.
[Techniques]
Rationale: People
who have difficulty perceiving non-text objects are often able to
access text alternatives of the same information because there are a variety of ways to display text (e.g., magnification, enhancement, text-to-speech, Braille output)
Applicability Notes:
- Rendering requirements do not apply to plain text editors.
Level A Success Criteria for Guideline A.2.1
Level AA Success Criteria for Guideline A.2.1
- (No level AA success criteria for Guideline A.2.1)
Level AAA Success Criteria for Guideline A.2.1
- (No level AAA success criteria for Guideline A.2.1)
Guideline A.2.2
[For the authoring tool user interface] Ensure that the interface can be presented in different ways.
[Techniques]
Rationale: Authors need to have access to and control over both the functional significance of presentation and also, in the context of authoring, the presentation that will be experienced by the end user. This is especially important for user interface components that do not implement an accessibility platform architecture or leverage existing implementations (e.g. custom user interface components built via JavaScript and CSS). Some authors require display settings that differ from the presentation that they intend to define for the published content (e.g., using a high contrast setting during editing content that is not intended to be high contrast).
Level A Success Criteria for Guideline A.2.2
- A.2.2.1 Independence of Display: Editing
views that usually have their display characteristics set
by rendering the content being
edited (e.g., WYSIWYG editing views) allows the authors' visual and audio display settings to override these characteristics without
affecting the content (e.g.,
markup, stylesheets, etc.) being edited.
- A.2.2.2 Purpose of Added Presentation: If the authoring tool modifies the presentation of the content being edited, then the functional purpose for the modification is made available via the platform (e.g., if misspelled text is underlined, the fact that it is misspelled is made available).
- A.2.2.3 Access to Text Presentation (Minimum): If an editing view (e.g., WYSIWYG) renders any of the following text presentation properties and those properties are editable by any editing view (e.g., instruction level), then the properties are made available via the platform:
- (a) font,
- (b) style (e.g., italic, bold),
- (c) color, and
- (d) size.
Level AA Success Criteria for Guideline A.2.2
- (No level AA success criteria for Guideline A.2.2)
Level AAA Success Criteria for Guideline A.2.2
- A.2.2.4 Access to Text Presentation (Enhanced): Any text presentation properties (text size, positioning, etc.) that are rendered in an editing view (e.g., WYSIWYG editing views ) and are editable by any editing view are available via the platform.
PRINCIPLE
A.3: Editing views must be operable
Guideline A.3.1
[For the authoring tool user interface] Enhance keyboard access to authoring features. [Techniques]
Rationale: Providing alternate keyboard accessibility provides access for people with limited mobility and people with
visual disabilities, who cannot rely on hand-eye coordination for
navigating the user interface.
@@AUWG is watching the keyboard control developments in UAAG 2.0@@
Applicability Notes:
Level A Success Criteria for Guideline A.3.1
- A.3.1.1 Accelerator Keys: If the authoring tool includes any of the following functions, authors can enable
key-plus-modifier-key (or single-key) access to them (where allowed by the operating environment):
- (a) open help system,
- (b) open new content,
- (c) open existing content,
- (d) save content,
- (e) close content,
- (f) cut/copy/paste,
- (g) undo/redo, and
- (h) open find/replace function.
- A.3.1.2 Available Keystrokes: Authors can always determine the currently available
keystrokes (e.g., from a central location such as a list in the
help system or a distributed location such as associating shortcuts
with menu items). [UAAG 2.0]
- A.3.1.3 Standard Text Area Conventions: Editing
views that allow text entry support the standard text area conventions for
the platform including, but not necessarily limited to:
character keys, backspace/delete, insert, "arrow" key
navigation, page up/page down, navigate to start/end, navigate
by paragraph, shift-to-select mechanism, etc.
Level AA Success Criteria for Guideline A.3.1
- (No level AA success criteria for Guideline A.3.1)
Level AAA Success Criteria for Guideline A.3.1
- (No level AAA success criteria for Guideline A.3.1)
Guideline A.3.2
[For the authoring tool user interface] Enable time-independent interaction.
[Techniques]
Rationale: People
who have difficulty typing, operating the mouse, or processing information
can be prevented from using systems with short time limits.
Applicability Note: Several of the success criteria in this guideline only apply when there are time limits put on the author, which is currently not very common for authoring tools.
Level A Success Criteria for Guideline A.3.2
- A.3.2.1 Data Saved: If the authoring tool ends an authoring session due to a time limit (e.g., authenticated session expires), then the authors have the "pre-settable" option to save the content being edited. For Web-Based Authoring Tools, this applies to any content that has already been submitted to the application by the user agent.
- A.3.2.2 Timing Adjustable: If the authoring tool is responsible for imposing a time limit on authoring sessions (e.g., to mediate collaborative
authoring), then authors can extend the time limit.
- A.3.2.3 Moving Targets: If the user interface includes any targets for authors' actions (e.g., are clickable, accept drag-and-drop actions) that are capable of movement, then authors can stop that movement.
Level AA Success Criteria for Guideline A.3.2
- (No level AA success criteria for Guideline A.3.2)
Level AAA Success Criteria for Guideline A.3.2
- A.3.2.4 No Time Limits: Authors have the option to remove time limits on authoring sessions.
Guideline A.3.3
[For the authoring tool user interface] Help authors avoid flashing that could cause seizures. [Techniques]
Rationale: Flashing
can cause seizures in people with photosensitive epilepsy.
Level A Success Criteria for Guideline A.3.3
- A.3.3.2 Blinking Request: If an editing
view renders content such that the authoring tool recognizes it as blinking or flashing (e.g.
blink
element), then the author has the option to turn off this blinking or flashing.
Level AA Success Criteria for Guideline A.3.3
- (No level AA success criteria for Guideline A.3.3)
Level AAA Success Criteria for Guideline A.3.3
- (No level AAA success criteria for Guideline A.3.3)
Guideline A.3.4
[For the authoring tool user interface] Enhance navigation and editing via content structure. [Techniques]
Rationale: People
who have difficulty typing or operating the mouse benefit when the structure that may be inherent
in certain content can be used to navigate more efficiently within editing views and to perform
edits.
Level A Success Criteria for Guideline A.3.4
Level AA Success Criteria for Guideline A.3.4
- A.3.4.2 Navigate By Element Type: If an editing
view displays a structured
element set, authors can move the editing focus forward/backward to the next identical or heading element.
- A.3.4.3 Navigate Tree Structures: If an editing
view displays a structured
element set, authors can, with a simple action, move
the editing focus from any element to
other elements in the set with any of the following
relationships (if they exist):
- (a) Parent: the element immediately
above,
- (b) Child: the first element immediately
below,
- (c) Previous Sibling: the element immediately
preceding at the same level, and
- (d) Next Sibling: the element immediately
following at the same level.
Level AAA Success Criteria for Guideline A.3.4
- (No level AAA success criteria for Guideline A.3.4)
Guideline
A.3.5 [For the authoring tool user interface] Provide
text search. [Techniques]
Rationale: People
who have difficulty typing or operating the mouse benefit from the ability to navigation to arbitrary points within editing views.
Applicability Notes:
Level A Success Criteria for Guideline A.3.5
- (No level A success criteria for Guideline A.3.5)
Level AA Success Criteria for Guideline A.3.5
- A.3.5.1 Text Search: A function is provided that allows text search of the content, which meets the following conditions:
- (a) Search All Editable: can search any textual information (including
text content, text
alternatives for non-text
objects, metadata, markup) that is editable using the authoring tool.
- (b) Bi-Directional: can search backwards and forwards. [UAAG 2.0]
- (c) Case Sensitive: can search in both case sensitive and case insensitive modes. [UAAG 2.0]
- (d) May Switch Views: permissible for the authoring tool to switch editing views to display the search results (e.g.,
from WYSIWYG to instruction level in order to display markup).
Level AAA Success Criteria for Guideline A.3.5
- (No level AAA success criteria for Guideline A.3.5)
Guideline A.3.6
[For the authoring tool user interface] Manage preference settings. [Techniques]
Rationale: Providing
the ability to save and reload sets of keyboard and display preference
settings benefits people using multi-user tools as well as people who have needs that differ over time (e.g., due to fatigue).
Level A Success Criteria for Guideline A.3.6
- (No level A success criteria for Guideline A.3.6)
Level AA Success Criteria for Guideline A.3.6
- A.3.6.1 Save Settings: Preference settings are stored for any of the following that the authoring tool controls
(i.e., not controlled by the platform):
Level AAA Success Criteria for Guideline A.3.6
- A.3.6.2 Multiple Sets: Choosing between multiple sets of preferences (e.g., personal profiles,
personal settings) are supported for any of the following that the authoring tool controls (i.e., not controlled by the platform):
- A.3.6.3 Options Wizard: Authors are provided with an accessibility option-setting "wizard" to configure options related to Part A.
Guideline A.3.7
[For the authoring tool user interface] Ensure that previews are
as accessible as existing user
agents. [Techniques]
Rationale: Preview features
are provided in many authoring tools because the workflow of authors often includes periodically checking how content will appear
to end users in
a user
agent. Authors with disabilities need to be able to follow
the same workflow.
Note: Previews are treated differently than editing views because authors, including those with disabilities, will not be well-served if preview features diverge too much from the actual functionality of available user agents. Therefore, preview features are exempted from necessarily having to meet all of the other requirements in Part A of this guidelines document, if they meet this guideline.
Level A Success Criteria for Guideline A.3.7
- A.3.7.1 Return Mechanism: If a preview is
provided, then a keyboard accessible mechanism for returning
from the preview (i.e., moving focus back from, exiting from) is provided and
is documented in the help system.
- A.3.7.2 Preview: If a preview is provided, then it meets at least one of the following:
- (a) Existing User Agent: the preview makes
use of an existing user
agent that is specified in the conformance
profile (e.g., opening the
content in a third-party browser or browser component),
- (b) Part A.1: the preview meets
all of the Level A guidelines in Principle A.1 of these guidelines, or
- (c) UAAG: the preview conforms
to the User Agent Accessibility Guidelines [UAAG].
Level AA Success Criteria for Guideline A.3.7
- (No level AA success criteria for Guideline A.3.7)
Level AAA Success Criteria for Guideline A.3.7
- (No level AAA success criteria for Guideline A.3.7)
PRINCIPLE
A.4: Editing views must be understandable
Guideline A.4.1 [For the
authoring tool user interface] Help users avoid and correct mistakes.
[Techniques]
Rationale: People who have difficulty making fine movements may be prone to making
unintended actions.
Applicability Notes:
Level A Success Criteria for Guideline A.4.1
- A.4.1.1 Undo Content Changes: Authoring actions are either reversible by an "undo" function or include a warning
to authors that the action is irreversible. The authoring
tool may have certain committing actions (e.g., "save" function)
that reset the undo history.
- A.4.1.2 Undo Setting Changes: Actions
that modify authoring tool settings are either reversible or include a warning
to the author that the setting modification is irreversible.
Level AA Success Criteria for Guideline A.4.1
- A.4.1.5 Redo: Authors can immediately reverse the most recent content "undo(s)" (i.e., a "redo" function).
Level AAA Success Criteria for Guideline A.4.1
- A.4.1.7 Multiple Undos: Authors can reverse
at least 5 consecutive reversible authoring actions.
Guideline A.4.2
[For the authoring tool user interface] Document the user interface
including all accessibility features.
[Techniques]
Rationale: While
intuitive user interface design is valuable to many authors, some
people may still not be able to understand or be able to operate
the authoring tool user interface without proper documentation.
Applicability Notes:
Level A Success Criteria for Guideline A.4.2
- A.4.2.1 Document Accessibility Features: All features (other than documentation) that are specifically required
to meet Part
A of these guidelines (e.g.
keyboard shortcuts, text search, etc.) are documented.
Level AA Success Criteria for Guideline A.4.2
- (No level AA success criteria for Guideline A.4.2)
Level AAA Success Criteria for Guideline A.4.2
- (No level AAA success criteria for Guideline A.4.2)
PART
B: Support the production of accessible content
Applicability Notes:
- Authors Available: Guideline in Part B refering to authors only apply during authoring sessions when authors are available (e.g., not to the specifics of a third-party "feed", etc.).
- Existing Technologies: Part B only requires support for accessible authoring practices that are relevant to technologies that the authoring tool already has the ability to create or edit. For example, a markup authoring tool that adds images by simply linking to their URIs would be required to support the production of alternative text for images in the markup, but it would not be required to add image editing functionality to ensure sufficient contrast in case image was of text.
- Authoring Systems: As per the definition of authoring tool, several software tools can be used in conjunction to meet the requirements of Part B. (e.g. a authoring tool could make use of a 3rd party software accessibility checking and repair program.
PRINCIPLE
B.1: Production of accessible content must be enabled
Guideline B.1.1 Support Web content technologies that enable the creation of content that is accessible.
[Techniques]
Rationale: Choosing technologies which support the possibility of accessible authoring is the first step in ensuring that the content produced is accessible.
Level A Success Criteria for Guideline B.1.1
- B.1.1.1 Tool Choice of Technologies (Level A): Any Web content technologies that is automatically selected by the authoring tool can conform to WCAG Level A.
- B.1.1.2 Author Choice of Technologies (Level A): If the authoring tool provides authors with Web content technology options, technology options that can conform to WCAG Level A are listed with at least as much prominence as any other options and the tool guides the author towards the most accessible technology for the task.
Level AA Success Criteria for Guideline B.1.1
- B.1.1.3 Tool Choice of Technologies (Level AA): Any Web content technologies that is automatically selected by the authoring tool can conform to WCAG Level AA.
- B.1.1.4 Author Choice of Technologies (Level AA): If the authoring tool provides authors with Web content technology options, technology options that can conform to WCAG Level AA are listed with at least as much prominence as any other options and the tool guides the author towards the most accessible technology for the task.
Level AAA Success Criteria for Guideline B.1.1
- B.1.1.5 Tool Choice of Technologies (Level AAA): Any Web content technologies that is automatically selected by the authoring tool can conform to WCAG Level AAA.
- B.1.1.6 Author Choice of Technologies (Level AAA): If the authoring tool provides authors with Web content technology options, technology options that can conform to WCAG Level AAA are listed with at least as much prominence as any other options and the tool guides the author towards the most accessible technology for the task.
Guideline B.1.2
Ensure that the authoring tool preserves accessibility
information.
[Techniques]
Rationale: Accessibility
information is critical to maintaining comparable levels of accessibility
across transformations and conversions.
Applicability Notes:
- If an authoring tool performs transformations or conversions after an authoring session ends (e.g., a batch maintenance process) only option (a) is allowed for both B.1.2.1 and B.1.2.3.
Level A Success Criteria for Guideline B.1.2
- B.1.2.1 Accessibility Information Preservation (Minimum): If the authoring tool performs transformations or conversions on existing Web content,
then for any accessibility
information that is required for that content to conform to WCAG Level A at least one of the following is true:
- (a) Preserve in Output: the accessibility
information is preserved and available for end
users in the resulting content;
- (b) Preserve Input and Notify: a copy of the accessibility
information is retained (e.g., as a "comment", by saving a backup
copy) and the authors are notified of the location and of the fact that it will not be available to end users; or
- (c) Author Queried: the authors are queried for an action for each piece of accessibility information that will not be preserved and is notified that this may result in accessibility problems.
Level AA Success Criteria for Guideline B.1.2
- B.1.2.2 Accessibility Information Preservation (Enhanced): If the authoring tool performs transformations or conversions during an authoring session,
then any accessibility
information in the pre-transformation/conversion content that is required for content to conform to WCAG Level AA or AAA is preserved and available for end
users in the resulting content;
- B.1.2.3 Notification Prior to Deletion: If the authoring tool automatically deletes any author-generated content for any reason, then at least one of the following is true:
- (a) Preserve Accessibility Information: the authoring tool only automatically deletes content that it can detect is not accessibility
information;
- (b) Notification Option: authors have the option to receive notification before deletion; or
- (c) No Deletion Option: authors have the option to turn off the automatic deletion.
Level AAA Success Criteria for Guideline B.1.2
- (No level AAA success criteria for Guideline B.1.2)
Guideline B.1.3
Ensure that automatically generated content is accessible.
[Techniques]
Rationale: Authoring
tools that automatically generate content that is not accessible impose additional repair tasks on authors.
Related: If accessibility
information is required from authors during
the automatic generation process, see Guideline
B.2.1. If templates or other pre-authored content are involved, see Guideline B.2.5.
Applicability Notes:
- This guideline applies to the automated behavior specified by the authoring tool developer under the assumption that authors will respond properly to any prompts.
- The guideline does not apply when actions of the authors prevent generation of accessible content (e.g., by setting less strict preferences, ignoring prompts for accessibility information, providing faulty information, writing their own automated scripts, etc.).
Level A Success Criteria for Guideline B.1.3
- B.1.3.1 Automatic "A" Accessible: If the authoring tool automatically
generates content, then that content meets WCAG Level A at the conclusion of the automatic generation process (e.g., when inserted into the existing content).
Level AA Success Criteria for Guideline B.1.3
- B.1.3.2 Automatic "AA" Accessible: If the authoring tool automatically
generates content, then that content meets WCAG Level AA at the conclusion of the automatic generation process.
Level AAA Success Criteria for Guideline B.1.3
- B.1.3.3 Automatic "AAA" Accessible: If the authoring tool automatically
generates content, then that content meets WCAG Level AAA at the conclusion of the automatic generation process.
PRINCIPLE B.2:
Authors must be supported in the production of
accessible content
Applicability Notes:
-
Principle B.2 applies to authoring tool processes that interact with human authors, and the authoring choices that author is making or the authoring choices under the control of the authoring tool. Authoring choices include choice of style sheets, templates, scripts, etc
Guideline B.2.1 Guide authors to
create accessible content.
[Techniques]
Rationale: By guiding authors from the outset towards the creation and maintenance of accessible content, accessibility problems are mitigated and less repair and retrofit effort is required.
Level A Success Criteria for Guideline B.2.1
- B.2.1.1 Guide "A" Accessible: If authors are asked for any information as content is being added or updated (e.g., by an image modification dialog), then the tool also prominently asks for any accessibility
information required for that content to meet WCAG Level A.
- B.2.1.2 Warn "A" Accessible: If an authoring action or instruction will always lead to the creation
of content that cannot be made to meet WCAG Level A other than by making an alternative version, then
a warning is displayed.
Level AA Success Criteria for Guideline B.2.1
- B.2.1.3 Guide "AA" Accessible: If authors are asked for any information as content is being added or updated, then the tool also prominently asks for accessibility information required for that content to meet WCAG Level AA.
- B.2.1.4 Warn "AA" Accessible: If an authoring action or instruction will always lead to the creation
of content that cannot be made to meet WCAG Level AA other than by making an alternative version, then
a warning is displayed.
Level AAA Success Criteria for Guideline B.2.1
- B.2.1.5 Guide "AAA" Accessible: If authors are asked for any information as content is being added or updated, then the tool also prominently asks for accessibility information required for that content to meet WCAG Level AAA.
- B.2.1.6 Warn "AAA" Accessible: If an authoring action or
instruction will always lead to the creation of content that cannot be made to meet WCAG Level AAA other than by making an alternative version, then
a warning is displayed.
Guideline B.2.2 Assist authors in checking for accessibility problems.
[Techniques]
Rationale: Checking as an integrated function of the authoring tool helps make authors aware of accessibility problems during the authoring process, so they can be immediately addressed.
Applicability Notes:
- While automated
checking or more advanced implementations of semi-automated
checking may improve the authoring experience, manual checking is the minimum requirement to meet the success criteria for this guideline.
- This guideline does not apply if the authoring tool controls the authoring process to such an extent that it is not possible for authors to introduce accessibility problems.
- This guideline does not apply to content that is not available at publishing (e.g., the actual content of third-party "feeds").
Level A Success Criteria for Guideline B.2.2
- B.2.2.1 Check Accessibility (Level A): At least one individual check is associated with each WCAG Level A Success Criterion that the tool has the functionality to modify (e.g., a tool that inserts images should check for alt text; a tool that can edit captions should check for them).
- B.2.2.2 Availability: Checking is available prior
to publishing in a manner appropriate to the workflow of the authoring tool.
- B.2.2.2 Identify Range: The appropriate range (e.g., element, group of elements, entire file, site, Web application, etc.) for each potential accessibility
problem is identified.
- B.2.2.4 Help Authors Decide: For any checks that require author judgment to determine whether
a potential accessibility
problem is correctly identified (i.e., manual checking and semi-automated checking), instructions are provided
to help authors to
decide.
Level AA Success Criteria for Guideline B.2.2
- B.2.2.5 Check Accessibility (Level AA): At least one individual check is associated with each WCAG Level AA Success Criterion that the tool has the functionality to modify.
- B.2.2.6 View Status: If the authoring tool records accessibility problems
found during checking, then a list of any accessibility problems is available to authors prior to the end of the authoring session.
- B.2.2.7 Save Status for Repair: If repair assistance is not provided during checking , authors have the option to save the list to facilitate interoperability between checking and repair.
- B.2.2.8 Metadata for Discovery: If the authoring tool records accessibility status, then authors have the option to associate this status with the content as metadata to facilitate resource discovery by end users.
Level AAA Success Criteria for Guideline B.2.2
- B.2.2.9 Check Accessibility (Level AAA): At least one individual check is associated with each WCAG Level AAA Success Criterion that the tool has the functionality to modify.
Guideline B.2.3
Assist authors in repairing accessibility problems.
[Techniques]
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.
Appliciability Notes:
- While automated
repairing or more advanced implementations of semi-automated
repairing may improve the authoring experience, only manual repairing is the minimum requirement to meet the success criteria for this guideline.
- This guideline does not apply if the authoring
tool controls the authoring process to an extent that it
is not possible for authors to introduce accessibility problems
Level A Success Criteria for Guideline B.2.3
Level AA Success Criteria for Guideline B.2.3
- B.2.3.2 Repair Accessibility (AA): For each WCAG Level AA accessibility
problem that is identifiable during checking, repair assistance is provided.
Level AAA Success Criteria for Guideline B.2.3
- B.2.3.3 Repair Accessibility (AAA): For each WCAG Level AAA accessibility
problem that is identifiable during checking, repair assistance is provided.
Guideline
B.2.4 Assist authors to manage, edit, and reuse equivalent alternatives for non-text objects.
[Techniques]
Rationale: Improperly
generated equivalent alternatives can create accessibility problems
and interfere with accessibility checking.
@@http://lists.w3.org/Archives/Public/w3c-wai-au/2008JulSep/0083.html@@
Level A Success Criteria for Guideline B.2.4
Level AA Success Criteria for Guideline B.2.4
- B.2.4.3 Acceptable Sources: Authoring tools only supply equivalent alternatives from the following sources:
- (a) Author-Entered: equivalent
alternatives previously entered by authors for
the same non-text
object (e.g., by the same author, or another author on
a collaborative system),
- (b) From Object Database: equivalent
alternatives stored with the non-text
object in an object database (or equivalent),
- (c) Null when Appropriate: null equivalent
alternatives for non-text
objects that the authoring tool recognizes are only used for pure decoration, or
- (d) Audio, Video, or CART Analysis: automatic video or audio analysis (e.g., speech recognition).
Level AAA Success Criteria for Guideline B.2.4
- B.2.4.4 Save for Reuse: Authors can store, for future reuse, both of the following author-assigned equivalent
alternatives (as applicable):
Note: Equivalent
alternatives should not be automatically generated from unreliable sources (e.g., file
names should not be used as text alternatives).
Guideline B.2.5 Assist authors with accessible templates and other pre-authored content.
[Techniques]
Rationale: As with automatically-generated content (see Guideline B.1.3), Templates and other pre-authored
content (e.g., clip art, synchronized media, widgets, etc.) that are not accessible impose additional repair tasks on authors.
Applicability Notes:
- Templates may be complicated to check for accessibility due to their inherent incompleteness. The accessibility status of templates is instead measured by the accessibility of content (in the final technology) created through their proper use.
Level A Success Criteria for Guideline B.2.5
- B.2.5.1 Templates "A" Accessible: If the authoring tool automatically selects templates or pre-authored content, then the selection meets WCAG Level A when used.
- B.2.5.2 Provide Accessible Templates: If the authoring tool provides templates, then there are accessible template options for a range of template uses.
- B.2.5.3 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),
- (b) Prominence: any accessible template options have prominence that is comparable with that of other options in
the selection mechanism.
Level AA Success Criteria for Guideline B.2.5
- B.2.5.4 Templates "AA" Accessible: If the authoring tool automatically selects templates or pre-authored content, then the selection meets WCAG Level AA when used.
- B.2.5.5 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.
- B.2.5.6 Templates in Repository: If the authoring tool provides a
repository of templates, then each of the templates has a recorded accessibility status.
- B.2.5.7 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),
- (b) Prominence: any accessible options have prominence that is comparable with that of other options in
the selection mechanism.
- B.2.5.8 Pre-Authored Content in Repository: If the authoring tool provides a repository of pre-authored content, then
each of the content objects has a recorded accessibility status.
Level AAA Success Criteria for Guideline B.2.5
- B.2.5.9 Templates "AAA" Accessible: If the authoring tool automatically select templates or pre-authored content, then the selection meets WCAG Level AAA when used.
Appendix D: Acknowledgments
Appendix Editors:
- Jan Richards (Adaptive Technology Resource Centre, University of Toronto)
- Roberto Scano (IWA/HWG
Participants active in the AUWG at the time of publication:
- Tim Boland (National Institute for Standards and Technology)
- Ann McMeekin (Invited Expert)
- Greg Pisocky (Adobe)
- Jan Richards (Adaptive Technology Resource Centre, University of Toronto)
- Andrew Ronksley (Royal National Institute for the Blind)
- Roberto Scano (IWA/HWG)
- Reed Shaffner (Microsoft)
- Dana Simberkoff (HiSoftware Inc.)
- Jeanne Spellman (W3C)
- Michael Squillace (IBM)
- Jutta Treviranus (WG Chair; Adaptive Technology Resource Centre, University of Toronto)
Other previously active AUWG participants and other contributors to ATAG 2.0:
Kynn Bartlett, Giorgio Brajnik, Judy Brewer, Wendy Chisholm, Daniel Dardailler, Geoff Deering, Barry A. Feigenbaum, Katie Haritos-Shea, Kip Harris, Phill Jenkins, Len Kasday, Marjolein Katsma, William Loughborough, Karen Mardahl, Charles McCathieNevile, Matt May, Matthias Müller-Prove, Liddy Nevile, Graham Oliver, Wendy Porch, Bob Regan, Chris Ridpath, Gregory Rosmaita, Heather Swayne, Gregg Vanderheiden, Carlos Velasco, and Jason White.
This document would not have been possible without the work of those who contributed to ATAG 1.0.
This publication has been funded in part with Federal funds from the U.S. Department of Education under contract number ED05CO0039. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.