<irfan_> scribe: Irfan

New Issue Triage

<irfan_> Scribe: irfan_

<scribe> scribe: irfan

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

jn: remove references to XForms
... any objection?

<pkra> +1

jn: i'd lke to bring it to the group to know if they are okay to remove

all: no objection

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

jn: Clarify if accessible names be calculated based on ancestor/descendant nested shadow DOM

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

jn: its reasonable to address it in 1.2 time frame
... would like to keep it open now
... would like to put 1.2 milestone

PR triage

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

jn: Generalize AccessibilityRole/AriaAttributes IDL

<jamesn> Discuss next week - Generalize AccessibilityRole/AriaAttributes IDL

jn: will put it in agenda for next week to discuss. seems very technical

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

TPAC

jn: please register before fee goes up.
... early birds rate are until 21st June
... hotels are expansive in Fukuoka. and if you are coming to TPAC, please get your registration done asap.

<Jemma> I am coming

Quick status checks

<carmacleod> https://github.com/w3c/aria/wiki/Generic-Role-End-to-End

Generic role and aria-textseparation split

<carmacleod> https://github.com/w3c/aria/wiki/Generic-Role-End-to-End

<pkra> https://github.com/w3c/aria/wiki/Generic-Role-End-to-End#proposed-generic-role

cm: A nameless container element that has no semantic meaning on its own, but can provide accessible states and properties for its descendants.
... aded the information here, so that ppl can see what is gone.

jn: have created a new section in the table that supports and inherits state and property.

mk: where did we have this discussion? by having prohibited... what does that mean?

JN: we are going to leave it as global

mk: this is very intuitive, in the beginning of section 6 where we define different state and property .. we may have section for prohibiting on some place.
... i believe i have scripting working but for some reason I can't find it.

<jamesn> <p>Some <a>states</a> and <a>properties</a> are applicable to all host language <a>elements</a> regardless of whether a <a>role</a> is applied. The following global states and properties are supported by all roles and by all base markup elements unless otherwise prohibited. Any global states and properties which are prohibited on any role will be listed in the Prohibited States and Properties section.</p>

jn: if people are okay with this direction then I can put it into the agenda for next week meeting.

mk: feel little conflicting by the wordings
... general directions are great. we can work on it

cm: nice direction for document. notice that spans are empty.
... this is breaking change.. I want to make sure that in describing section, provide alternative to the people.

<Jemma> https://raw.githack.com/w3c/aria-practices/zcorpan/labelling-describing/aria-practices.html#names_and_descriptions

mk: Brian has a test case related to that. Its part of the calculation for the content of the link.

jn: we do need to workout.. what would break and would not.
... most of the things that people think works, they actually dont work consistently. Testing tool should flag it.

required and supported PRs

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

mr: Move some properties from "required" to "supported" on slider role #946
... Move some properties from "required" to "supported" on slider role

mk: they should see it in the documentation
... in the section that describes the property.
... browser developer have to look on two different places..
... entire table would not be scriptable

jn: role needs to have information available about the value.

mr: its fair

jn: I don't oppose to have a separate table.

mr: fall back table needs to be removed in that case.

<Jemma> https://www.w3.org/TR/wai-aria-1.2/#authorErrorDefaultValuesTable

<Jemma> "User agents MUST NOT expose WAI-ARIA attributes that reference unresolved IDs."

mr: if people can review the changes that I have made would help. there was one comment that out of scope for his.

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

mk: its seems incomplete documentation about min-max

jn: was this broken before. if it was, then moving it to a more generic new issue.

<Jemma> https://raw.githack.com/melanierichards/aria/slider-defaults/index.html#slider

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

mr: going to open a new issue then

jn: i propose to remove them.

I am not oppose to have it in separate table if you want to go this way.

mk: just removing those specific roles
... related to slider
... they should be tied together
... that would including removing a row from this table

jn: this will clean the table and the options that are not required wont be here.
... we can have 949 open

Quick, straw-poll-level discussion:

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

jn: is this ready to merge?
... I ahve addressed the feedback from Carolyn.
... mc, could you please take a look into conformance section which seems messed up?
... conformance section in working draft is messed up.

mc: will look into it

jn: is it good to merge at this moment?

scott: fine by me

<Jemma> merge~

<Jemma> yes

<jamesn> Merge https://github.com/w3c/aria/pull/971 at end of week

jn: will merge it by end of the week.

In-depth discussions

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

jn: Tree Inclusion focus/activedescendant requirements need clarification

mk: just by referencing the language that i put into aria active descendent.. words there could be blended with what was already there.

jn: are you taking about direct descendent or any descendant?

mk: if someone writes wrong div, it is going to create weird a11y tree
... how to distinguish the div which is focusable?

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/role/row/
Present: jamesn pkra Scott_O carmacleod MichaelC irfan_ melanierichards JaEunJemmaKu CurtBellew harris Matt_King
Regrets: JoanmarieDiggs MarkMcCarthy BryanGaraventa
Found Scribe: Irfan
Found Scribe: irfan_
Inferring ScribeNick: irfan_
Found Scribe: irfan
Scribes: Irfan, irfan_
Found Date: 23 May 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.)