RE: AUWG Poll #5: 15 October 2007

-----Original Message-----
From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On Behalf
Of Jan Richards
Sent: Monday, October 15, 2007 11:01 PM
To: WAI-AUWG List
Subject: AUWG Poll #5: 15 October 2007


Hi all,

Thanks for all of your poll replies. I think we are really make 
substantive progress.

Note that I have held out the "Authoring Tool" definition for now since 
there are still issues to discuss.

Cheers,
Jan



-----

Instructions:

- Proposed rewordings, issues etc. are listed.

- Members in good standing (http://www.w3.org/WAI/AU/members) have the
following "response" options:
      A: Accept the proposal
      B: Accept the proposal with the changes (then specify changes)
      C: Do not accept the proposal (then specify reason)

- Once 3 people have accepted a proposal (assume my vote is to accept
unless noted) and none have rejected it, I'll start a 3 day timer. If
the timer expires with no rejections then the proposal is assumed to be
carried

- to keep things organized, please respond to the poll as a whole rather
than to individual questions.

-----

Proposal 1: B.2.2.7 Save Status - techs would include EARL
http://www.w3.org/WAI/AU/2007/WD-ATAG20-20071015/WD-ATAG20-20071015.html#che
ck-notify-on-schedule

Response: A

-----

Proposal 2: B.2.5.6 Pre-Authored Content Selection Mechanism
http://www.w3.org/WAI/AU/2007/WD-ATAG20-20071015/WD-ATAG20-20071015.html#che
ck-accessible-preauthored

Response: A

-----

Proposal 3: Definition of "template selection mechanism"
http://www.w3.org/WAI/AU/2007/WD-ATAG20-20071015/WD-ATAG20-20071015.html#def
-Template-Selection-Mechanism

Response: A

-----

Proposal 4: Definition of View (Sub-terms are "Editing View" and "Preview"):

view - also called viewport

*User interface* functionality that *authors* use to interact with
the *content* being edited. Authoring tools often have two types of views:

1. Editing View

Views that both present the content to authors and allow authors to make
modifications to the content. There are several broad approaches to
presenting content for editing, which may be combined:

(a) Instruction Level:
Authors work with non-rendered instructions for the content being edited
(e.g., HTML markup). Examples include plain text editing views as well
as form-based editing views that provide direct access to the
instructions (e.g., selecting attribute values).

(b) Content Renderings:
Authors work with content that is fully or partially rendered, played,
or executed. *Partial renderings* occur when only some aspects of the
content are rendered, played, or executed. For example, a frame-by-frame
video editor may render the graphical aspects, but not the temporal
aspect of a video. Some renderings are *WYSIWYG* because they closely
resemble the appearance and behavior that a *user agent* would produce
(e.g., an HTML editor that displays rich text, images, tables, etc.),
while others are non-WYSIWYG because they differ from those produced by
user agents (e.g., a graphical wavefront editing view of an audio file).

(c) Meta-Content:
Authors work with higher-level or abstract information that the
authoring tool interprets to generate the resulting *content*.
For example, a content management system that allows authors very
limited control (e.g, toggling on/off, setting colors) over it's
built-in content modules (e.g. stock ticker, calendar).


2. Preview:

A non-editable view in which the content being edited is rendered,
played, or executed as it would in a *user agent*.

Response: A

-----

Proposal 5: Modify the definition of "authoring tool user interface" to
make use of "view".

authoring tool user interface

The display and control mechanism that *authors* use to communicate with
and operate the authoring tool software. Authoring tool user interfaces
may be *non-Web-based* or *Web-based* or a combination (e.g., a
stand-alone markup editor with on-line help pages). Authoring tool user
interfaces can be considered in two parts:

1. "Chrome": Any parts of the user interface that do not represent the
content being edited. This includes:
- user interface elements that surround, underlie, and/or super-impose
upon editing views (e.g., text areas, menus bars, rulers, pop-up context
menus).
- user interface elements that are separate from the editing view (e.g.
documentation)

2. Content Display: Any parts of a *view* that represent the content
being edited. This includes:
- plain text content (but not the containing text box control).
- content renderings

*Content Display Accessibility Exemption:* While Part A of ATAG 2.0
generally holds authoring tools responsible for providing accessible
content displays, accessibility problems that are due to the existence
of accessibility problems in the content being edited are exempt from
the requirements. For example, if an author has not yet defined a text
label for an image, it is permissible for a WYSIWYG rendering of that
image to lack a label.

-----

Response: A

Received on Thursday, 18 October 2007 07:16:45 UTC