<scribe> scribe:shimizuyohta

Open PR

Simon: 143 by myself, one more change needed and it'll be ready soon.
... Test name change by Yohta
... That test need to be rebased.

Yohta: Take a look into it and ask Jon if I needed help.

Jon: Creation script updated then?

Simon: That was part of test refactorign PR.

More GitHub issue templates check box

Satus on test plans check box

Matt: There was todo for me to what to do with group testing.This week I was focused on design and ran out of time to do this.
... The concern with grouping is that the way the assertion are worded, are I don't hink in line with what freedom scientific and Apple would expect to us.
... One thing they both said was that it'd be better to use group with fieldset.
... We need wording assetions regardign entering/leaving group that we can align to SR developers are saying.
... I'm hoping to keep this discussion asynch.
... We need assertions for aria-role=group, and we need to test that.

Michael: Will it be discussed in the separate issue?
... To me I think it'd be better to have separate issue.

Jon: Need help creating test case?

Proposal for simplifying user interface and test cycle administration check box

Isaac: I have incorporated all feedback and updated the visual wireframe.
... All the visual wireframe match Matt's descriptions.
... Team's working on new estimates for chages we're making.

Matt: In issue 132, people can provide feedback.

<isaacdurazo> New wireframes here: https://github.com/w3c/aria-at/issues/132#issuecomment-616421203

Matt: I modified Isaac descritpin in the way I was picturing. Center piece of all this is initial plan had additional screen for row/result.

Michael: Is there anything blocking this moving forward?

Matt: More eyes/thinking is needed, though there's no time for entire review.

Create tests for APG design pattern: menubar

Yohta: They should be ready to peer-review after rebase.

Matt: After I unblocked checkbox, my focus will move to review it.

Michael: I'll review it again as well.

Matt: In what circumstances role is conveyd/not would be part of discussion. Need to be mindful how SR handle native menu.

Michael: Are you suggesting documentation for those in issue?

Matt: That'd be great. E.g. There's circumstances that SR announce position and set size.
... Differences are noticeable once you dig in, and discussion is needed for that.

Michael: I'll do JAWS, and ask Jon to work on NVDA & VO

Issue 54

Simon: Before we leave test plan, we were to ask AT developers to test review.

Matt: We need to wait by next week.
... After we finish with checkbox and menubar, we can move on to comboobx.

How to pass "menubarEditor" object to test setup script

Simon: Did this change with test refactor Michael?

<Matt_King> https://github.com/w3c/aria-at/issues/147

Jon: For menubar, you have to go and open thing. What I did with example was updated API, and call them. You find DOM node, open and use that node to open that menu.

The way I did it for menubar was to set a variable on the document object on the menubar, and referenced it.

Jon: It wokrs now, but open for ideas.

Simon: Question:is this the proper way to do this?

Matt: Example do a lots of things in response to key stroke.
... In order to get things to certain states, is the most reliable way is emulate key stroke itself, and give that stroke to javascript?

Jon: That's another way to do this.
... I just don't know about timing.
... It didn't seem like reliable in current approach.

Simon: With the test refactor of js, you can create custome scripts.We could expose whatever we need with that functionality.

Jon: Do you think key commands, find elements gonna work reliably?

Simon: We need web driver for that.

Michael: I don't think my PR would affect your ability to do this.

Matt: The other alternative not to do much setup. We could say to user to "Expand X menuitem"
... This makes tester familiar with example.
... If the setup is simple, we can put our resources in user instructions.

Jon: Less scripting is make it easier to reuse example in APG certainly. Complication is menubar is we have hidden thing we wanna have to focus on.
... You could get people close, such as "open the menu and go to item X"
... We have the column to explain people what the script does.

Matt: We may need the issue to track that.Jon can you take on this issue?

Jon: We do have something and I can look into it for next week.

Aria AT - Reports Home Page

<michael_Fairchild> https://github.com/w3c/aria-at/issues/159

Matt: This issue is to design the reports home page. There are some basis thoughts that I put in.
... If anyone wants to contribute here in coming 24 hours, that'd be great if you can.
... Isaac needs to have the design done by next coming Thursday.

Correction next Thursday.

Jemma: I can take a look into it and help Isaac if needed.

Show "pass / total" instead of "pass / fail" in test results

Matt: I think we have consensus for this.

<michael_Fairchild> https://github.com/w3c/aria-at/issues/151

Simon: There was some confusion. Could we adopt "pass / total"

Matt: I'd suggest fewer column to minimize cognitive load.I don't know the number of fail is that helpful in this context.

Michael: Another alternatvive is percentage, such as pass/%

Matt: I'm good with "pass / total". But this is where we'd expect lot of feedback from people.

Consensus: "pass / total"

Consider displaying command titles in addition to keystrokes

Matt: This was intended for test runner.
... I don't know NVDA names are commands, while JAWS names are commands.
... VO names the command.
... This would add information to at command.js structure?

Michael: Right.

Matt: It feels like something could be added later, or easier to add down the road.

Michael: When creating test, we research what commands are relevant, and I thought it's natural to add descriptions as we research.

Matt: Displaying is feature change in runner that can be added anytime.

Simon: This would need to change to add new property.

Matt: There will be places where will be only commands.

Michael: If action is to put PR to change structure, I can do that.

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 zcorpan jongund michael_Fairchild Joe_Humbert shimizuyohta Jemma
Found Scribe: shimizuyohta
Inferring ScribeNick: shimizuyohta

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.)