IRC log of au on 2013-02-11

Timestamps are in UTC.

19:52:49 [RRSAgent]
RRSAgent has joined #au
19:52:49 [RRSAgent]
logging to http://www.w3.org/2013/02/11-au-irc
19:52:57 [Jan]
Zakim, this will be AUWG
19:52:57 [Zakim]
ok, Jan; I see WAI_AUWG()3:00PM scheduled to start in 8 minutes
19:53:04 [Jan]
Chair: Jutta Treviranus
19:53:15 [Jan]
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2013JanMar/0031.html
19:53:33 [Jan]
Meeting: WAI AU
19:54:01 [jeanne]
jeanne has joined #au
19:54:21 [Jan]
Regrets: Sueann N., Roberto S.
19:59:57 [Zakim]
WAI_AUWG()3:00PM has now started
20:00:04 [Zakim]
+[IPcaller]
20:00:08 [Zakim]
+Jeanne
20:00:52 [Jan]
zakim, [IPcaller] is really Jan
20:00:52 [Zakim]
+Jan; got it
20:02:32 [Zakim]
+[Microsoft]
20:02:44 [Zakim]
+[Microsoft.a]
20:03:06 [Jan]
zakim, [Microsoft] is really Alex
20:03:06 [Zakim]
+Alex; got it
20:03:19 [Jan]
zakim, [Microsoft.a] is really Cherie
20:03:19 [Zakim]
+Cherie; got it
20:04:35 [alex]
alex has joined #au
20:04:53 [Zakim]
+[IPcaller]
20:05:04 [Zakim]
+Greg
20:05:23 [Jan]
zakim, [IPcaller] is really Jutta
20:05:23 [Zakim]
+Jutta; got it
20:07:53 [Jan]
Topic: 1. "Focus indicator during navigation" issue
20:08:21 [Greg_Pisocky]
Greg_Pisocky has joined #au
20:10:54 [Jan]
JR: A.3.1.2 Focus Visible: If the *authoring tool* provides *sequential keyboard access*, then a keyboard focus indicator can be visible. (Level A)
20:11:56 [Jan]
AL: Why worded this way?
20:12:05 [Jan]
JR: Explains
20:12:16 [Jan]
AL: Thinks you mean linearization of keyboard focus
20:13:05 [Jan]
AL: Could imagine a 2 dimensional up down left right that would not be covered
20:13:58 [Jan]
JT: Any reason to not to require focus indicator for all keyboard interfaces
20:14:49 [Jan]
AL: Number of items is important...many items on screen...focus indicator needed, less so with few items
20:15:21 [Jan]
GP: Very helpful to know where focus lies even with just a few items
20:15:28 [Jan]
AL: I'm talking about one thing
20:17:02 [Jan]
2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
20:17:15 [Jutta]
Jutta has joined #au
20:19:51 [Jan]
JR: I'm ok with this except wondering about ok to have A?
20:20:31 [Jan]
AL: From practical standpoint this is a discrepancy
20:22:19 [Jan]
AL: We may need to do some homework on this one.
20:24:43 [Zakim]
+Tim_Boland
20:25:01 [Jan]
JR: Also we are covered by A.1.1.1 and A.1.1.2...
20:25:13 [Jan]
JT: Is this more important in authoring environment
20:25:18 [Jan]
?
20:25:38 [Jan]
AL: No I don't think its more important for authoring tools
20:25:55 [Tim]
Tim has joined #au
20:26:07 [Jan]
JT: Was highlighted by Alex
20:26:23 [Jan]
AL: Its in the test and shouldn't be
20:26:56 [Jan]
JT: Let's go back and review the test wording
20:27:49 [Jan]
If the authoring tool only includes web-based user interface functionality, then select SKIP.
20:27:51 [Jan]
If the platform on which the authoring tool is installed cannot be used with a keyboard (i.e. a mobile device that lacks a built in keyboard and cannot be connected via USB, Bluetooth, etc. to any form of external keyboard), then select FAIL. (Note: If this is due to limitations of the platform, "Partial Conformance due to Platform Limitation" is still possible.)
20:27:52 [Jan]
If an external keyboard is required, attach one.
20:27:54 [Jan]
Open authoring tool on the selected platform and document (list) all functions of authoring tool (this could be from authoring tool documentation or author experience with the tool). Do not include any functions where path-dependent input is required. The path exception includes the any data continuously collected from pointing devices, including pressure, speed, and angle (e.g. a paintbrush...
20:27:55 [Jan]
...tool in a graphics editor).
20:27:57 [Jan]
For each function in the list: Check that the function works correctly with the keyboard. If it does not, then select FAIL.
20:27:59 [Jan]
If the function must be accessed by traversing keyboard focus through the authoring tool user interface, check whether a visible focus indicator is provided for the function's user interface controls. If there is not, then select FAIL.
20:28:01 [Jan]
Check the system for situations in which a key press has a time limit. If any key press time limit is found to be less than 20 seconds, then select FAIL.
20:28:03 [Jan]
Go to the next function in the list (if any).
20:28:05 [Jan]
Select PASS (all functions must have passed)
20:28:08 [Jan]
https://www.w3.org/2002/09/wbs/35520/20130107-2/results#xq3
20:36:56 [Jan]
JR: Can just remove "If the function must be accessed by traversing keyboard focus through the authoring tool user interface, check whether a visible focus indicator is provided for the function's user interface controls. If there is not, then select FAIL." - there are other FAIL criteria in the test
20:38:08 [Jan]
JT: Any objections to removing this?
20:38:12 [Jan]
scribe: Jan
20:38:23 [Jan]
JT: None heard
20:38:31 [Jan]
Resolved: remove "If the function must be accessed by traversing keyboard focus through the authoring tool user interface, check whether a visible focus indicator is provided for the function's user interface controls. If there is not, then select FAIL." - there are other FAIL criteria in the test
20:38:48 [Jan]
JT: Still need to add an SC on visivle focus?
20:38:50 [Jan]
JR: I would say not
20:39:17 [Jan]
AL: Also for A.3.1.4
20:39:21 [Jan]
JR: OK
20:40:37 [Jan]
Topic: A.3.2.3
20:40:50 [Jan]
JT: Issue with the examples
20:41:07 [Jan]
JT: Some disagreement about removal of examples
20:41:20 [Jan]
https://www.w3.org/2002/09/wbs/35520/20130107-2/results#xq11
20:42:12 [Jan]
GP: Stop and pause are also used in audio...
20:42:39 [Jan]
GP: There are certain aninmations... eg software simulations
20:43:45 [Jan]
AL: So in that case ... its a different layer
20:44:08 [Jan]
JT: Controls associated with the animation players (scrub bar)
20:46:50 [Jan]
If no parts of the authoring tool user interface can move (e.g. a moving scrub bar control), then select SKIP.
20:47:35 [Jan]
Test 0001 Assertion: If components of the authoring tool user interface can move, the author can pause the movement.
20:47:36 [Jan]
If no parts of the authoring tool user interface can move (e.g. a moving scrub bar control), then select SKIP.
20:47:38 [Jan]
For each part of the authoring tool user interface that can move: If there is no way to pause or stop the motion (e.g. stop button, pause button), then select FAIL.
20:47:39 [Jan]
Go to the next part of the authoring tool user interface that can move (if any).
20:47:41 [Jan]
Select PASS (all moving parts of the user interface must have passed).
20:47:50 [Jan]
Resolved: All agree with If no parts of the authoring tool user interface can move (e.g. a moving scrub bar control), then select SKIP.
20:48:13 [Jan]
Topic: A.3.2.4 Content Edits Saved (Extended):
20:48:35 [Jan]
JT: JR suggested using for a period that exceeds the auto-save period
20:48:37 [Jan]
AL: OK
20:48:54 [Jan]
Resolved: All agree with "period that exceeds the auto-save period"
20:49:04 [Jan]
Topic: A.3.3.1 Static View Option
20:50:01 [Jan]
https://www.w3.org/2002/09/wbs/35520/20130107-2/results#xq13
20:51:34 [Jan]
AL: "Set" in SC is not a problem
20:51:40 [Jan]
AL: "Set" in SC IS a problem
20:51:50 [Jan]
AL" For authoring tools that don't auto-set
20:51:55 [Jan]
AL" For authoring tools that don't auto-PLAY
20:52:44 [Jan]
AL: Suggests edits to SC
20:53:01 [Jan]
AL: A.3.3.1 Static View Option: If the authoring tool contains editing-views that renders visual time-based content automatically, then those editing-views can be paused and can be set to not play automatically
20:53:44 [Jan]
JR: A.3.3.1 Static View Option: If the authoring tool contains editing-views that renders and plays visual time-based content automatically, then those editing-views can be paused and can be set to not play automatically
20:55:46 [Jan]
JR: A.3.3.1 Static View Option: If the authoring tool contains editing-views that render and play visual time-based content automatically, then those editing-views can be paused and can be set to not play automatically
20:56:24 [Jan]
JS: Should not mean a substantive change
20:56:28 [Jan]
AL: OK by me
20:56:35 [Jan]
JT: Any concerns?
20:56:39 [Jan]
GP: Fine
20:56:42 [Jan]
TB: Fine
20:56:53 [Jan]
Resolved: A.3.3.1 Static View Option: If the authoring tool contains editing-views that render and play visual time-based content automatically, then those editing-views can be paused and can be set to not play automatically
20:57:53 [Jan]
JT: Thanks...continue next week.
20:58:09 [Zakim]
-Tim_Boland
20:58:10 [Zakim]
-Alex
20:58:12 [Zakim]
-Jeanne
20:58:12 [Jan]
JT: Soeey...the following week..
20:58:13 [Zakim]
-Cherie
20:58:18 [Zakim]
-Jutta
20:58:34 [Jan]
JT: Next call Feb 25th
20:58:43 [Zakim]
-Jan
20:58:48 [Zakim]
-Greg
20:58:49 [Zakim]
WAI_AUWG()3:00PM has ended
20:58:49 [Zakim]
Attendees were Jeanne, Jan, Alex, Cherie, Greg, Jutta, Tim_Boland
20:59:06 [Jan]
RRSAgent, make minutes
20:59:06 [RRSAgent]
I have made the request to generate http://www.w3.org/2013/02/11-au-minutes.html Jan
20:59:19 [Jan]
RRSAgent, set logs public
20:59:29 [Jan]
Zakim, bye
20:59:29 [Zakim]
Zakim has left #au
20:59:37 [Jan]
RRSAgent, bye
20:59:37 [RRSAgent]
I see no action items