AUWG Minutes - 11 July 2005

Attendees:

Jutta Treviranus
Jan Richards
Barry Feigenbaum
Greg Pisocky

JT: Wendy sent request of WCAG 2.0 with a response requested for August 2,
2005.

JR: Everyone should get a general sense. People have the email with the
links to the documents.

AI: Action item is to have the discussion re: WCAG 2.0 at the next
conference call

Agenda:

1. There are still many outstanding proposals that need to be submitted.

These are labeled in:

(a) From the last call comment table:

http://lists.w3.org/Archives/Public/w3c-wai-au/2005AprJun/att-0053/Last_call
_comment_table.html

(b) The guideline draft (guideline 1)

http://jan.atrc.utoronto.ca/public/auwg/guidelines.html

2. F2F planning

Washington, D.C. in September?


3. Bug swatting

http://lists.w3.org/Archives/Public/w3c-wai-au/2005AprJun/0053.html

Jan submitted some additional proposals today

Proposal A.?.1 Ensure that browser-accessed functionality conforms to WCAG
[Priority RP].

PROPOSED:

Rationale: Authors must be able to have access to authoring tool
functionality that is implemented as Web content.

Note: For non-Web-based authoring tools, this is a relatively
straightforward requirement, likely covering only a few areas of the
interface (i.e. Web-based help features, etc.). However, for most Web-based
authoring tools the requirement will cover the majority of functionality in
the tool and overlap most of the other requirements in Part A of the
guidelines.

Proposal A.?.4 PROPOSED:

[1]

Def'n: Preview: A non-editable, rendered view that is intended to emulate a
browser or class of browsers

[2]

Proposal A.?.4 Ensure previews emulate accessible rendering features of
browsers [Priority ?]

Rationale: The workflow of many authoring tools includes periodically
checking a preview of how content will appear in a browser. When this
functionality is not provided by an external browser, the authoring tool
should ensure the same level of accessibility to the content as a browser
would provide.

Note: The *authoring tool user interface* for built-in preview windows must
meet the accessibility requirements in this document. It is only the preview
content window that this checkpoint applies to.

GP: Expressed concerns about asking work in progress to be as accessible as
a finished product.

AI: Jan will be adding a sentence for those situations where the content is
incomplete.

Proposal: A.1.1 Provide text alternatives for all non-text content in the
authoring tool user interface


Proposal: A.3.2 Maintain consistency within the authoring tool user
interface.
[Priority ?]

Rationale: Authors who may become disoriented easily will have less
difficulty when consistent and predictable responses to author actions are
provided. In general, consistent interfaces will benefit all authors to some
degree.

AI: Jan will incorporate the suggestions for rewording these proposals.

Dates for September Face to Face

AI: Post query on the list to determine which are the best dates the week of
Sepetember 19 for the face to face,

Next meeting in two weeks and discuss WCAG Review.

Received on Tuesday, 12 July 2005 20:08:41 UTC