<Wilco> https://github.com/w3c/wcag-act/pull/486/files#r500152843
Shadi: minor updates, level 2 heading, during early approval process, would draft be included in (brackets)?
Wilco: doesn't need AG approval
Shadi: once rule is approved by AG, minor updates can happen up to a year later between approval and publishing
Wilco: can happen anytime after approval by task force
Shadi: how does the ACT task force decide? is there a process?
Wilco: discussion on ACT task force call
... clarification would help indicating when the changes occur
... merging, done
<Wilco> https://www.w3.org/2002/09/wbs/93339/ACTScrollableElement/results
Wilco: clarify other ways of scrolling to address Cathy's comment
maryjom: describe other cases where keyboard access is not required
Wilco: scrolling can be controlled via another keyboard method
maryjom: touch as an alternative
trevor: firefox is confusing with tabindex implementation, by default set to -1, but when set explicitly the element is not tab focusable
wilco: this can still cause keyboard accessibility issues
charu: the name implies operable (accessible)
trevor: should we only use horizontal scrolling examples as failures?
wilco: assumptions need to be fixed
maryjom: adding assumption to allow scrolling controlled by other methods
wilco: are these blockers or do we proceed?
trevor: are these minor editorial changes?
wilco: will make changes and bring up at next meeting
wilco: adding editorial change to assumptions
... brought up mapping last week
maryjom: if a rule isn't for conformance against an accessibility requirement, then we shouldn't use ACT task force time to review
trevor: what is missing to apply this where it wasn't before?
wilco: it does cause problems
... mapping to ARIA isn't correct, as it doesn't exclude using other roles
maryjom: using the rule to check that only ARIA 1.1 used is valid, but depends on the rule purpose
... this rule could catch spelling issues
wilco: aria mapping is incorrect
charu: what other roles can we use if not aria?
wilco: this is why aria doesn't prevent use of other rules
... who is the liaison on this?
... Charu is the liaison
wilco: no one has looked at this yet
maryjo: survey sent out yesterday
wilco: no responses, so ask everyone to complete surveys
wilco: rule doesn't account for different types of disabled elements
... this one due next week
... filled out decision-making process, but without comments
... do we need a cfc?
... waiting on chairs to decide whether AG will review
... waiting on one more change to be finalized by the community group, open pull request
<Wilco> https://github.com/act-rules/act-rules.github.io/pull/1465
wilco: autocomplete needs a liaison
Shadi to take this one