<scribe> scribe: shadi
WF: no objections
... congratulations Aron!
... first review
Aron: thanks for your support
WF: PR #1404
... what is the issue?
JYM: confused streaming and
non-streaming definitions
... definition for non-streaming completely off
... but impacts all rules related to non-streaming
WF: so this can be merged but need fix related issues
CD: need to get it to the
agenda
... will work on non-streaming definition
JYM: maybe be able to have a
quick fix
... for finite duration
WF: updated two days ago
... still going through approval process
... working on the rule with Jey
JYM: two approvals
... PR 1447
AJ: will look into it this
week
... PR merged recently with editorial fixes
... but still outstanding issue
... on aria-required owned elements
<Wilco> https://github.com/w3c/aria/issues/1033
AJ: if HTML elements can be
considered
... need to wait for confirmation before sending response
WF: propose this to apply to all
child elements
... all immediately owned elements
... currently ARIA only considers entire sub-tree
... suggest to remove radio group elements
... because these are quite different
... think there is a fix but need response from ARIA group
AJ: using incorrect HTML in that example
<scribe> ...done on purpose to demonstrate example
WF: yes, that's ok
... need to take date off this one for now
CD: object element has one
approval from JYM
... need more reviews
... PR 1441
<Wilco> https://github.com/act-rules/act-rules.github.io/pull/1441
EPR: can have a look
WF: extend the date by a week?
CD: yes, probably needed
WF: visual elements
... updates on that?
CD: will put in final call
... JYM just approved it
WF: it is already in final call
CD: right, can be merged
... issue to be fixed first
WF: date on that?
... 12th or 19th?
CD: 19th
WF: element with aria-hidden has no focusable content
CD: will need new date too
... read your counter proposal but need to consider
... at least October 12th
WF: forgot the iFrame one
... need to move to October 5th
... auto-complete
AJ: have some questions on the
issues raised
... ask the person to clarify or just close them?
WF: our own issue, so can close them
JYM: issues will automatically close when you merge, if they are referenced
AJ: ok, will leave a comment that
issue has been addressed
... then close them in a week
WF: no need to close them, will close with merge
CD: scrollable element next
WF: awaiting W3C review
CD: takers for the other
ones?
... headers attribute refers to cells in the same table
... issue with inapplicable and passed examples
AJ: can look into it but can't confirm yet
CD: meta-element has no refresh
delay
... also issue with inapplicable examples
... apparently only happen in Firefox
... Wilco seems to be looking at it
[unaimous approval to assign Wilco]
CD: failed example for accessible name
JYM: some browsers stop at that
point, others don't
... specs not very clear on that issue
EPR: browsers not following spec?
JYM: spec not really clear on that
EPR: could go into the accessibility support section
HB: name and shame?
SAZ: https://aria-at.w3.org/
... might help with that
WF: seems to work on Chrome
JYM: depends on versions, issue reported upstream
<Carlos> https://github.com/w3c/accname/issues/72
JYM: taking this one
WF: another accessible name rule
CD: think we already discussed some of this?
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/1248
WF: need to resolve issue 1248
HB: I can take that
... if I get help
WF: will hold your hand, guide you through, and tuck you in!
CD: came up while Jean-Yves was
reviewing device motion rule
... reaction could be shortly paused rather than permamently
disabled
... Success Criterion unclear about this
AJ: I think safe to assume that
disabled means more permanently switched off
... as opposed to temporarily for short period
EPR: yes, agree
<adil_> sorry guys I had some internet issues
SAZ: maybe make the assumption and raise an issue on WCAG 2.2 to provide a definition for "disabled"
JYM: how do you test "disabled"? could have timer to re-enable after a period
AJ: see issue of not being able
to test accurately
... thinking of the 20 hour rule
WF: used 10 minutes for something else
CD: were moving from 10 minutes to 1 minute
WF: might be over-assuming that
stays disabled permanently
... SC does not actually say that
AJ: agree, it is unclear
... yet reasonable assumption
[agreement to use that assumption]
CD: will take that
SAZ: also suggest relaying the issue to AGWG
WF: issues often not responded to
SAZ: still should do
WF: agree
CD: will do
WF: seems we all agree on that
JYM: need to ensure that it is
copied in the rule
... and not lost
... has direct impact on the rule
AJ: help to link to accessibility support section?
AH: how often do such exceptions
occur
... how general are they in the glossary
AJ: refer to specific rule
... but do not mention specific browsers
... so somewhere in between
AH: if generic, then sufficient
in the glossary
... if specific, need to remain in the rule
WF: can just take them out
AJ: agree
CD: leave them in glossary and remove them from injecting in the rule
[agreement]
WF: takes some programming to do but seems we have a solution
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) Default Present: Carlos, shadi, Wilco, adil, Daniel, Jean-Yves, EmmaJ_PR, adil_ Present: Carlos shadi Wilco adil Daniel Jean-Yves EmmaJ_PR adil_ Found Scribe: shadi Inferring ScribeNick: shadi WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth 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: 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]