Test authoring status

<scribe> scribe: michael_fairchild

Matt: What's the status of the checkbox plan? Has that been reviewed yet?

Michael: I did a first pass and made some changes

(discussion on timeline and process)

Matt: for the first 3, we should all review all 3 test plans
... is the checkbox plan finished for MacOS?

Michael: no
... I can take that on, when does it need to be done?

Val: I think we just need to add commands for VO on MacOS
... does VO have both reading and interactions modes?

Matt: sort of, but I don't think we need any reading mode tests for checkboxes

(discussion of testing quick nav with signle letter nav key, which may be turned off in VO by default)

Michael: I'll try to get VO commands set up by the end of the weekend

Val: how about the menubar tests?

Jon: hopefully by the end of the day, we will have some updated test files

<spectranaut> michael_fairchild: see the link to the test plan here for easier reviewing, and investigate where tests of VoiceOver with quicknav on should be added to the tests of navigating in reading mode

<spectranaut> michael_fairchild: https://github.com/w3c/aria-at/issues/52

Thanks @spectranaut

Jon: (provided an overview of recent changes)
... if there are multiple commands to get the same element, should we test all of them or just some of them (OR vs AND)

Matt: it may depend, do you have an example?

Jon: if you are in reading mode, you can use Tab or Down Arrow.

Matt: we want to test each command

<jongund> https://github.com/w3c/aria-at/blob/master/tests/checkbox/navigate-to-checkbox.html

Jon: has a question about the sequence of the commands and associated instructions

<spectranaut> here is the same test rendered: https://w3c.github.io/aria-at/tests/checkbox/navigate-to-checkbox.html

Michael: concern about the test instructions. Not clear that the tester should reset virtual focus to the top of the page for each command

Matt: the test script can also help to set up the focus location where that is important

Michael: how will we wire up the customized setup JS with the csv file

Matt: there could be a column in the csv that describes what the set up script should do. After the tests are generated, those comments need to be implemented

(discussion of how complex these scripts might be)

val: how is combobox coming along?

Matt: I'm converting it to the CSV
... My goal is to finish writing them this afternoon

Jon: In menubar, there are several ways to navigate to several different roles within the menubar. How should we write that?
... I think these are 4 separate tests: navigate to menu bar, open the menu bar, navigate to something within the menu bar, etc

Val: please open a new issue if you find out that we need to change the test design
... goal for wed - for all of the tests that are in progress, everyone read through all of the tests so that we can can have a discussion on the language used in the tests

test plan review page

<spectranaut> test plan review page: https://w3c.github.io/aria-at/review-test-plans/

<spectranaut> related to issue: https://github.com/w3c/aria-at/issues/37

Matt: might be good to have a filter for different ATs

Michael: would also be good to describe what the set up script should do for each test

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Matt_King isaacdurazo spectranaut zcorpan Erika_Miguel shimizuyohta michael_fairchild
Found Scribe: michael_fairchild
Inferring ScribeNick: michael_fairchild

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)