See also: IRC log
<jeanne> scribe: jeanne
<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2012AprJun/0063.html
<Jan> B.2.3.2 Conditions on Automated Suggestions:
<Jan> B.2.3.3 Let User Agents Repair:
<Jan> B.2.3.2 Generation of Text Alternatives: If the authoring tool automates generation of text alternatives for non-text content, then the following are all true: (Level A)
<Jan> (a) Author Control: If authors are available (i.e. an authoring session is open), then authors have the opportunity to accept, modify, or reject the generated text alternatives prior to the alternatives being inserted into the content. [APPROVED]
<Jan> (b) Identified as Auto-Generated: If authors are not available (i.e. an authoring session has ended), then the generated text alternative is identified such that authors have the opportunity to accept, modify, or reject the generated text alternative during a subsequent authoring session.
<Jan> (c) Contextual Information: Use of descriptive context information possessed by the authoring tool (e.g. that an image is a user's profile picture) is acceptable.
<Jan> (d) Pattern Recognition: Use of the results of pattern recognition algorithms (e.g. Optical Character Recognition) is acceptable.
<Jan> (e) Relevant Properties: Use of text properties of the non-text content that have been defined as being intended for the provision of text alternatives (e.g., metadata "description" field) is acceptable.
<Jan> (f) Irrelevant Properties: Use of text properties of the non-text content that have not been defined as being intended for the provision of text alternatives (e.g., file name, file format, date) is not acceptable.
<Jan> (g) No Generic Strings: Use of generic text strings (e.g. "image") is not acceptable.
<Jan> Note: For automatic generation of other types of content, see success criteria B.1.1.1 and B.1.1.2.
<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2012AprJun/0063.html
<Jan> JR: Not enough people on call to decide.
AL: Are we trying to wordsmith this today?
<Jan> AL: These are AND...
AL: it is not an AND situation, you have to choose one.
JR: You can have an IF within a
list of AND conditions
... What I wonder about is (b) -- there are tools that store
the state of the content, but most HTML editors do not, and how
can it meet (b).
... It isn't locked in, it would have to allow editing.
<Jan> JS: But wouldn't even apply unless tool is auto-generating
JS: Most tools aren't going to automatically generate alternative text . It wouldn't even apply to an HTML editor
SN: I checked with the commenter, and they accepted the update.
<Jan> Resolved: AUWG: There are several points made in the comment:
<Jan> Re: tying communication with platform accessibility services with programmatically determined, it is already tied by a reference to "platform accessibility service" in "programmatically determined".
<Jan> Re: "communicate with", vs "using": The Working Group feels that "using" is too vague and instead proposes: "Platform Accessibility Services: If the authoring tool contains non-web-based user interfaces, then those non-web-based user interfaces expose accessibility information through platform accessibility services."
<Jan> Re: "platform accessibility service": The Working Group is concerned that that term is too vague. The definition should make it clear that IAccessible2 is covered and in fact IAccessible 2 is an example.[APPROVED]
<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2012AprJun/0059.html
<Jan> User agent: Any software that retrieves, renders and facilitates end user interaction with web content (e.g. web browsers, browser plug-ins, and media players). The W3C recommends that user agents follow the W3C-WAI User Agent Accessibility Guidelines (UAAG). However, many software products combine user agent and authoring tool functionality in various ways, including:
<Jan> + Preview-Only: When user agent functionality can only render web content that it receives from the authoring tool functionality (e.g. a preview mode in an HTML editor). Such preview-only features are not considered *in-market user agents*.
<Jan> + User Agent with Authoring Tool Mode: When user agent functionality must retrieve and open web content before it can be sent to the authoring tool functionality (e.g., browser with a built-in authoring tool).
<Jan> + Combined User Agent/Authoring Tool: When the default mode of the user agent enables editing the web content. Such tools do not require previews because the author is already experiencing the content in the same way as end users (e.g., word processor-style editors, wikis).
<Jan> - In-Market User Agent: A user agent that is not *preview-only* and that can be procured by members of the public (free or otherwise).
<Jan> Scribe: Jan
Resolved: Accept wording above for user agent definition
"previews: Views in which no authoring actions are provided (i.e., the view is not editable). Previews are provided to present the web content being edited by the authoring tool more or less as it would appear to end users of in-market user agents. Previews may be implemented using actual in-market user agents, but this is not necessary. See the definition of user agent for more information.
"User Agent Accessibility Guidelines (UAAG) Overview (This will be of special interest to developers of "Combined User Agent/Authoring Tools" and "User Agents with Authoring Tool Modes").
Resolved: All accept changes to preview and introduction bullet
AUWG: The following clarification will be added: "If the authoring tool supports copy and paste of structured content, then any accessibility information (WCAG) in the copied content is preserved when the authoring tool is both the source and destination of the copy-paste and the source and destination use the same web content technology."
Resolved: All accept: "AUWG: The following clarification will be added: "If the authoring tool supports copy and paste of structured content, then any accessibility information (WCAG) in the copied content is preserved when the authoring tool is both the source and destination of the copy-paste and the source and destination use the same web content technology."
AUWG: ATAG 2.0 has introduced a
new conformance type for such situations: "Partial ATAG 2.0
Conformance - Platform Limitations (Level A, AA, or AAA) This
conformance option may be selected when an authoring tool is
unable to meet one or more success criteria because of
intrinsic limitations of the platform (e.g., lacking a platform
accessibility service). The (optional) explanation of...
... conformance claim results should explain what platform
features are missing.
Resolved: All accept "AUWG: ATAG 2.0 has introduced a new conformance type for such situations: "Partial ATAG 2.0 Conformance - Platform Limitations (Level A, AA, or AAA) This conformance option may be selected when an authoring tool is unable to meet one or more success criteria because of intrinsic limitations of the platform (e.g., lacking a platform accessibility service). The (optional)...
scribe: explanation of conformance claim results should explain what platform features are missing."
AUWG: Optimizations do not
involve any change in format. The definition is: "Optimizing
Content Transformations: Transformations in which the content
technology is not changed and the structural features of the
content technology that are employed also stay the same.
Changes would not be expected to result in information loss
(e.g., removing whitespace, replacing in-line styles with
an...
... external stylesheet).
Resolved: All accept: "AUWG: Optimizations do not involve any change in format. The definition is: "Optimizing Content Transformations: Transformations in which the content technology is not changed and the structural features of the content technology that are employed also stay the same. Changes would not be expected to result in information loss (e.g., removing whitespace, replacing...
scribe: in-line styles with an external stylesheet)."
AUWG: The Working Group has judged it infeasible to place accessibility markings throughout the interface as would probably be required to meet the suggested wording. B.2.4.2 is a special case because information about templates (e.g. their name, author, description, etc.) is already frequently displayed.
Resolved: All accept: AUWG: The Working Group has judged it infeasible to place accessibility markings throughout the interface as would probably be required to meet the suggested wording. B.2.4.2 is a special case because information about templates (e.g. their name, author, description, etc.) is already frequently displayed.
AUWG: The term "checking" is clearly defined as encompassing manual checking and a note is also provided on the success criterion. The problem with cutting manual checking out of the definition of accessible checking is that there is a continuous progression of increasing automation that defies easy delineation.
Resolved: All accept: "AUWG: The term "checking" is clearly defined as encompassing manual checking and a note is also provided on the success criterion. The problem with cutting manual checking out of the definition of accessible checking is that there is a continuous progression of increasing automation that defies easy delineation."
AUWG: Whether it is heavyweight depends on the design of the prompting. Unintrusive error detection, such as the red-underlining frequently employed for spell checking is often turned on by default.
"Note: This success criterion requires that features be on by default, but allows developers to provide authors with the option to turn them off or modify their settings."
AUWG: Whether it is heavyweight
depends on the design of the prompting. Unintrusive error
detection, such as the red-underlining frequently employed for
spell checking is often turned on by default. A note that users
can be given the option to turn off accessibility features
appears in the intent: "Note: This success criterion requires
that features be on by default, but allows developers
to...
... provide authors with the option to turn them off or modify
their settings."
... Whether it is heavyweight depends on the design of the
prompting. Unintrusive error detection, such as the
red-underlining frequently employed for spell checking is often
turned on by default. A note that users can be given the option
to turn off accessibility features has been added to the
intent: "Note: This success criterion requires that features be
on by default, but allows...
... developers to provide authors with the option to turn them
off or modify their settings."
Resolved: All accept: AUWG: Whether it is heavyweight depends on the design of the prompting. Unintrusive error detection, such as the red-underlining frequently employed for spell checking is often turned on by default. A note that users can be given the option to turn off accessibility features appears in the intent: "Note: This success criterion requires that features be on by default,...
scribe: but allows developers to provide authors with the option to turn them off or modify their settings."
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/ediotr/editor/ Found Scribe: jeanne Inferring ScribeNick: jeanne Found Scribe: Jan Inferring ScribeNick: Jan Scribes: jeanne, Jan ScribeNicks: jeanne, Jan Default Present: Jan, Jeanne, Alex, Greg, +1.561.236.aaaa, Sueann, Tim_Boland Present: Jan Jeanne Alex Greg +1.561.236.aaaa Sueann Tim_Boland Tim Regrets: Jutta T. Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2012JulSep/0001.html Got date from IRC log name: 09 Jul 2012 Guessing minutes URL: http://www.w3.org/2012/07/09-au-minutes.html People with action items:[End of scribe.perl diagnostic output]