19:52:49 RRSAgent has joined #au 19:52:49 logging to http://www.w3.org/2013/02/11-au-irc 19:52:57 Zakim, this will be AUWG 19:52:57 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start in 8 minutes 19:53:04 Chair: Jutta Treviranus 19:53:15 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2013JanMar/0031.html 19:53:33 Meeting: WAI AU 19:54:01 jeanne has joined #au 19:54:21 Regrets: Sueann N., Roberto S. 19:59:57 WAI_AUWG()3:00PM has now started 20:00:04 +[IPcaller] 20:00:08 +Jeanne 20:00:52 zakim, [IPcaller] is really Jan 20:00:52 +Jan; got it 20:02:32 +[Microsoft] 20:02:44 +[Microsoft.a] 20:03:06 zakim, [Microsoft] is really Alex 20:03:06 +Alex; got it 20:03:19 zakim, [Microsoft.a] is really Cherie 20:03:19 +Cherie; got it 20:04:35 alex has joined #au 20:04:53 +[IPcaller] 20:05:04 +Greg 20:05:23 zakim, [IPcaller] is really Jutta 20:05:23 +Jutta; got it 20:07:53 Topic: 1. "Focus indicator during navigation" issue 20:08:21 Greg_Pisocky has joined #au 20:10:54 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 AL: Why worded this way? 20:12:05 JR: Explains 20:12:16 AL: Thinks you mean linearization of keyboard focus 20:13:05 AL: Could imagine a 2 dimensional up down left right that would not be covered 20:13:58 JT: Any reason to not to require focus indicator for all keyboard interfaces 20:14:49 AL: Number of items is important...many items on screen...focus indicator needed, less so with few items 20:15:21 GP: Very helpful to know where focus lies even with just a few items 20:15:28 AL: I'm talking about one thing 20:17:02 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 has joined #au 20:19:51 JR: I'm ok with this except wondering about ok to have A? 20:20:31 AL: From practical standpoint this is a discrepancy 20:22:19 AL: We may need to do some homework on this one. 20:24:43 +Tim_Boland 20:25:01 JR: Also we are covered by A.1.1.1 and A.1.1.2... 20:25:13 JT: Is this more important in authoring environment 20:25:18 ? 20:25:38 AL: No I don't think its more important for authoring tools 20:25:55 Tim has joined #au 20:26:07 JT: Was highlighted by Alex 20:26:23 AL: Its in the test and shouldn't be 20:26:56 JT: Let's go back and review the test wording 20:27:49 If the authoring tool only includes web-based user interface functionality, then select SKIP. 20:27:51 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 If an external keyboard is required, attach one. 20:27:54 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 ...tool in a graphics editor). 20:27:57 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 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 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 Go to the next function in the list (if any). 20:28:05 Select PASS (all functions must have passed) 20:28:08 https://www.w3.org/2002/09/wbs/35520/20130107-2/results#xq3 20:36:56 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 JT: Any objections to removing this? 20:38:12 scribe: Jan 20:38:23 JT: None heard 20:38:31 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 JT: Still need to add an SC on visivle focus? 20:38:50 JR: I would say not 20:39:17 AL: Also for A.3.1.4 20:39:21 JR: OK 20:40:37 Topic: A.3.2.3 20:40:50 JT: Issue with the examples 20:41:07 JT: Some disagreement about removal of examples 20:41:20 https://www.w3.org/2002/09/wbs/35520/20130107-2/results#xq11 20:42:12 GP: Stop and pause are also used in audio... 20:42:39 GP: There are certain aninmations... eg software simulations 20:43:45 AL: So in that case ... its a different layer 20:44:08 JT: Controls associated with the animation players (scrub bar) 20:46:50 If no parts of the authoring tool user interface can move (e.g. a moving scrub bar control), then select SKIP. 20:47:35 Test 0001 Assertion: If components of the authoring tool user interface can move, the author can pause the movement. 20:47:36 If no parts of the authoring tool user interface can move (e.g. a moving scrub bar control), then select SKIP. 20:47:38 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 Go to the next part of the authoring tool user interface that can move (if any). 20:47:41 Select PASS (all moving parts of the user interface must have passed). 20:47:50 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 Topic: A.3.2.4 Content Edits Saved (Extended): 20:48:35 JT: JR suggested using for a period that exceeds the auto-save period 20:48:37 AL: OK 20:48:54 Resolved: All agree with "period that exceeds the auto-save period" 20:49:04 Topic: A.3.3.1 Static View Option 20:50:01 https://www.w3.org/2002/09/wbs/35520/20130107-2/results#xq13 20:51:34 AL: "Set" in SC is not a problem 20:51:40 AL: "Set" in SC IS a problem 20:51:50 AL" For authoring tools that don't auto-set 20:51:55 AL" For authoring tools that don't auto-PLAY 20:52:44 AL: Suggests edits to SC 20:53:01 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 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 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 JS: Should not mean a substantive change 20:56:28 AL: OK by me 20:56:35 JT: Any concerns? 20:56:39 GP: Fine 20:56:42 TB: Fine 20:56:53 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 JT: Thanks...continue next week. 20:58:09 -Tim_Boland 20:58:10 -Alex 20:58:12 -Jeanne 20:58:12 JT: Soeey...the following week.. 20:58:13 -Cherie 20:58:18 -Jutta 20:58:34 JT: Next call Feb 25th 20:58:43 -Jan 20:58:48 -Greg 20:58:49 WAI_AUWG()3:00PM has ended 20:58:49 Attendees were Jeanne, Jan, Alex, Cherie, Greg, Jutta, Tim_Boland 20:59:06 RRSAgent, make minutes 20:59:06 I have made the request to generate http://www.w3.org/2013/02/11-au-minutes.html Jan 20:59:19 RRSAgent, set logs public 20:59:29 Zakim, bye 20:59:29 Zakim has left #au 20:59:37 RRSAgent, bye 20:59:37 I see no action items