Resolved: To use this text B.1.1 "Rationale: If authoring tools automatically produce web content that includes accessibility problems (WCAG), then this will impose additional repair tasks on authors."

19:15:53 [Jan]

Resolved: Response: AUWG: The Working Group has changed the wording to: B.1.1 "Rationale: If authoring tools automatically produce web content that includes accessibility problems (WCAG), then this will impose additional repair tasks on authors."

19:16:34 [Zakim]

+??P21

19:16:43 [Jan]

Topic: MS2: It would be helpful to have exception for B.2.3.1 in the case of CAPTCHA, decorative, formatting, and invisible images.

19:18:09 [Jan]

AUWG: A note will be added as follows: "B.2.3.1 Alternative Content is Editable (WCAG): If the authoring tool provides functionality for adding non-text content, then authors are able to modify programmatically associated text alternatives for non-text content. Note: An exception can be made when non-text content is known to be decoration, formatting or invisible." The case of CAPTCHA is not...

19:18:10 [Zakim]

-Sueann

19:18:10 [Jan]

...as clear because the purpose must be described and the author may need to contribute.

19:18:50 [Zakim]

+Sueann

19:18:59 [Jutta]

Jutta has joined #au

19:21:40 [Jan]

Note: An exception can be made when non-text content is known to be decoration, formatting, invisible or a CAPTCHA."

19:23:07 [Jan]

Resolved: "Note: An exception can be made when non-text content is known to be decoration, formatting, invisible or a CAPTCHA."

19:23:32 [Jan]

Resolved: AUWG: A note will be added as follows: "B.2.3.1 Alternative Content is Editable (WCAG): If the authoring tool provides functionality for adding non-text content, then authors are able to modify programmatically associated text alternatives for non-text content. Note: An exception can be made when non-text content is known to be decoration, formatting, invisible or a CAPTCHA."

Topic: IBM18: B.2.3.1 - if the tool supports inserting a video, then this requirement means the authoring tool has to provide a way to add/edit captions and video descriptions?

19:24:58 [Jan]

Proposed text: AUWG: No. Text alternatives to non-text content are defined as: "text alternatives for non-text content: Text that is programmatically associated with non-text content or referred to from text that is programmatically associated with non-text content. For example, an image of a chart might have two text alternatives: a description in the paragraph after the chart and a short...

19:25:00 [Jan]

...text alternative for the chart indicating in words that a description follows." Captions and audio descriptions are instead types of "alternatives for time-based media".

Resolved: AUWG: No. Text alternatives to non-text content are defined as: "text alternatives for non-text content: Text that is programmatically associated with non-text content or referred to from text that is programmatically associated with non-text content. For example, an image of a chart might have two text alternatives: a description in the paragraph after the chart and a short text...

19:31:24 [Jan]

...alternative for the chart indicating in words that a description follows." Captions and audio descriptions are instead types of "alternatives for time-based media".

Resolved: AUWG: The Working Group understands this comment to be saying that WCAG conformance is only part of the requirement and that that the missing part is a requirement along the lines of "Web-based user interfaces must be usable on user agents that implement communication with platform accessibility services." This make sense, however, there is much more to user agent accessibility...

19:36:55 [Jan]

...than API communication, so the Working Group has decided to leave requirements in this area to UAAG 2.0. To provide clarification, the following text will be added to the relevant intent sections:

19:36:56 [Jan]

"For A.1.1.1: Note: Even when a web-based user interface has met the requirements of WCAG 2.0, many factors will determine the accessibility of any particular end-user's experience, including (but not limited to): the features and settings of the end-user's user agent, platform, and assistive technology (if any). It is recommended, therefore, that developers of web-based authoring tools be...

19:36:58 [Jan]

...familiar with the accessibility guidance that the User Agent Accessibility Guidelines (UAAG) provides to the developers of user agents. At the time of publication, UAAG version 1.0 is a W3C Recommendation and version 2.0 is under development.

19:37:02 [Jan]

For A.1.2.1:

19:37:03 [Jan]

(Proposed) Note 2 (to follow the existing Note): Even when a non-web-based user interface has followed the relevant user interface accessibility guidelines for the platform, many factors will determine the accessibility of any particular end-user's experience, including (but not limited to): the features and settings of the platform and assistive technology (if any).

19:37:08 [Jan]

For A.1.2.2:

19:37:10 [Jan]

(Proposed) Note 2 (to follow the existing Note): Even when a non-web-based user interface has been designed to expose accessibility information through platform accessibility services, many factors will determine the accessibility of any particular end-user's experience, including (but not limited to): the features and settings of the platform and assistive technology (if any). "

Proposed: AUWG: Rather than adding additional text to scope the success criterion, a note appears in the intent: "Web-based authoring tools will already be required to meet this success criterion as part of a Success Criterion A.1.1.1." which is the requirement for web-based user interfaces to follow WCAG 2.0.

19:41:49 [Jan]

Topic: IBM9

