<dbass> Dorothy Bass
<dbass> i'll be quiet
<scribe> scribe: carmacleod
jamesn: 12 issues - triage
quickly
... combobox issues 1.2 milestone (and assigned to mck), most
others 1.3
<Jemma> https://github.com/w3c/aria/issues/1178
<Stefan> +present Stefan_Schnabel
<jamesn> https://github.com/w3c/aria/issues/1056
jamesn: extension specs like dpub
aria have roles that inherit from aria roles
... for example role doc-biblioentry inherits from list
<tzviya> here is the issue filed for dpub-aria https://github.com/w3c/dpub-aria/issues/15
<aaronlev> to clarify, it inherits from listitem, not list, i think
mck: the extension spec needs
biblioentry to have a required context role
... main purpose of our ontology was for states and
properties
... as opposed to "typing" the element itself
aaronlev: which is unfortunate
mck: but maybe we could rearrange things
tzviya: if I need to create another role called doc-biblioentrylist, there's no value to aria
mck: and it's another role for authors
jamesn: spitballing, what if we rename the terms "subclass" and "superclass" to something else, and then allow extensions to subclass
<Zakim> joanie, you wanted to ask if the role is needed (if it's a list item in a list in a bibliiography, isn't it a biblioentry list?)
tzviya: I think it affects more than biblioentry - footnote, and a few others
jamesn: instead of removing these 4 states/properties from globals, just "deprecate" them from globals, and remove them later
<MarkMccarthy> https://github.com/w3c/aria/issues/1164
jamesn: i.e. keep in globals
list, add "(deprecated from globals)" in inherited list
... allows validators to flag
... Wilco gave example of aria-disabled on div being propagated
to descendants
... personally, I support trying to do this
scott: would like to inform
authors that they could put role group on the div, and that
would be valid
... are we doing this just to save this one example
jamesn: would leave it deprecated until possibly 1.4
mck: so, we allow aria-disabled on group, does it propagate to all descendants?
aaronlev: only focusable, I believe. we don't want it on things that don't support it - that would cause confusion
jamesn: anyone object to going down this path of deprecating first?
mck: we will have to add some prose to the definition of aria-disabled describing this
jamesn: I've assigned it to myself
<jamesn> https://github.com/w3c/aria/pull/1135
aaronlev: it might be nice to tell authors to use specific roles if they are grouping comments
mck: lots of roles - table, list,
region roles - could be used to group comments
... algorithm for screen readers could be "if aria-details
points to [this set of roles] then look inside for
comments"
jamesn: can we come up with 2 or 3 roles that would cover all of the use cases?
mck: so if aria-details is pointing to anything else, is it a validity problem?
jamesn: it's only so the screen reader can determine whether or not the details contains comments
mck: what kind of requirement is this? authors should? must?
aaronlev: I don't think it should be more than a SHOULD
mck: need more than one possible
container. group or region (with name) or complementary (which
may or may not be appropriate)
... wondering... if you allow group, why not list? The 4 most
natural containers would group, list, region, table
jamesn: if you want a table to be
a landmark, you need to add a region around it
... aaronlev do you have a way forward?
aaronlev: group or region
jamesn: need another approving reviewer
mck: I'll look at it this week
<jamesn> https://github.com/w3c/aria/issues/1117
<aaronlev> gotta run, bye all
<Stefan> +q
https://github.com/w3c/aria/issues/1117
mck: if we're doing it on paragraph, I don't see why we would do it for listitem
jamesn: what is the difference between name from contents and name prohibited?
<joanie> joanie: I believe in the case of name from contents, the user agents descend the child elements. If those child elements have aria-label (for example) on them, then the displayed text for the list item and the name from the item won't match.
Stefan: often listitems contain a lot of content, and adding an aria-label to them makes it nicer for screen reader users to navigate
jamesn: let's do the non-controversial ones, and save listitem until later
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) Succeeded: s/complimentary/complementary/ Present: jamesn tzviya Joanmarie_Diggs carmacleod MarkMccarthy janina Jemma Stefan_Schnabel Regrets: harrisScheneiderman peterKrautzberger sinaBahram Found Scribe: carmacleod Inferring ScribeNick: carmacleod 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]