<joanie> agenda: this
<joanie> agenda: be done
<scribe> Scribe: Stefan
Next Item: Face-to-face week of 29 April - 5 May: Which days and agenda?
Joanie: 3 day meeting - which three days?
Matt: Tu-Thursday
Bryan: better towards end of the
week
... better begin of the week
Michael: no conflicts
STefan: cannot make it to the meeting due to travel restrictions
Joanie: GG of FS may come to the
conference
... would be good to have one from screen reader vendors at the
conference
... we need focus on roles again instead of accName
... role parity I mean
Matt: there are topics related:
semantics of inline vs. block
... also affects css
... accName issues have overlappable parity
Joanie: name calculation can come
as 1.2 topic
... ther are broader name calculation issues potentially
Matt: meaty technical stuff is
not helped when talking about doc structure
... must have super strong focus on meaty tech issues
... otherwise there will be negative consequences
Joanie: there is also
implemenation parity
... I see danger in different implementations ..
inconsistencies
Stefan: also inconsitencies on AT side
Matt: tis is a F2F topic
Joanie: may be multiple reasons
for that, lack of need, not imülemented yet and so on
... we get so much stuff regarding the mapping already, we need
to start there
... for the notes, this is the "not mapped vs. mapped"
problem
Matt: we shoud definitly say
which roles, properties etc. we think screen readers shouöd
rener directly
... meaning its unclear to end users
... aria-controls is one of this examples
... we need informative way and not normative way indicating
how to annouce this
... we have a project for this underway
Joanie: there will be a wiki page for that
<joanie> Specs: https://www.w3.org/TR/graphics-aria-1.0/ and https://www.w3.org/TR/graphics-aam-1.0/
Joanie: date is 02. of february
<joanie> https://w3c.github.io/test-results/graphics-aam/
Joanie: current test results are
here
... for FF it is complete, Windows, MacOS/Linux also
... MS will do this by early may
... I would like to enter CR
... any commments before I put out CFC?
... Michael?
Michael: we didn't recieve any
comments
... we need affirmative feedback from the WG
Joanie: for graphics I will send out a CFC
<joanie> https://www.w3.org/wiki/AccName_1.1_Testable_Statements
Joanie: once again Bryan is hero
of the week
... we also need to handle the missing test cases
... we added them to the wiki
... we need to close this part of process, any gaps
still?
... we have other topics to discuss the details
... so the impression is we have complete test coverage
<joanie> https://github.com/w3c/accname/issues
Matt: better assigning them to milestones
Joanie: we can also use labels
Michael: milestone show % complete
Matt: used milestones for changelog
Joanie: I am good with milestones such as for creation of accName
Matt: 2 to address: issue 1 and 5
<joanie> https://github.com/w3c/accname/issues/1
Matt: 1 is more complex,
potentially editorial
... exaple in spec may cause confusion
... may be we need a change request for this
... ia mwilling to spend a little time on it
<joanie> https://github.com/w3c/accname/issues/5
Matt: also for issue 5 ..
... what does otherwise mean here .. answer was all of
them
... is there is general consensus? THen I can take subsequent
actions
<joanie> https://github.com/w3c/accname/issues/3
<joanie> https://github.com/w3c/accname/issues/4
Matt: seems to be duplicate
issues
... will be F2F topics
<joanie> https://github.com/w3c/accname/issues/6
<joanie> The handling of multiple label elements on one form field is unclear
Matt: issue 6 and 7 ... actually
related to issue 2
... is accName spec capturing anything related to naming?
<joanie> https://github.com/w3c/accname/issues/7
Matt: issue 7 there is some
editorial complexity here
... hard area beacuse there are inconsistent
implementations
... there are still pitfalls in the issues
Joanie: issue 1 I'm turning this
into a v
... issue 1 I'm turning this into a test case
Matt: makes sense
<joanie> https://w3c.github.io/test-results/accname/
<joanie> https://www.w3.org/wiki/AccName_1.1_Testable_Statements#Name_checkbox-label-embedded-menu
Bryan: what's supposed to return is not supported it seems
<joanie> <input type="checkbox" id="test" />
<joanie> <label for="test">Flash the screen
<joanie> <span role="menu">
<joanie> <span role="menuitem" aria-selected="true">1</span>
<joanie> <span role="menuitem" hidden>2</span>
<joanie> <span role="menuitem" hidden>3</span>
<joanie> </span>
<joanie> times.
<joanie> </label>
Joanie: (discussing the
example)
... Aria 1.0 example is incorrect based on what the algorithm
says
<joanie> https://www.w3.org/wiki/AccName_1.1_Testable_Statements#Name_checkbox-label-embedded-menu
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Present: Stefan Joanmarie_Diggs Irfan Irfan_Ali matt_king janina Regrets: James_Nurthen Jon_Gunderson Found Scribe: Stefan Inferring ScribeNick: Stefan Found Date: 01 Mar 2018 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]