19:41:54 [Jan]

Resolved: AUWG: Rather than adding additional text to scope the success criterion, a note appears in the intent: "Web-based authoring tools will already be required to meet this success criterion as part of a Success Criterion A.1.1.1." which is the requirement for web-based user interfaces to follow WCAG 2.0.

19:42:14 [Jan]

Topic: IBM10

19:42:30 [Jan]

AUWG: WCAG 2.0 does not include a definition of Time Limit, but in the interest of clarity, the Working Group has added one: "Time Limit: The amount of time that an authoring tool provides to an author to perform a task (e.g., read a message, select an item, save a change). Examples include: authoring session timeouts, time-based presentations (e.g. tutorial video)."

19:43:00 [Jan]

Resolved: AUWG: WCAG 2.0 does not include a definition of Time Limit, but in the interest of clarity, the Working Group has added one: "Time Limit: The amount of time that an authoring tool provides to an author to perform a task (e.g., read a message, select an item, save a change). Examples include: authoring session timeouts, time-based presentations (e.g. tutorial video)."

19:43:22 [Jan]

Topic: IBM11

19:43:30 [Jan]

Proposed: AUWG: The success criterion was not meant to imply this because it is quite difficult to qunantify. The success criterion is simply that any exposed markup elements can be be leveraged to allow more efficient navigation of the markup. This could be simple tree-traversal or, as you state, something more sophisticated, such as navigation by ARIA landmark.

19:44:28 [Jan]

JT: Do we want to add anything else?

19:45:00 [Jan]

GP: Its ok

19:46:45 [Jan]

SN: Suspect that being more prescriptive may be problematic.

19:47:25 [Jan]

SN: OK

19:47:32 [Jan]

Resolved: AUWG: The success criterion was not meant to imply this because it is quite difficult to qunantify. The success criterion is simply that any exposed markup elements can be be leveraged to allow more efficient navigation of the markup. This could be simple tree-traversal or, as you state, something more sophisticated, such as navigation by ARIA landmark.

19:48:03 [Jan]

Topic: GZ2

19:48:18 [Jan]

Resolved: AUWG: This change has been made: (b) Match: Matching results can be presented to authors and given focus"

19:48:42 [Jan]

Topic: IBM12

19:48:51 [Jan]

Proposed: AUWG: Audio and haptic display settings are less commonly utilized, but still valid.

19:49:42 [Jan]

JS: Could say we mean "duisplay" in the broader sense.

19:49:57 [Jan]

JT: In the spirit of encouraging multiple modes of presentation.

19:51:28 [Jan]

AUWG: The AUWG intended for "display" to be used in the sense of presenting information across potentially multiple modes. While, audio and haptic display settings are less commonly utilized, they are still valid.

19:52:23 [Jan]

AUWG: The AUWG intends for "display" to be used in the sense of presenting information across potentially multiple modes. While audio and haptic display settings are less commonly utilized, they are still valid.

19:52:40 [Jan]

AUWG: The AUWG intends for "display" to be used in the sense of presenting information across potentially multiple modes. While audio and haptic display settings are less commonly utilized, they are still valid examples.

19:53:01 [Jan]

AUWG: The AUWG intends for "display" to be used in the sense of presenting information across multiple possible modes. While audio and haptic display settings are less commonly utilized, they are still valid examples.

19:53:33 [Jan]

Resolved: The AUWG intends for "display" to be used in the sense of presenting information across multiple possible modes. While audio and haptic display settings are less commonly utilized, they are still valid examples.

19:53:44 [Jan]

Topic: GZ3

19:57:16 [Jan]

@@AUWG: The following changes will be made to the "User Agent" glossary entry:

- In-Market User Agent: A user agent, that can be procured by members of the public (free or otherwise). Usually, an in-market user agent will be a separate software from the authoring tool, however, sometimes a software may combine user agent and authoring tool functionality. These cases include:

19:57:20 [Jan]

- Preview-Only: If the user agent can only render web content that it receives from the associated authoring functionality, then the software is an authoring tool with a "preview" feature. Such preview-only features are not considered in-market user agents.

19:57:22 [Jan]

- User Agent with Authoring Tool Mode: If the user agent functionality must retrieve and open web content before it can be sent to the authoring tool functionality, then the software is a user agent with an authoring tool mode. If the user agent is used to "preview" content produced by the authoring tool mode, then it is to be considered an in-market user agent.

19:57:24 [Jan]

- Combined User Agent/Authoring Tool: A user agent in which the default mode of user interaction enables editing the web content. These tools do not need previews because the author is already experiencing the content in the same way as end users.

19:57:28 [Jan]

And the following entry will be changed:

19:57:30 [Jan]

"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 as it would appear to end users of user agents. Previews may be implemented using actual in-market user agents, but this is not necessary. See the defintion of user agent for more information.

19:57:36 [Jan]

And the following will be added to note #5 in the introduction.

19:57:37 [Jan]

"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").