<jamesn> agendabot, find agenda
<agendabot> jamesn, OK. This may take a minute...
<agendabot> clear agenda
<scribe> scribe: pkra
jnurthen: meeting next week,
incl. deep dive before
... last meeting of year.
... and then Jan 7 2021
... #1366 - is this 1.3?
carolyn: yes.
jnurthen: no new PRs.
... next week deep dive topic: braille pattern input
... any disagreement?
... => all clear.
jnurthen: PR 1213
carolyn: I've addressed the comments.
jnurthen: great, will ask
re-reviews from Aaron, myself.
... will try to merge next week
jnurthen: @all is this the right
order?
... we have required context role and required owned
... do we need this? Seem like "yes".
curtis: so they can be in group if context is ok?
jnurthen: yes. That's how it's really been. We're not really adding anything.
carolyn: it clarifies. I think
people look there so it's good clarification.
... I'd like more review.
jnurthen: I'm wondering if we need more in other sections, e.g., to explain the arrow here.
carolyn: that sounds good. I will try to do it.
jnurthen: maybe as a separate issue/PR.
carolyn: will create issue.
jnurthen: not sure if the order / direction of arrows is right.
carolyn: maybe that's right.
sina: could it be > rather than an arrow?
carolyn: the abbreviation is "containing"
curtis: maybe just use the word instead?
jnurthen: if it's not a problem, then maybe leave it as we haven't had complaints in the past.
https://pr-preview.s3.amazonaws.com/w3c/aria/pull/1359.html#option
sina: I also see just right arrow, abbr not coming through.
jnurthen: ok, we should fix.
sina: just add sr-only text.
jnurthen: maybe the word is
better then.
... going back to order. I'd rather like group <=
listbox
mattking: I agree, from screenreader point of view.
pkra: could we add the actual role?
sina: seconding matt's comment.
carolyn: so I'll flip it and add name.
sina: sr-only containing with aria-hidden on arrow
jnurthen: but abbr is
standard.
... move that other part into editorial PR
mattking: accepted some
suggestions but want to change some more. responded to Sina's
comment, but admittedly not too helpful.
... I feel like these exceptions are rare. We could make a
separate sentence.
sina: even "generally should not" would help. people reading this might not differentiate enough.
mattking: if we add list of exceptions, do people here feel it's just as strong?
carolyn: might sound like they should use them in those rare circumstances.
sina: and they should - in those cases. Otherwise it doesn't work.
mattking: I just want "extremely rare" there.
sina: "rare" seems enough but
ok.
... and it's fewer words.
mattking: ok, I'll work it in.
jnurthen: please add comment that people should speak up and that we plan to merge.
mattking: sarah ok'ed early. james approved.
jnurthen: yes, but let's give people one more note.
zakim: next item
jnurthen: one more reviewer please.
mattking: I thought I had.
jnurthen: you had but there was a change.
mattking: on it...
jnurthen: we discussed it with
Michael yesterday.
... he's happy to do it.
michael: just one off now, then automate.
jnurthen: looks like we can do that.
pkra: I'll look into that.
jnurthen: we should avoid adding
confusion, e.g., for dpub aria
... just keep it for releases.
pkra: is the json manually generated?
<jamesn> https://raw.githack.com/w3c/aria/2020-09_CR/index.html#respec-offender-error-no-matching-dfn-found
jnurthen: yes but in the respec
can export the json.
... in the respec menu button
sina: just a github action then?
pkra: yes!
jnurthen: https://github.com/w3c/aria/pull/1354
carolyn: I added pkra but it's not really related.
jnurthen: any takers?
sina: I'll do it.
jnurthen: https://github.com/w3c/aria/pull/1332
... will add it to agenda for next time.
... https://github.com/w3c/aria/pull/1315
carolyn: UAs said no. But there are still inconsistencies that are worth fixing.
jnurthen: will convert to draft
then.
... https://github.com/w3c/aria/pull/1298
... needs reviewers.
... https://github.com/w3c/aria/pull/1213
carolyn: I addressed the comments.
jnurthen: more reviewers?
curtis: I'll do it.
jnurthen: https://github.com/w3c/aria/pull/1188
mattking: wasn' this superceded?
jnurthen: good point. I'll ping
Aaron.
... https://github.com/w3c/aria/pull/1162
... we're looking at that.
... https://github.com/w3c/aria/pull/1147
... should this be merged?
... merged.
... https://github.com/w3c/aria/pull/1127
... this is will need careful checking of each change.
mattking: on PR 1340, should "however" be "and"? "and if they do, they must"...
carolyn: let's continue.
... some other time.
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: jamesn, pkra, carmacleod, MarkMccarthy, Joanmarie_Diggs, harris_, CurtBellew, StefanS Present: jamesn pkra carmacleod MarkMccarthy Joanmarie_Diggs harris_ CurtBellew StefanS Matt_King Regrets: MelanieSumner IsabelHoldsworth JamesCraig SarahHigley Found Scribe: pkra Inferring ScribeNick: pkra Agenda: https://lists.w3.org/Archives/Public/public-aria/2020Dec/0017.html 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: 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]