PART A: Make the user interface accessible
1.1 Ensure that browser-accessed functionality conforms to WCAG [Priority RP]
- user interface
From_UAAG.21 Provide author profile functionality.
1.X Ensure that documentation is accessible. [RP]
- At least one version of the documentation must be provided as Web
content that conforms to WCAG (whether or not
delivered on the Web). @@clean up def of
WebCcontent to include HTML, PDF, Flash, Word docs, etc.@@.
1.X Ensure previews emulate accessible rendering features of browsers @@def'n
of preview: A non-editable, rendered view that is intended to emulate a browser
or class of browsers.@@:
- Preview functions must provide the accessible rendering
features of the browser or class of browsers being emulated @@identified
in the conformance profile@@ and/or allow the author to choose
an alternative browser to perform the preview.
A.1: Authoring Interface must be Perceivable
A.1.1 Provide text alternatives for all non-text
content in the user interface @@ensure preview rendered
view out clause is in the defn@@
Success Criteria:
- All non-text objects in the authoring tool user interface that have information
value (e.g., toolbar icon, placeholder image, sound effect, etc.) must have
a text alternative.
- All editing views must always
include an option to display any available text
alternatives for non-text objects in the content.
A.1.2 Provide synchronized alternatives
for multimedia.
Success Criteria:
- All multimedia in the authoring tool user interface that has information
value (e.g., progress indicators, etc.) must have
synchronized alternatives.
- All editing views must always
include an option to display any available
synchronized alternatives for multimedia in the content.
Provide
A.1.3 Ensure that the visual presentation is configurable. [@@add success
criteria on foreground/background distinguishability] JT-to propose
- user interface
A.1.4 Ensure that the audio presentation is configurable. JT-to propose
- user interface
- A.1.5 Ensure enhanced access to multimedia. JT-to propose
- user interface
A.1.6 Allow
the display preferences of the editing view to be changed
without affecting the document markup. [Priority 1]
A.1.7 Ensure that all user interface controls have clearly associated labels.
- (covers input fields, table cells, etc.) BAF to propose some succ. crit.
A.2: Authoring Interface must be Operable
A.2.X "Configurability of operability" - JT to propose
A.2.1 Make all functionality operable
via a keyboard or a keyboard interface.
Success Criteria:
- The author must be able, through keyboard input alone, to perform
any authoring task (e.g. navigating, selecting, and editing content with
editing views, operating the authoring tool
user interface, installing
and configuring the authoring tool, and accessing documentation) that is
available through the user interface.
- Follow @@operating environment conventions for
keyboard control.
- Single-key access must be provided to the following functionalities:
- Key-plus-modifier-key (or single-key) access must be provided to the
following functionalities in the user interface (if present):
- move @@content focus to the previous enabled control
- navigate between panels or windows
- open help system
- open new content
- open existing content
- save content
- close content
- cut/copy/paste
- undo/redo
- open find/replace function
- navigate to the start and end
A.2.2 Allow authors to control time limits
on their reading or interaction.
Success Criteria:
- All user interface time limits must be configurable
unless they are controlled by time-sensitive external processes (e.g. time-outs
of systems outside of the authoring tool).
A.2.3 Allow users to avoid content that could
cause photosensitive epileptic seizures.
Success Criteria:
- Authors must be able to turn off flashing in the user interface that violates
international health and safety standards for general flash or red flash.
A.2.4 Ensure that
editing views enable the author to navigate the structure and perform
structure-based edits. [Priority 2]
Success Criteria:
- In any element hierarchy, the author must always be able, with
a device-independent action, to move the editing
focus from any element to any of the following elements, if they exist:
the element immediately above (i.e. parent), the first element immediately
below (i.e. child), the element immediately preceding at the same level
(i.e. previous sibling), and the element immediately following at the same
level (i.e. next sibling).
- In any element hierarchy, the author must always be able, with
a device-independent action, to select content
and perform editing functions on any element along with any content, including
subelements.
- @@add proposal - that takes into graphs -BF
to propose@@
A.2.5 Allow the author
to search content and markup within the editing views. [Priority 2]
Success Criteria:
- The author must be able to perform text searches of all content
or markup that is editable by the author.
A.2.6 Provide an undo function.
Success Criteria:
- Actions that modify content must be either reversible with an
undo and redo function or include a warning to the author that the action
is irreversible.
A.2.7 Separate selection from activation
Success Criteria:
- There must be an option that ensures that moving
the content focus to or from any control in the user interface
does not automatically activate any explicitly associated event handlers of any event type.
GL3: Authoring Interface must be Understandable
A.3.1 Observe
operating environment conventions for the authoring tool user interface, documentation, input configurations,
and installation.
A.3.2 Organize content consistently
from "page to page" and make interactive components behave in predictable
ways.@@"Maintain consistency within the authoring tool user interface."@@
A.3.3 Configurability for "individual conventions".
A.3.4 Document
all authoring interface accessibility features.
Success Criteria:
- All features that benefit the accessibility of the authoring interface must be
documented in the help system.
- Default keyboard bindings must be documented in the help system.
- The current author preferences for @@input configurations must be
displayed in either a centralized fashion (e.g., a list of bindings) or
a distributed fashion (e.g., by listing keyboard shortcuts in user interface
menus)
GL4: Authoring Interface must be Access System Friendly
A.4.1 Support interoperability with assistive technologies. [Priority 1]
Success Criteria:
- The authoring tool must conform to accessibility platform architectures
(e.g. MSAA, Java Access, etc.).
- If there is any authoring tool functionality or information that is not
addressed by available accessibility platform architectures, an interoperability
mechanism must be provided such that all authoring task could
be accomplished in at least one way by an assistive technology implementing
the mechanism.
PART B: Support the production of accessible content
GL1: Enable the production of accessible content
2.1 Support technologies that
enable the creation of Web content that conforms to WCAG. [Priority 1]
2.2 Ensure
that the tool preserves all unrecognized markup and accessibility information
during transformations and conversions. [Priority 2]
...
GL2: Support the author
in the production of accessible content
3.1 Prompt
and assist the author to create content that conforms to WCAG. [Web Content Checkpoints Relative to WCAG]
...
GL3: Promote and integrate accessibility solutions
4.1 Ensure that
the most accessible option for an authoring task is given priority. [Priority 2]
...