W3C

- DRAFT -

SV_MEETING_TITLE

10 Sep 2020

Attendees

Present
JoeHumbert, jongund, rob-fentress, michael_fairchild, Juliette_McShane, Jesdaigle, Jemma_
Regrets
Chair
SV_MEETING_CHAIR
Scribe
jongund

Contents


start meeting

start this meeting

https://www.w3.org/2001/12/zakim-irc-bot.html

<scribe> scribe: jongund

New call time and platform

MF: How is it going?
... Anything else for the agenda?
... Last meeting we decided to move the time to Thursdays at this time, every other Thursdays
... Doesn't seem to be an issue with the change, any concerns?
... Glad it is working
... Moving from Bluejeans to Zoom, did anyone have any issues connecting?

HR: I am very confortable with it

Update from Bocoup

Jes: We are still doing work on APG
... We are early stages of scoping work for the next ARIA-AT test hareness
... Just trying to collect information

MF: Thank you for the update. Matt would have more information on the work with Bocoup

HR: I am a new member, is Bocoup creating all the test cases

<JoeHumbert> Zoom just stopped for me

MF: No, Bocoup is contracted with the test harness and reporting results
... Matt is working with another company to help build test authoring
... The community group can help out wherever you can
... Members can authoring tests
... I am the product owner for the automation, if you want to help out contact me
... Matt is better to coordinate on test cases

BF: By automation prototype ...

MF: It is a prototype, it will not be able to even do a single test
... The goal, is to test a single test, to automate that, drive a screen reader and then can get results

BF: What screen reader?

MF: Toss up for NVDA or VoiceIver

HR: Not an accessibility checker, like an according, it clicks on some tabs and see if the correct things are spoken

MF: You could say, navigate to this button and then see if the assertions for the button are met
... Any other questions on that?

Automated Testing

MF: Continuation of previous topic

Documentation on test

JG: No, I will try to do before next meeting

MF: Leave it on the agenda for the next time

Issue 295 Reusing assetions

MF: We talked about this last time
... Instead of duplicating assertions, we could just reference them
... Matt thought this was a good idea, but no decisions have been made

JG: It will make it more difficult for newbies to learn, but if there is going to be a compnay developing them, they will be familiar

HR: I am generally support it, but concerned about the level of complexity
... Concerned about overhead to the work

MF: I will make a comment in the issue
... Not sure how much work this is to implement, and not sure how much efficiency it would add to authoring

JG: If there is going to be a tool, the tool could suggest assetions

MF: We need to have a tool
... Matt has looked into making a tool, but it was goign to be complex

JG: There is alot of options with the keyboard commands

MF: Any other issues?

BF: Since we have one new person, can you give an overview of organizations

a/BF/RF/

Overview of the terms

MF: We have a wiki with some of this information

https://github.com/w3c/aria-at/wiki

<rob-fentress> What Michael is working from: https://github.com/w3c/aria-at/wiki/Working-Mode

MF: A test is specifies assertions, with each assertion has a priority ...

https://github.com/w3c/aria-at/wiki/Working-Mode

Reviewing definitions in the wiki page

<michael_fairchild> https://w3c.github.io/aria-at/tests/checkbox/test-01-navigate-to-unchecked-checkbox-reading.html?at=jaws

Reviewing the test runner

<Juliette_McShane> +`1

Introductions

MF: I work at Deque, and I am supporting the vision of Matt king
... Matt works for Facebook
... I was working on a similar project, but it was not sustainable, this project can do it better

BF: I work for Virginia Tech, I am volunteering to test, I support best practices at VT, ....

JM: I am director of ..., recently joined the W3C, trying to figure out what working groups to see where are best fit iit is, since we are a service provider and focus on compliance

MF: Matt has secured funding to build the tests and the test harness, so we need people to actually run the test

<Jemma_> I have to go for another meeting. My name is Jaeun Jemma Ku. I am working for University of Illinois and help ARIA-APG as co-facilitator with Matt King.

JM Access to Online, history of the company, works with training prisoners in accessibility evaluation, so we have alot of people

HR: I am part of the IT accessibility team at University of Washington, was at Illinois and worked with Joe and Robert too
... My primary job is to make systems at Washington accessible, working this for many years, and my students help too

Mikey: Help Hadi

JH: I am senior accessibility specialist at Paciello Grpup, I proposed a community group similar to this a few years ago, but this proposal is more viable
... I want real world implementation information, what really works

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/09/10 19:56:17 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Default Present: JoeHumbert, jongund, rob-fentress, michael_fairchild, Juliette_McShane, Jesdaigle
Present: JoeHumbert jongund rob-fentress michael_fairchild Juliette_McShane Jesdaigle Jemma_
Found Scribe: jongund
Inferring ScribeNick: jongund

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


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


[End of scribe.perl diagnostic output]