scribe+

Ongoing projects

<Wilco> https://github.com/orgs/act-rules/projects/2

wilco: project board
... used to track different projects and upcoming and ongoing work

<Wilco> https://github.com/act-rules/act-rules.github.io/pull/2075

dan_tripp: label in name is closer, responded to review from Jean-Yves. Mostly details to wrap up

wilco: when ready, request re-review

<Wilco> https://github.com/act-rules/act-rules.github.io/issues/2393

wilco: Godwin is waiting for w3c approval which is taking longer than usual perhaps due to holidays
... Daniel was going to get some review

<Wilco> https://github.com/act-rules/act-tools/pull/53

wilco: anyone interested in starting a new project?
... need a lead and at least 2 people to help review

sorin: I'd like to start on something introductory to start with
... open to suggestion
... maybe auditing rules or updating existing rules, collaborating with other teams

Dropping aria-busy exception

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

<Wilco> https://github.com/act-rules/act-rules.github.io/pull/2387

wilco: we use aria-busy on a thing to ignore the subtree
... role=menu, put aria-busy on it, an exception applies. I think we misread ARIA standard
... aria-busy tells AT not to announce content while in progress
... AT can read content but it's not required

giacomo-petri: visual loading status but AT is not announcing "loading" doesn't matter because the aria-busy=true is provided

wilco: voiceover ignores content and doesn't announce aria-busy state. skips or hides it

kathy: that would be a problem

wilco: in menu example, valid child are menu items. a text node is not valid
... aria-busy doesn't make a text node valid

giacomo-petri: just tested and voiceover announces web content busy

sorin: I tested inapplicable example 4 and didn't get any busy info

giacomo-petri: I tested on a div with tabindex
... voiceover announced "website menu busy" in demo

wilco: more testing should be done

<Wilco> https://github.com/w3c/aria/pull/2754/changes

giacomo-petri: https://github.com/w3c/aria/pull/2754/changes

wilco: PR includes "MAY temporarily contain invalid <a>accessibility children</a>"
... thank you for raising this with aria wg
... propose closing ACT PR

RESOLUTION: close https://github.com/act-rules/act-rules.github.io/pull/2387

First element after heading (continued)

<Wilco> scribe+

<Dan_Tripp> https://github.com/act-rules/act-rules.github.io/issues/2390

<Wilco> Kathy: we discussed in a previous meeting. It raised some questions about whether we evaluate heading descriptiveness based on the first element.

<Wilco> ... Our rules approach may not be correct.

<Wilco> Armagan: The term that was introduced was first perceivable content

<Wilco> ... This creates a sort of repetition.

<Wilco> ... {showing an example}. There is no repeating content from the heading in the content after

<Wilco> ... I would suggest a radical change. Instead of heading is descriptive, it could be heading is relevant.

<Wilco> ... I'm ready to work on an alternative rule if interested

scribe+

dan_tripp: did we make progress in last ACT meeting and is it documented anywhere

wilco: maybe in minutes

dan_tripp: did we discuss block under heading

armagan: propose a rewrite of the rule

giacomo-petri: disagree with examples shown. content was related to the headings/title
... agree the first content may not be correct. maybe create a bigger context or if related

wilco: reason for first perceivable content was we couldn't figure out where a section ends
... use the first thing under the heading but not perfect

dan_tripp: ann brought up footer example. H3 in the main and then footer after.

wilco: other examples of transition to a new section without a new heading
... we had fewer tools to describe a section when we wrote this rule
... we can figure out how to do this

armagan: suggest if heading looks irrelevant, it should fail but failures should be rare

wilco: if heading describes nothing in section might be an approach

sorin: note in ACT rules says a word or single character may be sufficient

wilco: propose a new rule if interested

armagan: very interested

sorin: also interested

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)

Default Present: Kathy, Dan_Tripp, Sorin, giacomo-petri
Present: Kathy, Dan_Tripp, Sorin, giacomo-petri
No ScribeNick specified.  Guessing ScribeNick: Kathy
Inferring Scribes: Kathy

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