<scribe> scribe: Irfan
<scribe> Chair: James
Quick Introduction
jn: two issues but nothing to triage
jn: we had a meeting but Brian couldnt make it to discuss accname and white space
<pkra> +1
JC from apple have some conflicts. we are going to do part3 next week to discuss more.
jn: web component and how the accname works as a slot. we do not account for accessible name calculation
peter: this is more like child node API getting into slot. but it is still a child
it is in assigned node.
scott: want to give it another peek. Last time I checked, it didnt seem weird. need to do more research if you assigned me the issue.
jn: not sure how easily we will be able to make changes.
it seems browsers are doing logical things but terminology in spec doesn't match. Its unclear but reasonable issue
scott: will take another look
jn: I think it is just algorithm is too complex.
https://www.w3.org/2020/09/03-aria-minutes.html#item06
issue # 746 Need an aria-interactive attribute to indicate a control has its own keyboard handlers
mk: seems complicated. I wrote text for aria interactive for aria1.1. if the goal is something to wide review for January, it is out of the reach. we should push it to 1.4
jn: moving it to 1.4
issue # 747 Add author MUST that if you define setsize you MUST also define posinset.
jn: it is related to validator.
sounds something easy for 1.3. assigning it to msumner
... issue:748 Definition of "owned" is not strict enough;
should actually be direct children, not any descendant
we need to sort it out in 1.3.
jn: my previous comment on this issue, Descendant elements of the element referenced with aria-owns where each ancestor node between the element referenced with aria-owns and the owned element has a role of none or generic
scott: there needs to be a concept of direct ownership vs descanted owner
mk: direct ownership feels like there is it is directly owned or contained. It could be intervening thing. For example, a menu and menu item
generic should work
jn: thats the part which requires implementation.
mk: we don't want to force people to add it explicitly
scott: only issue is in HTML you cant have div within unordered list.
mk: is there any possibilities that may change in HTML
it has implications
ms: been thinking about getting deep down to this issue. pls assign this to me and I will look into it
scott: feel free to ping me. I may have some additional thought
jn: next issue # 750 Creation of resource definitions for localized state information
jd: dont make sense role description as slice in pizza slice example
mk: we need aria role description
jn: Irfan will follow up on this.
as of now moving it to 1.4
... issue# 751 Expand value types for aria-invalid
... issue # 758 Add role="image" as synonym for role="img"
scott: will take this one.
jn: issue #760 Add informative note that authors should not rely on rowgroup mappings on all platforms and therefore should not use additional attributes on an element with role rowgroup.
jd: not looking at that issue. problem with rowgroup existence. for ex. tabindex should be in a11y tree
jn: I should be asisgn it to JC
and move it to 1.4
... #762 Bringing VoiceOver "actions" to the web
... not sure if AOM solution is sufficient. this gets into
making hover. essentially we need an alternative of hover in
a11y API which could help us get there.
we should put it on agenda for deep diving.
it is at risk for 1.3
jn: #767 Consider adding context attribute through which ATs could ensure correct presentation of content
mk: create another issue in pronunciation github and link to this issue. if there is a partial solution then we still need to track it here.
jn: # 779 Consider moving
normative, NON-mapping content from Core AAM to ARIA
... #798 Clarify if aria-selected & aria-checked are
required on roles 'treeitem' & ('menuitemcheckbox',
'menuitemradio') respectively
question is whether an aria selected is an required attr on tree items?
answer is yes.
jn: aria-checked is not required
mk: we do aria selected either true or false. false should not be required as default value
we do not know if it is selectable
mk: this issue should be fixed in 1.3
jn: assigned to Matt
... #812 Allowed structures for spinbutton widgets is
ambiguous
fixed and should be closed
This is scribe.perl Revision of Date 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/note/node/ Succeeded: s/fixe/fixed/ Present: Irfan Joanmarie_Diggs pkra StefanS jamesn Scott_O Matt_King Found Scribe: Irfan Inferring ScribeNick: Irfan 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.)[End of scribe.perl diagnostic output]