<scribe> scribe: carmacleod

<pkra> almost anyway.

<pkra> :)

New Issue Triage 🐞

https://github.com/search?l=&q=is%3Aopen+is%3Aissue+repo%3Aw3c%2Faria+created%3A%3E%3D2020-01-16+repo%3Aw3c%2Faria+repo%3Aw3c%2Faccname+repo%3Aw3c%2Fcore-aam&type=Issues

<Zakim> joanie, you wanted to say not 1.2

https://github.com/w3c/aria/issues/1164

jamesn: need a use case before we would consider this
... it would be a major change to put it back
... does this break something that works today - if so, we should consider it

https://github.com/w3c/aria/issues/1161

https://github.com/w3c/aria/issues/1160

https://github.com/w3c/aria/issues/1159

sina: do we have a definition of hidden that describes 3 types of hidden?

jamesn: need to look at glossary entry - I believe it is defined as "hidden from the accessibility tree"

mck: it is very relevant in APG, but only relevant in the ARIA spec when we talk about "visible"

sina: I'm happy to help

jamesn: need someone to go through all 3 specs and the glossary entry, and make sure all references agree on the definition
... if all places are talking about the same thing, then it's an easier task

carmacleod: Sina and I can work on this together

https://github.com/w3c/aria/issues/1158

jamesn: 1.3

New PR Triage 🎁

<jamesn> https://github.com/search?l=&q=is%3Aopen+is%3Apr+repo%3Aw3c%2Faria+created%3A%3E%3D2020-01-16+repo%3Aw3c%2Faria+repo%3Aw3c%2Faccname+repo%3Aw3c%2Fcore-aam&type=Issues

Remove Ajax: https://github.com/w3c/aria/pull/1165

https://github.com/w3c/aria/pull/1163

jamesn: need reviewers for https://github.com/w3c/aria/issues/700 because that will help fix part of 1163

<Jemma> https://github.com/w3c/aria/pull/799

mck: need to get pull 799 reviewed

jamesn: it needs to be reviewed by implementers

joanie: melanie is on another project - need to ask bogdan
... jamesteh is replacing alexsurkov

<harris> https://github.com/w3c/aria/pull/1162

https://github.com/w3c/aria/pull/1157

jamesn: this is on the agenda

brailleroledescription update ⠗⠕⠇⠑

<harris> https://github.com/w3c/aria/pull/923

<pkra> can you hear me?

https://github.com/w3c/aria/pull/1097

<pkra> i'll retry...

<pkra> calling in...

jamesn: sina will re-review, and once approved, we can put it in

<MarkMccarthy> github: https://github.com/w3c/aria/pull/1097

feat: aria-braillelabel ⠇⠁⠆⠇

<jamesn> https://github.com/w3c/aria/pull/923

pkra: what happens if an element with aria-labelledby references an enement with a braille label?

sina: eventually, we may want to define aria-braillelabelledby

jamesn: this should be rarely used

sina: the one exception where it would be used regularly is something like a math editor

jamesn: we need some use cases so that we don't over engineer this

pkra: I worry about authors needing to duplicate braille label
... all right. then we need to specify that braille label needs to be directly on the element
... I would like to see a use case for aria-labelledby and some future aria-braillelabelledby having a different id

Add comment role 💬

<joanie> joanie: Whatever the consensus is, it needs to be in the ARIA spec for user agents; not just the APG.

https://github.com/w3c/aria/pull/1135

aleventhal: I believe we are waiting on mck's review for comment role

mck: I am reviewing details first

jamesn: I'll add mck to the reviewers for the comment PR

mck: question: there's a part of details where it says "the additional information can be..." and then there's a list
... the "can be" language - we have this list because AT might want to use the roles of elements referenced by aria-details to make it available
... something along those lines
... would prefer other words instead of "can be" - so that AT should? may? provide the information

aleventhal: AT may use this information to present a summary of the details

mck: may use the role of the referenced element to tell the user about the role of the information that is available

aleventhal: just to help user know "do I want to navigate over there"

Add suggestion role 🎩

<jamesn> https://github.com/w3c/aria/pull/1134

aria-live says only use assertive when “interruption is imperative”. Why does aria-errormessage example use it rather than polite 🚨

<Scott_O> https://github.com/w3c/aria/pull/1157

https://github.com/w3c/aria/issues/1139

<pkra> +1 to merge

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/lises/lines/
Present: Joanmarie_Diggs Stefan_Schnabel jamesn harris janina tzviya MichaelC jongund Irfan pkra carmacleod Jemma CurtBellew scottohara Matt_King MarkMccarthy
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: 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.)