<Matt_King> rrasagent, make log public

scribe?

Issue 188 Global Accessibility Awareness Day comms

<scribe> scribe: Jemma

Boucoup's comm team is working on the event

simon: writing blog post, twitter msg and we send an email to community group tomorrow.

also reaching out to stakeholders, google, mozila, and ask about this project on Thursday.

heads up for any communication coordination - we can retweet those.

blog post will be under Boucoup

mck: any contact to w3c education group?
... will you share the doc so that we can be retweeted by different group, deque, u of i, and so on

<Joe_Humbert> please send to me as well

jon, michale, we can share the news our social media group.

Issue 162 Need volunteers for Pilot test - May 27-June 2

simon: moving this piolot to another week.

we need some testing for pilot test

usablity test does not need to be rescheduled.

if you have any feedback, please update the issue.

I added instruction to issue 162

<zcorpan> https://github.com/w3c/aria-at/issues/162

jon: we may need to add more details to help testers.

rob: what should I as the tester do?

simon: people can ask questions via irc or add comments to the issues

?: is version settled down regarding the test?

simon: firefox is ready

<Joe_Humbert> Joe asked about version

<zcorpan> https://github.com/w3c/aria-at/issues/116#issuecomment-624673182

https://github.com/w3c/aria-at/issues/116

mck: chrome 81 is for sure
... Regarding AT version, I want to be more precise

simon: JAWS 2020.2004.66 - April 2020

NVDA 2019.3.1

macOS 10.15.4

Windows 10 1909, OS build 18363.815

Chrome 81.0.4044.138

Firefox 76.0

Safari 13.1

<Matt_King> SP: AssistiveLabs is possible option for pilot testing, and Simon will provide help with a beta test account if necessary.

simon; we will set up remote the system which has all the browaser and screenread version like that of browser stack

joe: there is recent release for NVDA for 4 days ago

mck: we don't wnat to use 2019 of NVDA version

joe: we just need to make sure that the testers have correct version for the testing

michael: we can collect different version of widows to see the different of test results

mck: mac os - version of os, screen reader are directly connected.

Issue 52 Create tests for APG design pattern: checkbox

simon: I will work on fixing check box issue.

mck: we can unlink between screen reader and pilot testing

simon: I meant prototype, not pilot

mck: two things: 1. consensus on test plan from screen reader developers 2. running pilot test using ARIA-AT app
... it would be ok to use draft version of test for pilot

joe: you may want to notify to testers that this is pilot which will not be used .

mck: we dont have a way to move one test to another test cycle yet. we may do it mannualy.

Issue 53 Create tests for APG example: Editable Combobox With Both List and Inline Autocomplete

menubar

issue 54

https://github.com/w3c/aria-at/issues/54

https://github.com/w3c/aria-at/issues/190

When is not set using setup scripts NVDA is in review mode, but the instructions for the interaction tests tell people to press Escape key which does nothing.

When focus is set using setup scripts NVDA is in interaction mode, but the instructions for the interaction tests tell people to press NVDA+Space which switches to browse mode.

When focus is set using setup scripts JAWS is in PC Cursor mode, but the instructions for the interaction tests tell people to press INSERT+Z which switches to Virtual PC Cursor mode.

The changing states of radio and checkbox menu items close the popup menus and moves focus to corresponding menu item in the menubar, so viewing the changed state requires reopening the popup menu.

JAWS Touch Cursor provides role, state and accessible name. where virtual cursor only reads accessible name

mf: jon may mean "when focus is not set " for first item

jon: when we set focus in NVDA, the problem happens

beep sound indifcate something and put people in the wrong mode

<zcorpan> (I've added a section "What will happen with the pilot test results?" in https://github.com/w3c/aria-at/issues/162)

mck: Testers don't know different sounds whethere it is focus mode or reading(?) mode
... it is litte bizzare to distinguish which mode you are in the screen reader.

in NVDA

does any one know about what is the short cut command for different reading modes?

<jongund> https://github.com/w3c/aria-at/blob/master/tests/resources/at-commands.mjs

<zcorpan> https://github.com/w3c/aria-at/blob/master/tests/resources/keys.mjs

jon: every tester group has own command but it is mapped to common command
... menubar case, if one menu item is selected, it will close the menu unlike radio button

mck: those assertions will be deleted.

jon: if you want to read current information in Jaws, virtual mode, menuitem it would not read role item, only it says status, cheecked or not

mck: interaction mode, in jaws, it just tells you a name, "menu", told you "you are leaving menu", speaking a role can be optional

jon: JAWS only tell you the status only, not role name.
... NVDA, it tells you the role name, menu, how many menu items are there so on.

mck: radio group case can be more clearer in comparison to Menu

mf: how about system level?

jon: we are using vitural cursor mode for test, but if we use touch cursor mode, we can get all these info.

mck: the reason for differences in virtual vs touch is that touch needs more informations
... we have to test utterance against one action, not a series of actions.

jon: 2) I can change harness test so that we can put more instrutions using pipe character. do you want to have separate PR?

<Joe_Humbert> I have to drop

mck: let

's keep one PR

mck: mode instrcutions

jon: mode instruciton is hard coded

other references are not

https://github.com/w3c/aria-at/blob/master/tests/resources/keys.mjs

mck: if you can create PR for keys.mjs and I can merge and update mode instruction

MF: I will do that.

mck: we are not going to have time to discuss menubar before the pilot test.

jon: we are pulling change state out, it will be ok.

rragents, make minutes

s/rrsagent, make minutes/

Jon and Matt will meet this Friday to work on key.mjs file.

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/testiong/testing/
Succeeded: s/running/using/
Succeeded: s/notice/notify/
Succeeded: s/tester/testers/
Succeeded: s/rragent, make minutes//
FAILED: s/rragent, make minutes//
Succeeded: s/rragent/rrsagent/
Present: Matt_King Jemma Joe_Humbert Michael_Fairchild Jongund Rob-fentress simon yohta
Found Scribe: Jemma
Inferring ScribeNick: Jemma

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