<scribe> scribe: Irfan

<scribe> Chair: James Nurthen

New Issue Triage

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

<jamesn> https://github.com/w3c/aria/issues/913

jn: it sounds like it is useful but dont see on high priority. anyone has any opinion?
... how urgent is this, Melanie?

mr: not very urgent. its just an idea

<Devarshi> devarshi+

mr: use case- user goes to aria specs t know which roles is needed.

mk: we have an open issue related to making sure that every role covered. we would have a link to related section in APG.
... before w ego live in 1.2 we will close that issue. you might want to link his issue with the one

jn: I dont think we need to put it in 1.2 milestone.

mr: fine by me

jn: anyone objects?

jd: another possible solution address this issue is, HTML AAM is easy t read to people. once we get 1.2 out and HTML AAM depending upon it rather than 1.1. there will be a ready to go table for authors.
... like SVG aam. that would be another way to tackle this problem

JN: we could use that information

F2F Updates

<jamesn> https://www.w3.org/WAI/ARIA/wiki/Meetings/F2F_Spring_2019

jn: registration page is open. please register and announce who is joining F2F.

Need cite role

<jamesn> https://github.com/w3c/aria/issues/873

jn: this is the need for cite role

<jamesn> https://github.com/w3c/aria/issues/873#issuecomment-466109761

cite role

<jamesn> GitHub: https://github.com/w3c/aria/issues/873

<Zakim> joanie, you wanted to point out that HTML-AAM has not mapped for all platforms except macOS which makes it a AXGroup

mk: there are decsion about wether there are not relative accessibility semantic. Only question: weather or not this has any relevance to annotation work. it is not going to rendered by AT

jd: we add a role then adding a role, mapping would be not mapped.

mk: agree

<MarkMcCarthy> +1

<melanierichards> +1

jn: we made a decision that cite is going to be generic

Issue 876: add draft specification for role label

Label role

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

jn: JG made some updates to this issue

<jongund> https://raw.githack.com/jongund/aria/issue876-role-label/index.html#label

jg: Only the roles checkbox, listbox, meter, radio, searchbox, spinbutton, switch and textbox support name from encapsulation method.

mk: there should not be any implementation complication to check the name calculation.

jn: looking at reference e.x list box
... author override the order

<jamesn> https://raw.githack.com/jongund/aria/issue876-role-label/index.html#namecalculation

jn: do we need to come up with a term other than two words

mk: there is a complication here. the way author is define right now, it includes the encapsulation.
... aria encapsulation would have to be different than authors.

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

jn: I see everything that supports encapsulation, also supports author

mk: role label doesn't have any affect on a11y tree. right now author includes encapsulation which is fine.

jn: its fine what JG done.

<jamesn> need to add to https://raw.githack.com/jongund/aria/issue876-role-label/index.html#namecalculation

mk: its not adding but its rewording

jn: it may requires changing to some other stuff as well.

jg: we have content and authors name from, do you want third thing that talks about encapsulation?
... 5.2.7, we need to add a definition of encapsulation

mk: i wish it would have been attribute
... content comes from author so its okay

jn: more comments?
... we will come back to this if anything else to be discussed

No mention of aria-placeholder in name/description calculation algorithm

placeholder

<jamesn> https://github.com/w3c/accname/issues/17

stefan: not clear which calculation is taking to consideration. we should be more clear here

jn: dont understand

stefan: aria-placeholder- what are your intentions to do here?

<bgaraventa1979> +q

stefan: best practice on web. if you put an accessible description as a fallback, its a good idea?

bg: as a fall back, if we are doing with title, if nothing before that would appear then adding a placeholder a good idea. otherwise placeholder technically would be in added in description
... title is hire up in the tree

jn: our plan was would be we would be make an accessible name and description calculation as placeholder
... is that correct?
... if people have no objection doing that, then we shoud agree that we are going to do that. we will take the issue again after pull request. is that okay part of action.

jg: i have reservation making placeholder as accessible description

jn: place-holder is already in accessible name

jg: I will file a bug

mr: there are some case where placeholder is an idea of providing an accessible name

mk: for authors who wish to create a good experience, these techniques dont protect.

jg: i am worried about validators
... thats the way lot of developers work.

mk: what we have done in acs names back, that certain steps in algorithm are fall back steps.
... its not just an ac name issue but HTML aam issue. these are fall back vs intentional label
... code is parsable and readable and valid but its not necessary good code.

jn: we are not going to change validation.
... sounds like aria practicing issue

mk: this will absolutely covered in APG. it should not effect the html validator

jn: lets not worry about that

<mck> +1 for accname to align with html-aam

<Stefan> +1

<joanie> +1 to aligned

jn: do we have agreement, acc name calculation is similar to native code? do we want to do it.

<MarkMcCarthy> +1 to align

mk: its better to specs to align
... valid code is not always good code

jn: BG, can you get that into acc name? issue is open.

mk: if you have a valid name and not description that idea is placeholder goes into the description

stefan: example would help

jn: we want parity and not diversion.
... I dont think we can come up with any conclusion on this.

need role for time element

<jamesn> https://github.com/w3c/aria/issues/878

<melanierichards> https://github.com/w3c/aria/pull/895

<jamesn> GitHub: https://github.com/w3c/aria/issues/878

mr: we reviewed the need role for time element.
... there is an added not about some potential aria day time property

<melanierichards> https://github.com/w3c/aria/issues/878

mr: Added an author should to match the content expectations of HTML. Should this really be a SHOULD, since that'll generate implications for compliance checkers, or should we change to a gentler suggestion? I don't believe we got formal resolution on this but we can review the next call this comes up.
... also removed name from content.

jn: any comment on pull request? are we ready to merge?

mk: having hard time with editor drafts. all the headings are gone.
... in the definition, shouldn't it be an element that represents specific point of time. we dont always refer to the super class.
... adding a super class something like phrase. I'd rather call it an element

jn: we have definition of an element.
... please take a look into the draft and make your comments

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/who is joining CSUN./who is joining F2F./
Succeeded: s/nly/Only/
Succeeded: s/>radio/radio/
Succeeded: s/godo/good/
Present: jamesn Irfan_Ali MarkMcCarthy MichaelC Joanmarie_Diggs HarrisSchneiderman Stefan melanierichards Bryan_Garaventa jongund Matt_King CurtBellew matt-king JaeunJemmaKu carmacleod
No ScribeNick specified.  Guessing ScribeNick: irfan_ali
Found Scribe: Irfan
Found Date: 07 Mar 2019
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.)