Re: Go to CR with ACT Rules Format

Hi,

Still reading doc, but I wanted to flag – under the Applicability Section.

We don’t account for the option to set applicability to being always true for a test.  Certain things just don’t have an applicability test, or the test is the same as the applicability test e.g. test for marquee element.

All the best

Alistair

From: Anne Thyme Nørregaard <ath@siteimprove.com>
Date: Wednesday, 17 October 2018 at 15:46
To: Wilco Fiers <wilco.fiers@deque.com>, Accessibility Conformance Testing <public-wcag-act@w3.org>
Cc: Stein Erik Skotkjerra <ses@siteimprove.com>
Subject: Re: Go to CR with ACT Rules Format
Resent-From: <public-wcag-act@w3.org>
Resent-Date: Wednesday, 17 October 2018 at 15:45

+1 from Siteimprove, but with comments:

Section “4. ACT Rule Structure”

  *   “ACT Rule Format [outcome](https://w3c.github.io/wcag-act/act-rules-format.html#outcome) definition” – We don’t really get what this bullet means, and it seems to us that it should be removed from this section that lists “MUST” requirements.
  *   It seems that we are missing 2 bullets that are also requirements for the ACT Rule Structure:
     *   “Change Log (or link to it), if any”
     *   “Issues list (or link to it), if any (optional)”

Section “7.1 Accessibility Requirements List”

  *   “An ACT Rule SHOULD list an identifier and a reference for each accessibility requirement that it maps to.” --> “An ACT Rule MUST list an identifier…”.
It is already limited to those accessibility requirements that it maps to, so it should be safe enough to use MUST.

Section “7.2 Accessibility Requirements Mapping”

  *   From this new section it seems that I could list an accessibility requirement for an atomic rule, where it is actually the composite rule that is mapped to the success criterion, as long as I write something like this for the mapping: “failed: Further testing is necessary to determine if the success criteria are not satisfied”. Is it the intention to allow this?

Section “9. Atomic Rules List (Composite rules only)”

  *   There was talk about allowing composite rules to list use other composite rules as input. Where did this end?


“Section “10.1 Applicability for Atomic Rules”

  *   We suggest (again) removing the following, that is a leftover from the old Auto-WCAG rules format:
“When a formal syntax, such as a CSS selector<https://www.w3.org/TR/selectors-3/> [css3-selectors]<https://w3c.github.io/wcag-act/act-rules-format.html%22%20%5Cl%20%22biblio-css3-selectors> or XML Path Language<https://www.w3.org/TR/xpath/> [XPATH]<https://w3c.github.io/wcag-act/act-rules-format.html%22%20%5Cl%20%22biblio-xpath>, can be used, that (part of the) applicability MAY use that syntax in addition to the plain language description.”
If we want to keep it, we suggest moving it to a note, since it’s not really part of the formal specification.

Best Regards,


Anne Thyme Nørregaard
Digital Accessibility Product Expert

[cid:image002.png@01D3AA4A.C3084FC0]<http://siteimprove.com/da/>

Sankt Annæ Plads 28  |  DK-1250 København K
Mobile +45 23 28 53 91  |  
ath@siteimprove.com<mailto:ath@siteimprove.com>

Facebook<https://www.facebook.com/Siteimprove>   Twitter<https://twitter.com/Siteimprove>   LinkedIn<https://www.linkedin.com/company/siteimprove>

Unsubscribe<http://go.siteimprove.com/hs/manage-preferences/unsubscribe-simple>


From: Wilco Fiers <wilco.fiers@deque.com>
Date: Monday, 15 October 2018 at 19.07
To: Accessibility Conformance Testing <public-wcag-act@w3.org>
Subject: CFC: Go to CR with ACT Rules Format
Resent-From: <public-wcag-act@w3.org>
Resent-Date: Monday, 15 October 2018 at 19.07

Hey everyone,

We've closed a ton of issues over the past few weeks, and our Github issues list is now free of any issues that could mean changes to the requirements in the ACT Rules Format (there is still some editorial work in there though).

With this Call For Consensus we'd like to ask the ACT Task Force to approve sharing the editor's draft and the proposed exit criteria with the AG Working Group, and to ask them for approval to go into Candidate Recommendation.

You can find the editor draft here:
  https://w3c.github.io/wcag-act/act-rules-format.html<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwcag-act%2Fact-rules-format.html&data=02%7C01%7Cath%40siteimprove.com%7C4922b1c7bdd8477f8f8208d632c0bd7a%7Cad30e5bc301d40dba10a0e8d40abe0f9%7C0%7C0%7C636752200730191406&sdata=EsKLTSBSZaIp5JQ52VAe69RUIDoaXQTZevdBX3RbCO8%3D&reserved=0>

You can find the proposed exit criteria here:
https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Exit_Criteria_for_Rules_Format_Spec<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FGL%2Ftask-forces%2Fconformance-testing%2Fwiki%2FExit_Criteria_for_Rules_Format_Spec&data=02%7C01%7Cath%40siteimprove.com%7C4922b1c7bdd8477f8f8208d632c0bd7a%7Cad30e5bc301d40dba10a0e8d40abe0f9%7C0%7C0%7C636752200730201415&sdata=vnlHdyjtd5wBuq2T97lxHLkWnpOPdjhLx9JIEMBDNJY%3D&reserved=0>

If you'd like to see all the changes between the last published draft and the current editors draft, you can see those here: (Status of the document will be added on publication)
https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Fact-rules-format%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fwcag-act%2Fact-rules-format.html<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fservices.w3.org%2Fhtmldiff%3Fdoc1%3Dhttps%253A%252F%252Fwww.w3.org%252FTR%252Fact-rules-format%252F%26doc2%3Dhttps%253A%252F%252Fw3c.github.io%252Fwcag-act%252Fact-rules-format.html&data=02%7C01%7Cath%40siteimprove.com%7C4922b1c7bdd8477f8f8208d632c0bd7a%7Cad30e5bc301d40dba10a0e8d40abe0f9%7C0%7C0%7C636752200730201415&sdata=kI0PV70w%2FCNQrMYDxapvcC6o32HLfUPyVzV5YlQv0w8%3D&reserved=0>

Background:
Reaching Candidate Recommendation means the ACT Rules Format will be feature complete. Requirements in the ACT RF can not be changed anymore, without going back to working draft. Editorial changes will still be possible. Once in Candidate Recommendation, the ACT Task Force will need to work to meet all of the exit criteria.

Please respond to this e-mail with a "+1" if you approve, or with a "-1" if you have any objections. The CFC closes on Wednesday October 17th.

Kind regards,

--
Wilco Fiers
Senior Accessibility Engineer - Co-facilitator WCAG-ACT - Chair Auto-WCAG
[cid:BCBD7D4B-677E-4B95-AE3F-60005DBD9EE4]