<Wilco> trackbot, start meeting
<audrey> hello! sorry what is the password ? :-)
<Wilco> scribe: Dagfinn
<Wilco> https://github.com/act-rules/act-rules.github.io/issues/472
<Wilco> https://github.com/act-rules/act-rules.github.io/pull/488/files
Wilco: ACT rules format is updated, is in candidate rec phase and stable
<Wilco> https://github.com/act-rules/act-rules.github.io/pull/488/files#r278286575
Wilco: Changes: New id-property
(random string), from success criterion to accessibility
requirement. Outcomes of rules are always mapped to WCAG.
... Some minor editorial changes. For full overview, see PR
488
Anne: Do you have any comments to the PR? Submit by Tuesday
<Wilco> https://github.com/act-rules/act-rules.github.io/issues/487
Wilco: Is this a reliable rule?
Comments?
... what if autocomplete is used on a field that doesn't need
it? Does this happen?
Brian: Autocomplete is used very
little. difficult to predict use in templates, that may cause
false positives
... we need to reassess the rule if this causes a lot of false
positives
Kasper: This rule coupled with assumptions is valid.
<Wilco> https://github.com/act-rules/act-rules.github.io/issues/470
Jey: Some PR have randomised string as file name. we use different conventions. What is the way to go fwd?
Wilco: Proposal to have shortened name followed by id in file name
<EmmaJ_PR> Sorry to be late ... Webex meeting number isn't working for me
Fil name updates to be done before rule format update. Jey looks at this
<Wilco> https://github.com/act-rules/act-rules.github.io/issues/458
<Brian_Bors_> Wilco send another email detailing a new meeting number
Wilco: We need a changelog to the rules
<Wilco> https://github.com/act-rules/act-rules.github.io/commits/develop/_rules/SC3-1-1-html-has-lang.md
Wilco: different solutions: Write
by hand, use change history from files
... downside with file history: We need to describe changes
more strictly.
Kasper: The change history makes it easier to see
Wilco: Need guidance on how to write good PR titles
Kasper writes a proposal for PR titles :)
EmmaJ: It would be useful to have guidance on how to create PRs
Kasper's assignment: How to write good PR - titles and scope of PR.
<EmmaJ_PR> https://act-rules.github.io/pages/contribute/#submit-a-draft-for-a-rule-pull-request-on-github
Also see the github documentation
<Wilco> https://github.com/act-rules/act-rules.github.io/issues/482
Wilco: We have som automated implementations, but need a way to submit implementations
<Wilco> https://www.w3.org/WAI/eval/report-tool/#/
Wilco: you could download a json file to open in the WCAG-EM report tool
Jey is working on generating a json file for each rule. should be done soon
<Wilco> https://github.com/act-rules/act-rules.github.io/issues/444
Kasper/Anne: Is it better to keep this as one rule, or split it into two?
<Wilco> https://github.com/act-rules/act-rules.github.io/pull/444#issuecomment-482066333
Wilco: Headings need both a
descriptive text and an acc name. those are not always the
same
... for instance when using aria-label on heading
... do we want to worry about the accessible name? It is an
edge case
EmmaJ: For some users, the acc
name is the only one they will see
... but why would they be different?
Dagfinn: Would SC 2.5.3 affect this?
Wilco: Depends on how you define user interface component
Not a composite rule. The rules are similar, but are note the same rule
<Brian_Bors_> My connection is really bad for the last 5 minutes but I just wanted to add that I have never seen a heading that has a different accessible name in practice and I have no to problems with the rule splitting up
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) Present: Kasper anne_thyme Dagfinn Wilco audrey Brian_Bors_ Found Scribe: Dagfinn Inferring ScribeNick: Dagfinn WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting 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.)[End of scribe.perl diagnostic output]