Minutes

IRC Logs

Action Items
ACTION: JR to Look around for W3C defn of markup and markup language.
ACTION: JR to Look through ATAG 2.0 for situations where term "user interface component" should appear
ACTION: JS to Remove "Mainstream Applications"
ACTION: JS to To use the new version of Platform
ACTION: JS to Use new defn of Option
ACTION: JS to Use new version of "tutorial"
ACTION: JS to Use new version of "user interface component "
ACTION: JS to Use new version of View
ACTION: JS to Use the new version of "recognized (by the tool)"
ACTION: JS to Use version of "Platform Accessibility Archiecture" without "Mainstream"

Text of Minutes
W3C
WAI AU
09 Feb 2009

Agenda

See also: IRC log
Attendees

Present
    Jan, AnnM, SueAnn, Jeanne, Greg
Regrets
    Andrew_R., Tim_B., Roberto_S.
Chair
    JR
Scribe
    AnnM

Contents

    * Topics
         1. Mainstream Application
         2. Markup
         3. Option
         4. Platform
         5. recognized (by the tool)
         6. Tutorial
         7. user interface component
         8. view
    * Summary of Action Items

 

 

<JR> Scribe: AnnM

<JR> http://www.w3.org/2002/09/wbs/35520/20090206/results

<JR> http://www.w3.org/2002/09/wbs/35520/20090206/results
Mainstream Application

<JR> A programmatic interface that is specifically engineered to provide communication between mainstream applications and assistive technologies (e.g., UIA, MSAA and IAccessible2 for Windows applications, AXAPI for MacOSX applications, Gnome Accessibility Toolkit API for Gnome applications, Java Access for Java applications, etc.). On some platforms it may be conventional to enhance communication furt

<JR> her by implementing a document object.

<JR> A programmatic interface that is specifically engineered to provide communication between applications and assistive technologies (e.g., MSAA, IAccessible2, UI Automation for Windows applications, AXAPI for MacOSX applications, Gnome Accessibility Toolkit API for Gnome applications, Java Access for Java applications, etc.). On some platforms it may be conventional to enhance communication...

<JR> ...further by implementing a DOM.

Agreed to use drop the use of the word mainstream when talking about applications, as per UAAG.

<JR> A programmatic interface that is specifically engineered to provide communication between applications and assistive technologies (e.g. MSAA and UI Automation for for Windows applications, AXAPI for MacOSX applications, Gnome Accessibility Toolkit API for Gnome applications, Java Access for Java applications, etc.). On some platforms it may be conventional to enhance communication further...

<JR> ...by implementing a document object.

<JR> ACTION: JS to Use version of "Platform Accessibility Archiecture" without "Mainstream" [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action01]

<trackbot> Created ACTION-101 - Use version of \"Platform Accessibility Archiecture\" without \"Mainstream\" [on Jeanne Spellman - due 2009-02-16].

<JR> ACTION: JS to Remove "Mainstream Applications" [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action02]

<trackbot> Created ACTION-102 - Remove \"Mainstream Applications\" [on Jeanne Spellman - due 2009-02-16].
Markup

<JR> A set of tags from a markup language. Markup can be presentational (i.e., markup that encodes information about the visual layout of the content), structural (i.e., markup that encodes information about the structural role of elements of the content) or semantic (i.e., markup that encodes information about the intended meaning of the content). A markup language is a syntax and/or set of...

<JR> ...rules to manage markup (e.g., HTML, SVG, MathML).

<JR> ACTION: JR to Look around for W3C defn of markup and markup language. [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action03]

<trackbot> Created ACTION-103 - Look around for W3C defn of markup and markup language. [on Jan Richards - due 2009-02-16].
Option

<JR> option

<JR> When an author is presented with choices. An option may be local (e.g., prompting whether to save before ending an authoring session) or global (e.g., preference settings).

<JR> ACTION: JS to Use new defn of Option [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action04]

<trackbot> Created ACTION-104 - Use new defn of Option [on Jeanne Spellman - due 2009-02-16].

agreed to go with proposed new wording.
Platform

<JR> The software environment within which the authoring tool operates. In the case of Web-based authoring tool user interfaces, this will be user agents. In the case of non-Web-based authoring tool user interfaces, this will be operating systems (e.g., Windows, MacOS, Linux), virtual machines (e.g., JVM), etc. Information is *available via the platform* (to assistive technologies) when it is...

<JR> ...communicated programmatically by the authoring tool to the platform, which then facilitates onward programmatic communication to assistive technologies. For non-Web-based user interfaces, this means via an implemented *platform accessibility architecture*. For Web-based user interfaces, this means following relevant Web content accessibility design guidelines so that the user agent can...

<JR> ...pass on the information.

<JR> I got kicked off...calling back

<JR> SN: Gives eclipse introduction...

<JR> SN: Has it's own browser widget...

<JR> SN: Used to generate content that could run in browser

<JR> SN: e.g. to create an HTML formatted report

