See also: IRC log
<scribe> scribe: Jan
JT: Closure is tomoorow (June
... We have received 1 comment so far
... We need to prompt people
... Are there indicators of anyone sles preparing them
SN: That's my plan
JR: Not aware of others
GP: We have looked at it and are fine with what we see
JT: Have heard a few people who
say it is ok
... I know of one other person preparing comments
... If we only have 1-2 comments by tomorrow...
JS: We could process comments we have and move towards CR
JT: Results - we are split. Which is not good.
JS: Do we want to look at another time? Sept?
JT: OK good to check out other locations and times before.
GP: Always open invite to Adobe in DC.
JT: Open invite to IDRC in Toronto
JS: And several invites to
... Maybe Jutta can start us off by proposing dates that are ok.
JT: I will send some times
JS: OK, then I can setup a survey
JS: Prototype test harness at http://w3c-test.org/framework/suite/ATAG20-LC-20120410/
JS: First page are all the groups using the framework
JS: They have taken all of the ATAG SCs and put them in a database.
JT: Helpful to recruit from beyond the group?
JR: Good HTML doc for adding tests: http://www.w3.org/WAI/AU/2012/ATAG20tests/ATAG2-DDApril2012PublicWD-Tests-rev201205DD
A.3.1.2 No Keyboard Traps: If keyboard focus can be moved to a component using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, authors are advised of the method for moving focus away. (Level A)
JS: 1. Open or paste in the "Comprehensive non-accessible test content (Level A, AA, AAA)"
JR: 2. Using the keyboard only,
explore the authoring tool user interface attempting to move
focus to every enabled control.
... 3. Using the keyboard only, explore the content being edited in a sequential fashion (e.g. arrow keys to move through a rich text editor) attempting to move editing focus to every part of the content being edited.
... 4. If at any point, the keyboard focus cannot be moved away from a component (or group of components) then the SC fails, otherwise it passes.
... 5. If at any point, the standard conventions (e.g. arrow keys, tab, etc,.) do not allow focus to be moved away from a component or group of components, BUT you find (e.g. with an online search) of a way to move the focus away, determine whether the method is documented either in the UI or in the documentation. If so, then the SC passes, if not then it FAILS.
B.1.2.2 Copy-Paste Inside Authoring Tool (WCAG): If the authoring tool supports copy and paste of structured content, then any accessibility information (WCAG) in the copied content is preserved when the authoring tool is both the source and destination of the copy-paste.
JR: 1. Open or paste in
"Comprehensive accessible test content".
... 2. Make a copy of the content (e.g. via select all, past, copy; or other duplicate function)
... 3. Save resulting content
... 4. Apply the "Web Content Accessibility Test Procedure"
... 5. If the saved content passes the procedure, then the SC passes, otherwise the SC fails.
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 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 WARNING: No "Present: ... " found! Possibly Present: GP Greg Greg_ JR JS JT Jan Jeanne Jutta P1 P26 SN Sueann Tim Tim_Boland aaaa https jeanne__ trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Regrets: Cherie_E. Alex_L. Alessandro_M. Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2012AprJun/0041.html Got date from IRC log name: 04 Jun 2012 Guessing minutes URL: http://www.w3.org/2012/06/04-au-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]