W3C home > Mailing lists > Public > w3c-wai-au@w3.org > April to June 2001

RE: ATAG2 - Guideline 7

From: Heather Swayne <hswayne@microsoft.com>
Date: Fri, 27 Apr 2001 16:49:35 -0700
Message-ID: <B7E0BEA478EBC24EBB2CF19F710760230170F0E0@red-msg-06.redmond.corp.microsoft.com>
To: "Jan Richards" <jan.richards@utoronto.ca>, <w3c-wai-au@w3.org>
I would like to suggest breaking 7.1 down into 3 guidelines.  Reason
being that earlier today I had to explain to a group of people what the
ATAG meant by "Relative Priority" and this was the one guideline that
they pointed out as not following the definition of "depending on the
corresponding priority in the WCAG."

Break down would look something like...
7.1.1 Ensure that the user interface of the authoring tool follows all
applicable operating system and accessibility standards and conventions
that are essential to accessibility. Priority 1
7.1.2 Ensure that the user interface of the authoring tool follows all
applicable operating system and accessibility standards and conventions
that are important to accessibility. Priority 2
7.1.3 Ensure that the user interface of the authoring tool follows all
applicable operating system and accessibility standards and conventions
that are beneficial to accessibility. Priority 3


 
 -----Original Message-----
From: 	Jan Richards [mailto:jan.richards@utoronto.ca] 
Sent:	Wednesday, April 25, 2001 2:08 PM
To:	w3c-wai-au@w3.org
Subject:	ATAG2 - Guideline 7

Hi everyone,

Here's another shot at the checkpoints for Guideline 7. I have changed
the wording for most of the checkpoints and their subtexts.


Guideline 7. Ensure that the authoring tool is accessible to authors
with disabilities.

Checkpoints:

7.1 Ensure that the user interface of the authoring tool follows all
applicable operating system and accessibility standards and conventions.
[Priority 1 for standards and conventions essential to accessibility;
Priority 2 for those important to accessibility; Priority 3 for those
beneficial to accessibility] 

The techniques for this checkpoint include references to
platform-specific checklists and guidelines and to general guidelines
for accessible applications. 

-----

7.2 Ensure that the user interface of the authoring tool enables authors
to change the presentation of editing views without affecting the
document markup. [Priority 1] 

This checkpoint requires that the author be able to view the content
they are authoring in a way that differs from the presumed appearance of
the rendered content. At minimum, this means supporting the user's
system-wide display preferences and providing alternate textual
representations for non-text elements during editing. 

-----

7.3 Ensure that the user interface of the authoring tool enables authors
to navigation via the document structure within editing views in an
accesible fashion. [Priority 1] 

At minimum, this means allowing the author to search or move focus
between elements of the same type using UI mechanisms that comply with
Checkpoint 7.1. More useful implementations, might allow greater
flexibility to traverse the document tree.

-----

7.4 Ensure that the user interface of the authoring tool enables the
user to edit the document structure and all available properties of each
element of the document in an accessible fashion. [Priority 1]

At minimum, this means ensuring that there is at least one means, that
complies with Checkpoint 7.1, of editing or changing every property
(that is available to be changed and edited by the tool). More useful
implementations might ensure that all means for editing or changing
propeties be accessible.

-----

Cheers,
Jan

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

Jan Richards
Adaptive Technology Resource Centre (ATRC)
University of Toronto

jan.richards@utoronto.ca
Tel: (416) 946-7060  Fax: (416) 971-2896

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
Received on Friday, 27 April 2001 20:46:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 22 September 2008 15:53:00 GMT