<Wilco> clear agenda

<Wilco> scribe: Dagfinn

Final call

<Wilco> https://github.com/act-rules/act-rules.github.io/pulls?q=is:open+is:pr+label:%22Final+call+2+weeks%22

<Jean-Yves> https://github.com/act-rules/act-rules.github.io/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+label%3A%22Final+call+1+week%22+

Rule is good, with many approvals

<Wilco> https://github.com/act-rules/act-rules.github.io/pulls?q=is:open+is:pr+label:%22Final+call+1+week%22

Reviewers wanted

<Wilco> https://github.com/act-rules/act-rules.github.io/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+label%3A%22reviewers+wanted%22+

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

Many fixes

Rule was not mapping to the SC. WCAG definition of labels was not taken into account

<Jean-Yves> https://github.com/act-rules/act-rules.github.io/issues/423

Side note: user crazybat is added as a collaborator to the group

Use "top-level browser context" instead of "web page"? #869

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

To redefine WCAG def "web page" is not a good idea. Rather not use that term

is it sufficient to have a def that is still unambigous?

we should use plain language in defs

top-level browser context does not fully align with what we mean by browser content

web page def is fairly broad

web page and browsing context are different things

browser context = a container for a window object. May be nested

web page is top level browsing context plus all context that is nested in it

the wcag def of web page is more general than HTML def

WCAG def could also include content such as PDF or other docs

support for both plain language def and a technical def

have a web page def for html named Web page (HTML)

Test case files are all invalid HTML and trigger quirks mode #952

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

test cases have no doctype, this trigger quirks mode

<Wilco> https://github.com/act-rules/act-rules.github.io/issues/952#issuecomment-545347799

could possible create changes in interpretation

possible solution is to add doctype to all test cases that don't have one, but this is disruptive and labour-intensive

could add a note that test case snippets must be wrapped and doctype added

Could add links to test cases to open them up

Expectation: "**each** test target" vs "**the** test target" #956

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

<Wilco> https://www.w3.org/TR/act-rules-format/#expectations-atomic

there will be an outcome for each individual test target

for most of the atomic rules, the test targets are checked individually. In these cases "the" works better

each means every in the grammatical sense

test rules will result in one or more outcomes, one for each test target

<EmmaJ_PR> https://www.grammarly.com/blog/each-and-every/

we should follow the ACT spec

"each" refers to items individually in a group of items

pick up this item in the ACT TF

Did not have time for all items on the agenda

<Wilco> trackbot, end meeting

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
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: Wilco, Jey, Jean-Yves, shadi, Kasper, Dagfinn
Present: Wilco Jey Jean-Yves shadi Kasper Dagfinn
Found Scribe: Dagfinn
Inferring ScribeNick: Dagfinn

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 24 Oct 2019
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.)