<CarlosD> scribe+ sashanichols

<CarlosD> agenda Passed Example 3 in Headers attribute specified on a cell refers to cells in the same table element [a25f45] should be edited/removed #2233

<CarlosD> topic Passed Example 3 in Headers attribute specified on a cell refers to cells in the same table element [a25f45] should be edited/removed #2233

Passed Example 3 in Headers attribute specified on a cell refers to cells in the same table element [a25f45] should be edited/removed #2233

giacomo-petri: updated comment

CarlosD: only the third example is tech dependent, everything else works correctly / incorrectly

giacomo-petri: example 5 is the correct solution, this is what spec say; correct solution is not working as expected
... we shouldn't have an example that's not following specs

@joshua: put not working examples on github, maybe they can be useful

CarlosD: doesn't think we need that

introductions for a new member @joshua

CarlosD: explains details of this meeting / org moments for a new member

giacomo-petri: table 1 working the same as the other examples, the entire rule is lacking support; we need to update the rule with recommending other solutions
... add accessibility support note that half examples are working and have are not

CarlosD: agrees

helen: clarifies if issues are because of the browsers and not spec?

giacomo-petri: if browsers fix the issues, we will need to update accessibility support

CarlosD: this is different because this is what people usually use

helen: concerned about industry bugs because rules might become complicated

CarlosD: we probably should warn people about this?

giacomo-petri: maybe we should raise this point to another group
... thinks that we should warn people at least
... thats why we have accessibility support notes

Shunguo: agrees on this point

CarlosD: reviewing ACT rules format, ACT rule must include limitations on accessibility support and we know there are limitations

<Dan_Tripp> Source for Carlos' quote: "An ACT Rule must include known limitations on accessibility support." - https://www.w3.org/TR/act-rules-format/#accessibility-support

CarlosD: we should include accessibility support notes on limitations that exist
... include in the description of an example that markup will work but invalid

giacomo-petri: is fine with that

Shunguo: mention specific browser support in accessibility support because browser implementation might change; maybe in the future mention which major browsers we support

CarlosD: discussing Dan's PR

Dan_Tripp: wait until it appears on the agenda

helen: it was in the agenda a couple meetings back

CarlosD: this is voluntary work and when there is time to work on it, notify and it will be put on the agenda

Dan_Tripp: will work on the item and will let us know when it's ready

CarlosD: looking at other PRs to bring up

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

giacomo-petri: this is an inapplicable example? automated tools should be able to mark it as a violation if it causes accessibility issues

Dan_Tripp: doesn't understand why this note is added to this particular rule

giacomo-petri: a lot of assistive tech ignore empty heading so they are essentially not causing accessibility problems

CarlosD: there is an inapplicable example in this rule that has an empty heading

Dan_Tripp: could we add a mention of the inapplicable example to the accessibility support note?

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: Sage, CarlosD, Dan_Tripp, Helen, Shunguo, giacomo-petri, sashanichols, Vartika, Joshua
Present: Sage, CarlosD, Dan_Tripp, Helen, Shunguo, giacomo-petri, sashanichols, Vartika, Joshua
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: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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