<CarlosD> scribe+ sashanichols

ACT standup

<Wilco> https://deploy-preview-330--wai-wcag-act-rules.netlify.app/standards-guidelines/act/rules/wcag/

Wilco: reviews, moving summary element to AG, working on a new page for displaying the rules (topic?)

Shunguo: 2 PRs

<Shunguo7> #2322. #2318

Kathy: a few tasks from the Monday planning meeting, following up by PR #334, follow up on one other role submitted previously for review

Vartika: nothing much

https://github.com/act-rules/act-rules.github.io/pull/2328

sashanichols: PR review, opened a PR to fix undefined issue on the rule, PR #2328

Sage: meeting with Wilco, approved some PRs

CarlosD: ACT task force disappeared form the agenda?

Kathy: resolve some ongoing repeated questions from AG every time we submit the role for review, figure out some processes with a set of rules we are submitting

Expand the iframe focusable rule to include scrollable non-interactive element in an iframe https://github.com/act-rules/act-rules.github.io/issues/2320

Shunguo: describing the issue case, suggesting expanding the rule to include a text when there is a scrollbar

@wilco: suggesting splitting the issue since there are 2 topic being discussed

Wilco: suggesting expanding the iframe rule for this issue instead

Kathy: could we consider the scrollbar to be interactive element?

CarlosD: iframe is not interactive, agrees with the suggestion to expand the iframe rule

Wilco: gets clarification on the issue when the iframe gets too much content, gets a scroll and the effect of the negative tabindex on it
... supports the change
... does this need to be a separate rule?

Shunguo: discussing iframes with just text
... better to fit into just this rule

CarlosD: update this rule instead of creating a new one?

Shunguo: yes

CarlosD: thinks this scenario is more applicable to the scrollable content
... ok with changing the iframe rule

Kathy: update iframe rule

CarlosD: go with updating the iframe rule

Shunguo: will go edit it

Wilco: difference between scroll and focus scenarios? the problem is interactive elements can be reached, the scenario we have now is to ensure the content can be scrolled, likes having a separate rule for this
... thinks it needs a separate rule per the rules format

Shunguo: ok with that

Wilco: discuss the other point - not putting focus on scollable element?

Shunguo: tested focus with Safari

<Wilco> https://www.w3.org/WAI/content-assets/wcag-act-rules/testcases/0ssw9k/5fa34d0a7eea03109cd12c0e7c21fce793c268db.html

Wilco: confirmed that Safari doesn't scroll it

CarlosD: also confirmed that Safari doesn't scroll it

Shunguo: will test it again

"Heading has non-empty accessible name" [ffd0e9]: Update from TF survey https://github.com/act-rules/act-rules.github.io/pull/2077

CarlosD: Wilco asked us to discuss it a month ago

Wilco: this came from the task force suggestion
... this is not a WCAG failure
... consider this making an aria requirement
... we don't have examples that fail WCAG 1.3.1, should be mapped to aria and not WCAG

Shunguo: if heading doesn't have content, is it a failure for 1.3.1?

Wilco: empty headings are not listed for AT

CarlosD: image that is marked as a heading without accessible name?

Wilco: it's 1.1.1 failure

Kathy: what about 2.4.6?

Wilco: it refers to heading as a function, not the element

Shunguo: image with accessible name can be used as a heading
... image without accessible name will both fail the heading and the image

Wilco: disagrees

CarlosD: what success criteria the heading fail?

Shunguo: fails aria

<CarlosD> https://www.w3.org/WAI/standards-guidelines/act/rules/ffd0e9/proposed/

Wilco: the rule is already doing what it should, close the PR

<Shunguo7> My Safari version: Version 18.3.1 (20620.2.4.11.6).

Shunguo: update on Safari test, it's focusable in the version 18.3.1 (20620.2.4.11.6)

CarlosD: using 18.5

Shunguo: sharing screen to show the issue
... the iframe is with a tabindex, that's why it's focusable

This is scribe.perl Revision VERSION of 2020-12-31
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/Wilco, reviews/Wilco: reviews/
Succeeded: s/@wilco:/Wilco:/
Succeeded: s/@wilco:/Wilco:/
Succeeded: s/@wilco:/Wilco:/
Succeeded: s/SY:/Shunguo:/
Succeeded: s/Sage K:/Sage:/
Default Present: CarlosD, sashanichols, Kathy, Wilco, Shunguo7, Vartika, Sage
Present: CarlosD, sashanichols, Kathy, Wilco, Shunguo7, Vartika, Sage
No ScribeNick specified.  Guessing ScribeNick: sashanichols
Inferring Scribes: sashanichols

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.)