Accessibility Conformance Testing Teleconference

<trevor> scribe: trevor

<Todd> scribe: Todd

CFC: Approve "Element with presentational children has no focusable content"

all +1 to the CFC

Ready for AG

Need to update survey or align with Wilco that this is ready

RESOLUTION: CFC ready for approval

ACT rules sheet and Surveys

Karen's rule ready for AG

<trevor> https://github.com/act-rules/act-rules.github.io/pull/1683

Trevor line-height merge is stuck on the license.

Todd can find solution to license problem

Kathy's rule, Carlos is still working on the PR for this.

Karen needs feedback from Wilco on iframe with negative tabindex rule

Open ACT pull requests

PRs being approved and Call for Reviews being done

Updated WAI rule pages design

This is the big news1

<dmontalvo> https://www.w3.org/WAI/standards-guidelines/act/rules/html-page-non-empty-title-2779a5/#accessibilityrequirementsmapping

WIlco said last week there were minor tweaks to do

Typo with atomic and composite rule and is live now

adding pointers to the pages through the WAI web site

How to evaluate for accessibility and explanation of WCAG documents

Updates to the ACT Introduction in WAI web site. Update pages that relate to task force and is now live

Wilco will continue work on process

kathy: any idea of other modifications planned?

dmontalvo: we should have navigation included that we need to figure out
... how we promote ACT will be the focus and will provide discussion on that for better plan
... update next week for that

kathy: someone mentioned code formatting

dmontalvo: opening different window issue being worked on by Wilco
... contrast is template thing, style issue
... both will be addressed

kathy: any feedback from anyone, provide to Daniel or Wilco

What to do with deprecated rules?

dmontalvo: what do we do with that? Do we signal that it is deprecated?
... Not really sure what Wilco is doing. How can we signal rules are deprecated and where they are being tested

kathy: Where can we keep track of these?
... do we keep separate list? list deprecated rules on the site?

dmontalvo: Would be weird, list on CG. Why did we deprecate it, explain why.

kathy: agree.

Heading has non-empty accessible name (1ec09b)

kathy: one rule that we had surveyed
... possibly SC 2.4.6, might be more suitable

+1

kathy: Wilco presented 2.4.6 may be for more visual headings
... open up for discussion here, to pull in 2.4.6

Helen: heading markup less of an issue. 1.1.1 was pulled into the example.
... Is this failing the rule or different rule (Failed Example 1)

kathy: Will was doing AT testing. Wait for Will to come back to report findings.

dmontalvo: my understanding is issues were found, only with old AT (2 or 3 versions behind current ones)

kathy: Go back to Ag?

dmontalvo: discussing going to AG with what we have, how does this fit into current WCAG
... Does current AT ignore this

kathy: Wait for Wilco as Helen suggested. Failed examples seem to fail more.
... some failed examples have issues with other SC's like 1.1.1 and 2.4.6

Helen: Do we think technically should they be taken out?
... Is this normative or practical example?

ACT content updates

kathy: Karen, Daniel and Kathy making sure all materials are up to date in document
... do we need further review before doing PR's, etc.?

dmontalvo: we have an understanding in doc of what to do. may want to have more detailed or clear description of pages we focus on
... something I need to do

Daniel will review PR's. No one will break anything if PR is submitted.

<dmontalvo> scribe- Trevor