See also: IRC log
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)
AL: Why worded this way?
JR: Explains
AL: Thinks you mean linearization
of keyboard focus
... Could imagine a 2 dimensional up down left right that would
not be covered
JT: Any reason to not to require focus indicator for all keyboard interfaces
AL: Number of items is important...many items on screen...focus indicator needed, less so with few items
GP: Very helpful to know where focus lies even with just a few items
AL: I'm talking about one thing
2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
JR: I'm ok with this except wondering about ok to have A?
AL: From practical standpoint
this is a discrepancy
... We may need to do some homework on this one.
JR: Also we are covered by A.1.1.1 and A.1.1.2...
JT: Is this more important in authoring environment
?
AL: No I don't think its more important for authoring tools
JT: Was highlighted by Alex
AL: Its in the test and shouldn't be
JT: Let's go back and review the test wording
If the authoring tool only includes web-based user interface functionality, then select SKIP.
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.)
If an external keyboard is required, attach one.
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...
scribe: tool in a graphics editor).
For each function in the list: Check that the function works correctly with the keyboard. If it does not, then select FAIL.
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.
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.
Go to the next function in the list (if any).
Select PASS (all functions must have passed)
https://www.w3.org/2002/09/wbs/35520/20130107-2/results#xq3
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
JT: Any objections to removing this?
<scribe> scribe: Jan
JT: None heard
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
JT: Still need to add an SC on visivle focus?
JR: I would say not
AL: Also for A.3.1.4
JR: OK
JT: Issue with the examples
... Some disagreement about removal of examples
https://www.w3.org/2002/09/wbs/35520/20130107-2/results#xq11
GP: Stop and pause are also used
in audio...
... There are certain aninmations... eg software
simulations
AL: So in that case ... its a different layer
JT: Controls associated with the animation players (scrub bar)
If no parts of the authoring tool user interface can move (e.g. a moving scrub bar control), then select SKIP.
Test 0001 Assertion: If components of the authoring tool user interface can move, the author can pause the movement.
If no parts of the authoring tool user interface can move (e.g. a moving scrub bar control), then select SKIP.
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.
Go to the next part of the authoring tool user interface that can move (if any).
Select PASS (all moving parts of the user interface must have passed).
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.
JT: JR suggested using for a period that exceeds the auto-save period
AL: OK
Resolved: All agree with "period that exceeds the auto-save period"
https://www.w3.org/2002/09/wbs/35520/20130107-2/results#xq13
AL: "Set" in SC is not a
problem
... "Set" in SC IS a problem
AL" For authoring tools that don't auto-set
AL" For authoring tools that don't auto-PLAY
AL: Suggests edits to SC
... 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
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
... 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
JS: Should not mean a substantive change
AL: OK by me
JT: Any concerns?
GP: Fine
TB: Fine
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
JT: Thanks...continue next
week.
... Soeey...the following week..
... Next call Feb 25th
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: Jan Inferring ScribeNick: Jan Default Present: Jeanne, Jan, Alex, Cherie, Greg, Jutta, Tim_Boland Present: Jeanne Jan Alex Cherie Greg Jutta Tim_Boland Regrets: Sueann_N. Roberto_S. Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2013JanMar/0031.html Got date from IRC log name: 11 Feb 2013 Guessing minutes URL: http://www.w3.org/2013/02/11-au-minutes.html People with action items:[End of scribe.perl diagnostic output]