Next AUWG call in THREE WEEKS (Nov 20)

Hi,

The AUWG call ended early today (at 4:30 ET). See notes below:

Since several participants have conflicts with the IDEAS conference, we 
will be pushing back the next AUWG call to Nov. 20, 2006.

Talk to you all then,
Jan

---

Notes from today:

Participants:
Tim Boland
Jan Richards
Greg Pisocky

Regrets:
Jutta Treviranus
Roberto Scano

1. Keyboard requirement proposal by JR:
http://lists.w3.org/Archives/Public/w3c-wai-au/2006OctDec/0000.html

- Resolution: AGREED


2. Group feedback on the techniques draft.

JR's Technique Review: HTML code view editor (Part A only)

GENERAL IDEA: Sufficient techs LABEL should be highlighted.

- Resolution: AGREED.


A.1.4: EDIT TECHNIQUE FOR Checkpoint A.1.4: Technique A.1.4-1.1
[Sufficient]: Separating the author's display settings for fonts,
colors, sizing (zoom), etc. from content presentation settings so that
the content presentation settings, but not the author's display settings
are used within the markup that is actually produced.

- Resolution: JR to re-word.


A.1.5 is short on examples

A.2.1: BREAK UP INTO 3 - Sufficient in combination? - Technique
A.2.1-1.1: [1] Providing sequential keyboard access (with different
keystrokes) for moving the focus between user interface areas (e.g.,
from the menus to the editing view to the floating toolbars, etc.) and
editing views. [2] Also provide sequential keyboard access (with
different keystrokes) for moving the focus within all of the controls
within each user interface area (e.g., the menu items, the editing view
objects, the floating toolbar controls) and editing view. [3] Also
provide the ability to operate any control with the keyboard alone.

- Resolution: AGREED.


A.2.1: BREAK INTO 3 - Sufficient in combination? Technique A.2.1-2.1 [1]
For sequential keyboard access, ensuring that as each control receives
focus, no activation is made automatically that would prevent further
sequential navigation. [2] For direct keyboard access, ensuring that as
the control receives focus, it is only activated if the controls has
only one setting (e.g., a particular menu item). [3] Ensuring that when
controls with more than one setting (e.g., drop down menus) receive the
focus no setting is automatically activated.

- Resolution: AGREED.


A.2.1: SC3: Need to modify to take into account that TAB can also be an
authoring key - e.g. to indent

- Resolution: JR to reword - maybe more examples.


Examples lacking in A.2.1
A.2.2: Examples lacking in A.2.2
A.2.5: Technique A.2.5-1.1 would benefit from a code view example
A.2.5: Need to be clear that code views should be able to SELECT entire
elements etc.

- Resolution: JR to return to list with proposals.


JR's Technique Review: HTML code view editor (Part B)

Lack of examples for B.1.2, B.1.3, B.1.4
Example would help Technique B.2.2-3.1
Lack of examples for B.2.4
B.3.3 code view example needed for B.3.3

- Resolution: JR to return to list with proposals.

Received on Monday, 30 October 2006 21:51:42 UTC