<JR> The software environment within which the authoring tool operates. In the case of Web-based authoring tool user interfaces, this will be user agents. In the case of non-Web-based authoring tool user interfaces, this will be operating systems (e.g., Windows, MacOS, Linux), virtual machines (e.g., JVM), etc. Information is *available via the platform* (to assistive technologies) when it is...

<JR> ...communicated programmatically by the authoring tool to the platform, which then facilitates onward programmatic communication to assistive technologies. For non-Web-based user interfaces, this means via an implemented *platform accessibility architecture*. For Web-based user interfaces, this means following relevant Web content accessibility design guidelines so that the user agent can...

<JR> ...pass on the information.

<JR> ACTION: JS to To use the new version of Platform [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action05]

<trackbot> Created ACTION-105 - Use the new version of Platform [on Jeanne Spellman - due 2009-02-16].

agreed to drop the mention of "higher level GUI toolkit (e.g., Eclipse)" from definition.
recognized (by the tool)

<JR> ACTION: JS to Use the new version of "recognized (by the tool)" [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action06]

<trackbot> Created ACTION-106 - Use the new version of \"recognized (by the tool)\" [on Jeanne Spellman - due 2009-02-16].

agreed to accept proposed rewording of "recognized (by the tool)"
Tutorial

<JR> A type of documentation that provides step-by-step instructions for performing multi-part tasks.

<JR> ACTION: JS to Use new version of "tutorial" [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action07]

<trackbot> Created ACTION-107 - Use new version of \"tutorial\" [on Jeanne Spellman - due 2009-02-16].

agreed to accept proposed rewording of "tutorial"
user interface component

<JR> A part of the user interface or content display (including renderings) of the authoring tool that is perceived by authors as a single control for a distinct function.

<JR> ACTION: JS to Use new version of "user interface component " [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action08]

<trackbot> Created ACTION-108 - Use new version of \"user interface component \" [on Jeanne Spellman - due 2009-02-16].

<JR> ACTION: JR to Look through ATAG 2.0 for situations where term "user interface component" should appear [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action09]

<trackbot> Created ACTION-109 - Look through ATAG 2.0 for situations where term \"user interface component\" should appear [on Jan Richards - due 2009-02-16].

<JR> JR: When next editors draft?

<JR> JS: Will work on it tomorrow...hopefully this week...certainly by Friday
view

<JR> A user interface function that authors use to interact with the content being edited. ATAG 2.0 categorizes views according to whether they support editing and the way in which they present content. There are two options for supporting editing in a view:

<JR> 1. editing views are editable.

<JR> 2. previews are not editable and present content as it would appear in a user agent.

<JR> There are three approaches to presenting the content in a view:

<JR> 1. as source content in which the unrendered content is presented (e.g., plain text editors, form-based editing views that provide direct access to the unrendered content (e.g., selecting attribute values),

<JR> 2. as content rendering, and

<JR> 3. as meta-content in which authors set only high-level options that the authoring tool then interprets to generate the resulting content (e.g., a content management system with a calendar module that limits author actions to toggling the calendar on or off).

<Greg> prompting on vs. prompting off?

<JR> A user interface function that authors use to interact with the content being edited. ATAG 2.0 categorizes views according to whether they support editing and the way in which they present content. There are two options for supporting editing in a view:

<JR> 1. editing views are editable.

<JR> 2. previews are not editable and present content as it would appear in a user agent.

<JR> There are three approaches to presenting the content in a view:

<JR> 1. as source content in which the unrendered content is presented (e.g., plain text editors),

<JR> 2. as content rendering, and

<JR> 3. as pre-built content in which authors set only high-level options that the authoring tool then interprets to generate the resulting content (e.g., a content management system with a calendar module).

<JR> 3. as pre-built content in which authors set only high-level options that the authoring tool then interprets to generate the resulting content (e.g., a calendar module in a content management system).

<JR> JR: No call next week

<JR> ACTION: JS to Use new version of View [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action10]

<trackbot> Created ACTION-110 - Use new version of View [on Jeanne Spellman - due 2009-02-16].
Summary of Action Items
[NEW] ACTION: JR to Look around for W3C defn of markup and markup language. [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action03]
[NEW] ACTION: JR to Look through ATAG 2.0 for situations where term "user interface component" should appear [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action09]
[NEW] ACTION: JS to Remove "Mainstream Applications" [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action02]
[NEW] ACTION: JS to To use the new version of Platform [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action05]
[NEW] ACTION: JS to Use new defn of Option [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action04]
[NEW] ACTION: JS to Use new version of "tutorial" [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action07]
[NEW] ACTION: JS to Use new version of "user interface component " [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action08]
[NEW] ACTION: JS to Use new version of View [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action10]
[NEW] ACTION: JS to Use the new version of "recognized (by the tool)" [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action06]
[NEW] ACTION: JS to Use version of "Platform Accessibility Archiecture" without "Mainstream" [recorded in http://www.w3.org/2009/02/09-au-minutes.html#action01]
 
[End of minutes]