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

[Fwd: [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 16:55:35 -0400
Message-ID: <4884F7C7.6080801@utoronto.ca>
To: WAI-AUWG List <w3c-wai-au@w3.org>

With changes from the call:

JR still needs to work on a few examples of how rendering goes beyond 
visual - eg Braille, voice


----------
(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, and documentation).



----------
In GLOSSARY:

*AUTHORING TOOL USER INTERFACE*
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.

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

CONTENT RENDERING
*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).

DOCUMENT OBJECT
Borrow from UAAG 1.0
(http://www.w3.org/TR/WAI-USERAGENT/glossary.html#def-document-object)

DOCUMENT SOURCE
Borrow from UAAG 1.0
(http://www.w3.org/TR/WAI-USERAGENT/glossary.html#def-document-source)

VIEW
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. *source 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).



Cheers,
Jan

-- 
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




-- 
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 20:54:10 GMT

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