<Matt_King> agenda board: https://github.com/w3c/aria-at/projects/3
<michael_fairchild> scribe: michael_fairchild
Matt_King: presentation proposals
for CSUN are coming up. I'll submit a talk for this
project.
... We could include other members and contributors in our
talk
michael_fairchild: We could also submit to Deque's axe-con
https://www.deque.com/blog/announcing-axe-con-digital-accessibility-conference/
Matt_King: Bocoup is working on
the infrastructure. The data structure needs to be changed
slightly - this is the data model of the app, not the
tests.
... This is the data model for the data that is collected
during testing
... more work is being done which will allow better re-running
a test, and we will also store which version of the test was
run
... we are also working on a better way to preview draft
versions of tests
<Matt_King> scribe: matt_king
mf: nothing new since last meeting
workstream focused on making prototype test with a screen reader
Work should start in late oct or early nov, based on bocoup schedule
mk: any more info on which screen reader?
mf: not yet
will loop back with bocoup
<michael_fairchild> scribe: michael_fairchild
Matt_King: we will be working
with Prime Access Consulting
... I'm in the process of getting the SoW finished
... They will create tests for 6-12 patterns by the end of the
year
... They should start ramping up in the first week of October.
I'll help them get familiar with the ARIA-AT project and
code.
... Then they will work in 3 week sprints
... we can still have CG members contribute tests. Prime Access
Consulting does not need to be the only people working on
it.
Matt_King: there is a project board for writing tests
project board: https://github.com/w3c/aria-at/projects/1
Matt_King: I was thinking of
reducing the scope of what is on this project board to just the
first few columns
... (lists the columns)
... I'd like to reduce the columns and end at 'ready for
testing'
... I don't want the completion of Prime Access Consulting's
deliverable to have too many external dependencies
michael_fairchild: I think that's fine
Matt_King: should we put the tests in the ARIA-AT tool so that they can be reviewed?
michael_fairchild: would they be listed as 'draft'?
Matt_King: yes
... we could add a column to the test CSV for status
issue created for this: https://github.com/w3c/aria-at/issues/300
Matt_King: I'll make these changes to the project board
https://github.com/w3c/aria-at/issues/295
Matt_King: I gave a lot of
thought to complexity. It may raise the barrier to entry to
writing tests, but if we are hiring folks to write tests then a
barrier to entry is not a huge problem
... If done well, I think this could simplify test
writing
... Are there certain kinds of assertions that can be used
across multiple roles?
... for example, conveying the name of something
... some assertions might need to be tied to a specific role or
property
... has anyone looked at our current tests and assertions to
see what is reusable?
... I haven't looked at this project in particular, but I've
done this with success at a11ysupport.io
Hadi: I also haven't looked, but I'm confident that there is a lot of opportunity for reuse here. However, if our tests are experts at testing, consistent language isn't as helpful, but still very helpful. The question is the work justifiable?
Matt_King: I imagine that we
would start with another CSV file. A column for attribute,
another for the assertion.
... maybe more columns
... I think as we are writing tests, we would make assertions
up as we go, and refine as we go
Hadi: are these assertions atomic? For example, the name of the control. Or the state of the control?
Matt_King: yes
... but there might be multiple tokens for each attribute.
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) Present: Jemma michael_fairchild juliette_mcshane Found Scribe: michael_fairchild Inferring ScribeNick: michael_fairchild Found Scribe: matt_king Inferring ScribeNick: Matt_King Found Scribe: michael_fairchild Inferring ScribeNick: michael_fairchild Scribes: michael_fairchild, matt_king ScribeNicks: michael_fairchild, Matt_King 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]