<joanie> agenda: this
<joanie> agenda: be done
<scribe> Scribe: Stefan
8 new issues
first one: gridcell 1155
<jamesn> https://github.com/w3c/aria/issues/1155
James: this should be
changed
... should we believe aaron hereΓ
... clarification needed in spec?
aaon: pr for core aam would be good
James: can you do it?
... should be moved to core aam spec?
joanie: ok
<carmacleod> https://github.com/w3c/aria/issues/1153
next: 1153
<jamesn> https://github.com/w3c/aria/issues/1153
James: i need more approvals for that
<jamesn> https://github.com/w3c/aria/pull/1154
James.. any objections?
<carmacleod> https://github.com/w3c/aria/issues/1152
MichaelC: I take a look and approve if ok
James: please look at it .. 1.3
issue perhaps
... my interpretation is "it depends on situation"
<carmacleod> https://github.com/w3c/aria/issues/1151
James: i agree with that, 1.2 or
1.3 address?
... we need to test for it instead only implying it
joanie: if it passes I am ok with it
James: in case of no pass, move to 1.3
<carmacleod> https://github.com/w3c/aria/issues/1150
James: this is written for DOM 4
joanie: ask him for annother PR?
Matt: talking about decendants
means DOM descendants in the past
... eg grid with custom element .. can never shadow DOM .. does
that mean shadow dom is separate tree or descendant of grid
james: this is probably not the
question here
... we need to say what we mean with "descendant"
... can we do in 1.2? claifying?
... i hope we can find somebody
joanie: somebody could triage it
James: any volunteers?
<pkra> 94 " descendant"
<Jemma> How about asking Wilco to help us to give more info about different trees?
joanie: there are not many descendat variants
<Jemma> definition of each trees, " light DOM tree, shadow DOM trees, the flat tree, and the accessibility tree"
scot has self-assigned him to this
james: let's start with desendant and expand from there
Matt: there are two ways to own, we need revise def for owned by
Scott O'Hara has self-assigned to this
<carmacleod> Need approving reviewers for: https://github.com/w3c/aria/pull/1149
John: I can review
Jon Gunderson reviewer
james: any objections?
james, none, fine we can still mo it in master
james: no comments
<carmacleod> https://github.com/w3c/aria/pull/1135
<jamesn> https://github.com/w3c/aria/pull/1135
james: no discussions here
<jamesn> https://pr-preview.s3.amazonaws.com/w3c/aria/pull/1135.html#comment
james: are there controversial partsΓ
aaron: relationship to other
content, relations of comments to comments
... you can use aria-level for this
jon: are comments self-commenting?
aaron: we are not too specific about that
joanie: we can do this in authoring practices
aaron: nobody had spec. features in mind
jon: what does screen reader do with this?
aaron: its in aria-annotations explainer and brainstroming document
<aaronlev> https://github.com/aleventhal/aria-annotations
<aaronlev> https://docs.google.com/document/d/1DYrsHDk6Y9071A1fRg8g8NZ_DtGYraX5BcVY-taBzMQ/edit?ts=5e1cbd7d#
aaron: we want to be able to
navigate by comment
... navigate comment tree in general
... like Jaws dialog for articles
<Jemma> https://github.com/aleventhal/aria-annotations#example----comments-on-a-specific-piece-of-content
aaron: aria-details may point to the comment
jon: it seems to be reverse computed
aaaron: detail reverse relationship is computed by the browser
aaron: multiple things can point
to same comment
... screen reader can store cell pointers
<tzviya> https://www.w3.org/TR/annotation-model/
aaron: diff between footnotes and comment are that comments may bee in a side bar
tzviya: footnotes are part of pub and may not use annotations
aaron: for footnotes use aria-details on footnote number
Scott: is there expectation that
authors use that in blog posts?
... blog post that allows for user comments, should they be
wrapped in comments role?
aaron: yes this is a good idea
james: annotation on entire blog post?
aaron: yes, basically
Sina: is there a grouping methodology?
aaron: for replies rec. is top comment available, use descendant comments
Sina: neither is
approppriate
... how to group siblings
aaron: answer must be in comments section .. wait .. there is no clean way of doing that yet
Sina: it is common to have 500 comments on L1
aaron: we're expection aria-level
to be used
... aria-details can point to any container
Sina: we can have separate comment trees on one page
aaron: we can group them
separately
... regarding efficiency, we will add more collection apis
Matt: grouping thing, for
usecases we have we can do it with roles we have
... is name from prohibiting, why?
aaron: I don't remember
Matt: pertains more to blog than
docs use case
... names would be strongly reccommended in blogs but it is not
required yet
aaron: would nacc name overwrite contents?
Matt: no because provided by author
aaron: have to check, that's error
Matt: we have aria-level but not posinset
aaron: must list as supported properties
Matt: blog use case we can do in
May
... when you add new comment you augment aria-details value of
blog article itself
james: what about spec.content on page?
Matt: we need to ajust language
to account to blog use case
... if entire post is article and descendants may cause
issues
aaron: you can use aria-details to point to something inside of you
james: Matt: can you review it for facebook use case and put comments into PR?
Matt: ok
<Zakim> joanie, you wanted to say something about the name overwriting contents
james: until next week would be perfect
joanie: screen reader sometimes
ignore name for containers
... hope that does not happen here
... for comment
Matt: articles, regions support
names
... and content is separated from that, they are more than just
text containers
... should for comments the same as for articles
... extra hotkeys for comments in screen readers, why?
Sina: we need them
Matt: footnotes and articles and
comments are different roles
... it will have authoring practices when this comes out
jon: thats a parallel labelling system
<pkra> can you hear me?
<pkra> damn it webex.
<pkra> nevermind thn.
<jamesn> https://github.com/w3c/aria/pull/923
<pkra> Not really.
<pkra> :(
<pkra> It's complicated.
<pkra> sorry.
<Matt_King> no, it should not be part of name calc
james: should it be part of labelling calculation?
<pkra> I think "no"
<pkra> but there's something to talk about.
<pkra> both.
james: agenda for next week
on* agenda
<pkra> thanks.
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/ffotnotes/footnotes/ Succeeded: s/(unknown)/Sina:/g Succeeded: s/(unknon) == Sina// Succeeded: s/posinst/posinset/ Succeeded: s/propertuies/properties/ Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Present: Joanmarie_Diggs Stefan_Schnabel jamesn harris janina tzviya MichaelC jongund Irfan pkra carmacleod Jemma CurtBellew scottohara Matt_King Regrets: Mark_McCarthy MarkMcCarthy Found Scribe: Stefan Inferring ScribeNick: Stefan Found Date: 16 Jan 2020 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]