<Scott_O> present Scott_O'Hara
<Scott_O> scribe: Scott_O
https://github.com/w3c/aria/issues/1063
which aria attributes apply to descendant elements?
JN: let's do 1.3
<pkra> +1
https://github.com/w3c/aria/issues/1074
pr in for this
https://github.com/w3c/aria/issues/1076
consider deprecating role=directory
<pkra> +1
not a lot of time left for 1.2, but if we want to do this we should get it in before 1.3
JN: we will go over list in more detail later
<jamesn> https://github.com/w3c/aria/milestone/10
JN: for 1.2 milestone we have 74
open, 79 closed
... many of which have PRs open (26)
<jamesn> https://github.com/w3c/aria/pulls
JN: we need to get these reviewed
and merged before next week
... pick at least one or two issues and work out what we should
do with them.
... make PRs to resolve, or comments to indicate why not, or if
they should be moved to 1.3.
MK: there are a good number that are combo boxes, and still need to work through those
JN: if anything is unassigned,
please assign yourself so we can work through them.
... will send out an email of PRs to review. Getting approvals
is ideal.
https://github.com/w3c/aria/pull/924
PK: made some updates to markup and wording. Add more warning to the note and indicate the importance of authors to use correctly.
JM: will get James Craig to review as well
JN: going to remove the WIP label. if we get approval, going to merge it unless we get other comments
https://github.com/w3c/aria/issues/1056
JN: this came up at TPAC. how are
we going to work with extension specs?
... example dpub can have doc-biblioentry in a list. but ARIA
doesnt' have that
JM: I think we need for dpub to do an updated version. in the future we may need to update this. but, for now, we should ask dpub to update their spec.
<carmacleod> scribe: carmacleod
<jamesn> w+
pkra: in general, an extension should not touch just things that are just children
jamesn: I believe what happened is that biblioentrylist existed initially, but it was cut when they tried to reduce the number of roles
pkra: once the annotation module gets further along, we should get together to look at what extension modules should do
joanie: trying to refresh memory,
looking at past emails
... they could deprecate biblioentryitem
... will follow up on this
james: Matt suggests we wait until Bryan is back
mck: there are related PRs that we may want to flag as targeting 1.3
<Scott_O> scribe: Scott_O
<jamesn> https://github.com/w3c/aria/issues/999
JN: do we want to get this into 1.2, or too close?
SO: added aria=haspopup to tab states and properties
JN: what do we need to do to make this into this milestone?
MK: i think we should make this a priority
JN: is it ready to merge? it's been reviewed, and people have been looking at it. is it ok to merge if we dont' get negative comments on it?
MK: I think we need to get positive reviews
SO: I'll do review as well
CM: me too
MK: I'll review
JN: anyone can review as well. and we should determine what testing and authoring practices need to do
MK: at least for this change is make sure we're solid on changing just these four properties listed properties, and not adding anymore.
JN: yes. let's just focus on is
this change going to make the spec better, and not look to
resolve everything for global states and properties
... i'm not convinced there's anything to do in practices
except for usages where they are no longer allowed
MK: aria-invalid,
aria-errormessage, and aria-disabled should all be ok
... and shouldn't result in any APG changes.
JN: joanie, can we do this in 1.2?
JM: let's aim for yes
https://github.com/w3c/core-aam/issues/49
JN: this is a core aam thing
JM: just cause that's where it lives right now
<jamesn> https://github.com/w3c/core-aam/issues/49
<jamesn> https://github.com/w3c/aria/pull/1070
JN: i removed all mentions of
taxonomy files, RDF, and similar refs
... may well just be editorial, but still worth a few people to
review
<MichaelC> https://www.w3.org/WAI/ARIA/schemata/
JN: please review
make form accessible name required as true
make form landmarks similar to regions
MK: for this one we would need to update APG.
JN: this would make parity with HTML AAM as well
<joanie> Yes
JN: we need testing for this as well?
<joanie> It needs Core-AAM
<joanie> It will then need testing
JM: it is going to need to be tested, and a core aam change
<pkra> bye everyone
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 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: Joanmarie_Diggs, janina, jamesn, pkra, Scott_OHara, MichaelC, Dorothy, harris, carmacleod, Matt_King Present: Joanmarie_Diggs janina jamesn pkra Scott_OHara MichaelC Dorothy harris carmacleod Matt_King Regrets: CurtBellew IrfanAli Found Scribe: Scott_O Inferring ScribeNick: Scott_O Found Scribe: carmacleod Inferring ScribeNick: carmacleod Found Scribe: Scott_O Inferring ScribeNick: Scott_O Scribes: Scott_O, carmacleod ScribeNicks: Scott_O, carmacleod Found Date: 03 Oct 2019 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]