<Wilco> scribe: Jey

zakim take up next

ARIA rules update

wilco: this came up with the act tf meeting

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

and wants to see how to embrace other accessibility requirements like ARIA into the rules

wilco: example the 3 aria rules in our current list, should not point to wcag as accessibility requirements
... Solution: we change the 3 aria rules to map to ARIA
... Solution: we author 3 narrowed down rules specifically targeting WCAG

anne: this is what we proposed may be half an year ago
... going into details of how to scope down the ARIA rule
... questions how many exceptions and work-around we will have to try and scope down rule to target WCAG

wilco: we would not make up test cases with invalid test examples, then that is a bigger problem, and or accessibility problem & we should not do that

<EmmaJPR> thanks

shadi: i have nothing else to do :)

wilco: with above, I would like permission from the group to bypass the CFC stage for changing accessibility requirements.

<shadi> +1 to Anne

anne: can we try to change the accessibility requirements and get the PR in quickly

wilco: does making the change break the site

Jey: Nope

wilco: how many pr's
... better to do as 1 PR

New Rule: Meta viewport do not prevent zoom #589

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

we need to clarify on the process of when to start a new rule

anne: would prefer a better workflow for embracing new rule
... so people can provide initial feedback, perhaps a label

wilco: may be have this as a regular item in the meeting agenda, to go through proposals

shadi: pr's are more easy to follow than issues.

anne: how do we know if the community approves the rule.

emma: this is something that can be taken to the wcag group

<EmmaJPR> https://www.w3.org/WAI/WCAG21/Understanding/reflow.html

wilco: what do you mean WCAG did not have an agreement on it?

@@ "Interfering with a user agent's ability to zoom" i.e., author using: maximum-scale or minimum-scale or user-scalable=no or user-scalable=0 in the meta element ?? @@ Note: In Pinch zoom thread on the WCAG list people did not seem to be in favor of this as a failure.

wilco & emma: analysing the above failure thread

anne: on the surface it looks good & have to dig into the SC

emma: definitely worth pursuing

Should assumptions be displayed above applicability #581

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

<Wilco> https://section508coordinators.github.io/ICTTestingBaseline/

<Wilco> https://section508coordinators.github.io/ICTTestingBaseline/01Keyboard.html

wilco: in going through the baseline that was created by truster tester, is it worth listing assumptions before applicability.
... likes the idea
... make the assumptions prominent?

+1

emma: should we name the section `Limitations, Assumptions ...`?
... agrees to re-order the sections

audrey: no idea

anne: no strong feeling
... should we change it in the act rules format

emma: we should not differ from act rules

wilco: act rules does not emphasise order
... we should be able to make this change & come up with a little proposal

solution: wilco & emma to work on it together

Face to Face meeting, September 2019? #578

Jey: October is preferrable

Emma: some of my colleagues will be getting involved

Anne: I am not allowed to fly anywhere
... Kasper & I can fill in remotely

wilco: will you be able to participate

audrey: I will be keen, but cannot do early September.

anne: SI can host

jey: final thoughts: good meeting

emma: final thoughts: I may be less involved, but other colleagues might pick up. I will catch up on work.

audrey: final thoughts: good meeting

anne: final thoughts: writing a process outline & coming along slowly.

Thank you.

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)

Succeeded: s/act-rules//
Succeeded: s/is the password//
Succeeded: s/Hi - failing to guess the password//
Succeeded: s/Emma, can you present+ please.//
Present: Jey audrey anne_thyme_ Wilco shadi EmmaJPR
Found Scribe: Jey
Inferring ScribeNick: Jey

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