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

Re: Proposed Rewording for Checkpoints 2.1.2, 2.1.3, 2.1.4 (resend)

From: Charles McCathieNevile <charles@w3.org>
Date: Thu, 3 Jun 1999 18:27:58 -0400 (EDT)
To: "gregory j. rosmaita" <oedipus@hicom.net>
cc: Authoring Tools WG <w3c-wai-au@w3.org>, Unagi San <unagi69@concentric.net>
Message-ID: <Pine.LNX.4.10.9906031752301.22019-100000@tux.w3.org>
I prefer the second, briefer wording for the current 2.1.2, with the
definitions given.

I would like to propose that we reword 2.1.3 and 2.1.4, in part based on
Bruce Roberts' proposal initially suggested in April, as follows:

Allow the author to identify (in an accessible way) all elements and
properties in the document which are available for editing. [P1]

I am assuming in this that identify in this checkpoint, combined with 2.4.1
allow the author to edit (everything) is enough to explicitly require the
ability to read the various objects.

As a further point of clarification, I am wondering about the scope of 2.1.2.
It seems to me that it is only a P1 requirement in so-called WYSIWYG editing,
although in that case the need is pretty clear.

In fact WYSIWYG editing, and the ability to display textual equivalents of
objects in the document (and visual equivalents as well - a sound object
might have a textual identifier, a visual icon, and a transcript or
description file), seem like partial approaches to satisfying 2.1.3 / 2.1.4,
given the requirement that WYSIWYG editing allows for different rendering in
the editing view and in the published version.

This requirement also relates to checkpoint 2.1.1 and the User Agent
Guidelines, but I will write about that as a separate proposal.

cheers

Charles

On Thu, 3 Jun 1999, gregory j. rosmaita wrote:

  aloha, all!
  
  in fulfillment of one of the action items i took at yesterday's
  teleconference, here is my proposed rewording for the Checkpoints
  currently numbered 2.1.2, 2.1.3, and 2.1.4
[snip]  
  --- begin proposed rewording of Checkpoints 2.1.2 through 2.1.4 ---
  2.1.2: [Priority 1]
  The author must be able to change the rendered view of the document 
  currently being edited without changing the presentational markup defined
  for the published document. 
  
  - OR -
  
  The author must be able to change the editing view without changing the
  presentational markup defined for the document currently being edited.
  
  2.1.3: [Priority 1] 
  Allow the author to display a textual equivalent of each element or object.
  
  2.1.4: [Priority 1] 
  For each element of a document, the properties of that element must be
  accessible to the author. 
[snip]  
  "editing view"
  	What is displayed by the authoring tool to the author during
  	the editing process.
  
  "rendered view"
  	What is displayed by the authoring tool to the author as a 
  	means of simulating how a user of the document being 
  	edited will interact with the document currently being edited as a
  	published document.
Received on Thursday, 3 June 1999 18:28:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:39:42 UTC