W3C home > Mailing lists > Public > w3c-wai-au@w3.org > July to September 2008

[Fwd: Re: Attempt to simplify and harmonize "content display" vs. "chrome" distinction in ATAG2 and UAAG2]

From: Jan Richards <jan.richards@utoronto.ca>
Date: Mon, 21 Jul 2008 15:43:49 -0400
Message-ID: <4884E6F5.1040201@utoronto.ca>
To: WAI-AUWG List <w3c-wai-au@w3.org>

Hi all,

Here's another attempt...

Things to note:
- main wording: content dependent vs. content independent
- Jeanne's "responsibility" idea
- tried to simplify wording and let some other terms do some of the work
- also: how do people feel about "desktop" interface to replace 
"non-Web-based" interface?

(New) "APPLICABILITY" section:

In some cases, a guideline in Part A may apply equally well to both
authoring tool functionalities that reflect the *content being edited*
and those that do not. When it is necessary to remove ambiguity about
the scope of a guideline, the guideline will include one of the
following labels:

*"Content Dependent"*: These guidelines apply only to functionality
which reflects the "content being edited" (e.g., *content renderings*,
the *document object*), which the author may have created with a
different tool and that the authoring tool may or may not *recognize*.

*"Content Independent"*: These guidelines apply only to functionality
which does not vary according to the "content being edited" (e.g., the
authoring tool's menus, user preferences, authoring tool documentation).
In other words, this functionality is wholly the responsibility of the
developer(s) of the authoring tool.


The display and control mechanism that authors use to communicate with
and operate the authoring tool software. User interfaces may be
*Desktop* or *Web-based* or a combination (e.g., a desktop authoring
tool might have Web-based help pages). User interfaces include *content
independent* functions and *content dependent* functions.

The *Web content* that is currently being modified by the authoring tool
for use by other people.

*User interface* functionality that the authoring tool presents as it
renders, plays or executes *Web content*. In this document the term
covers conventional renderings (e.g., "WYSIWYG"), unconventional
renderings (e.g., rendering an audio file as a graphical wavefront) and
*partial renderings*, in which some aspects of the content are rendered,
played, or executed, but not others (e.g., a frame-by-frame video editor
renders the graphical, but not the temporal aspect, of a video.

Borrow from UAAG 1.0

Borrow from UAAG 1.0

User interface functionality that authors use to interact with the
*content being edited*. In addition to being *editable* or
*non-editable* (e.g. a *preview*), there are several broad approaches to
presenting the content:
1. *unrendered content* in which the *document source* is presented
(e.g., plain text editors, form-based editing views that provide direct
access to the unrendered content (e.g., selecting attribute values),
2. *content rendering*, and
3. *meta-content* in which authors set high-level options that the
authoring tool then interprets to generate the resulting content (e.g.,
a content management system that only lets authors set the month and
year on a built-in calendar module).


Jan Richards, M.Sc.
User Interface Design Specialist
Adaptive Technology Resource Centre (ATRC)
Faculty of Information (i-school)
University of Toronto

   Email: jan.richards@utoronto.ca
   Web:   http://jan.atrc.utoronto.ca
   Phone: 416-946-7060
   Fax:   416-971-2896
Received on Monday, 21 July 2008 19:50:36 UTC

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