Meeting minutes
https://
assigning Scott
https://
Aaron has essentially answered this
I think we can close
Action: James to close #1397
https://
jamesn: Assigning Carolyn
Scott: Assign me as well
carmacleod: Thank-you, Scott!
jamesn: There are a lot of ACCNAME issues
https://
jamesn: Is this editorial?
jcraig: Yes - it's just in a note
https://
jcraig: painful conflicts. may need to cherry-pick
scott: what is needed to finish making inline elements generic? span is not mapping nicely to generic in HTML-AAM
jamesn: maybe we should ttalk about ACCNAME in next week's deep dive
bryan: sounds good
Updated aria-setsize and aria-posinset to clarify usage for authors<https://github.com/w3c/aria/pull/1332 >
ACCNAME
<jamesn> https://
<jamesn> https://
jamesn: people, please add your opinions to these issues
carmacleod: what is the use case? how common is it?
bryan: it happens often. I see it typically where authors want to surround a form field with a label
jamesn: we have it in our component library
jamesn: we need this to be more consumable and understandable so that we can have consistent results across the browser engines
bryan: I think the only way is to have something automated
<jcraig> IIRC, BG is referring to my comment that test-driven development (with WebDriver computedlabel) is the way to move AccName forward.
jamesn: maybe we should codify what the browsers are doing?
bryan: that works well, except when there are discrepancies
<jcraig> WPT includes WebDriver tests
jcraig: webdriver has computedLabel - not all browsers support computedLabel yet. We could fail any that either don't support computedLabel or where the computedLabel doesn't match Accname
<jcraig> Some history: https://
jcraig: would rather have accname tests in Web Platform Tests instead of relying on webdriver
<jcraig> Source of the WPTWebDriver test for computedlabel
mck: maybe some of the ARIA-AT folks from Bocoup could give info on how to add accessors to WPT