Re: CFC #2, move ACT Rules Format out of Candidate Recommendation

Hey Anne,
Yeah, for some reason the ACT-R website didn't build last night. Sorry, I
checked it locally that all the fixes went in, but I didn't wait around for
it to get pushed. I'm looking into it, and will try to get it sorted. Here
is the stuff that that should fix:
https://github.com/act-rules/act-rules.github.io/pull/674#issue-296846133

That leaves open your comments on:

> C9 – link for No keyboard trap (80af7b) goes to No keyboard trap
non-standard navigation (ebe86a) instead

Copy-paste error, I'll sort that out right away.

> C19 – “View issues” for video rule returns an empty list – can that be
considered an “issues list” when it’s empty? For the others: Shouldn’t the
list only have open issues on it? Closed issues/PRs should be recorded in
the changelog instead, according to ACT Rules Format. This would mean that
keyboard rule cannot either be used as an example here.

I'll put in a different rule that does have an open issue for it.

Wilco


On Fri, Jul 12, 2019 at 11:26 AM Anne Thyme Nørregaard <ath@siteimprove.com>
wrote:

> Re-reviewed and still have some comments:
>
>
>
> Could be critical for fulfilling exit criteria and leaving CR:
>
>    - C1 – the “outcome definition” is still missing from the Glossary for
>    each rule
>    - C4 – they are still not satisfying tests, are they?
>    - C9 – link for No keyboard trap (80af7b)
>    <https://act-rules.github.io/rules/ebe86a/> goes to No keyboard trap
>    non-standard navigation (ebe86a)
>    <https://act-rules.github.io/rules/ebe86a/> instead
>
>
>    - C19 – “View issues” for video rule returns an empty list – can that
>    be considered an “issues list” when it’s empty? For the others: Shouldn’t
>    the list only have open issues on it? Closed issues/PRs should be recorded
>    in the changelog instead, according to ACT Rules Format. This would mean
>    that keyboard rule cannot either be used as an example here.
>
>
>
> Usability issues, probably not critical for leaving CR:
>
>    - C1 – date on rules are still missing
>    - C1 – Renaming “Accessibility Requirements” to “Accessibility
>    Requirements Mapping” in ACT-R rules
>    - C18 – I still find it confusing that:
>
>
>    - the keyboard rule only has one definition altogether, and it’s in
>    the input rules that there are more than one definition, and
>    - that the Glossary for the video rule only has one definition, and
>    that the “more than one” definitions are because the rule links out to
>    specs etc.
>
>
>    - C19 – Issues list still does not show up on my laptop screen / any
>    smaller screen
>
>
>
> Best Regards,
>
> *[image: signature_1623488222]*
>
>
>
> Anne Thyme Nørregaard
>
> *Digital Accessibility Product Expert*
>
>
>
> *[image: Siteimprove]* <http://siteimprove.com/da/>
>
>
>
> Sankt Annæ Plads 28  |  DK-1250 København K
>
> Mobile +45 23 28 53 91  |   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: *Friday, 12 July 2019 at 00:43
> *To: *Accessibility Conformance Testing <public-wcag-act@w3.org>
> *Subject: *CFC #2, move ACT Rules Format out of Candidate Recommendation
> *Resent-From: *<public-wcag-act@w3.org>
> *Resent-Date: *Friday, 12 July 2019 at 00:43
>
>
>
> Hey everyone,
>
> After some feedback on a CFC from Monday, we think all issues have been
> sorted out and are ready for another CFC. As before, a new draft has been
> created that shows all of the changes. We have also collected all of the
> information we think necessary to meet the exit criteria. The next step
> will be to propose leaving candidate recommendation to the Accessibility
> Guidelines Working Group.
>
> Please let us know if you have any concerns going forward with this step.
> This call for consensus ends on Monday July 15th.
>
> You can find the editors draft here:
> - https://w3c.github.io/wcag-act/act-rules-format.html
> <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwcag-act%2Fact-rules-format.html&data=02%7C01%7Cath%40siteimprove.com%7C2022748ee0654e27a2de08d706512593%7Cad30e5bc301d40dba10a0e8d40abe0f9%7C1%7C0%7C636984817907911960&sdata=INOxnXm107fgh8VWH2Ytc9e02dxbQ2pV1zpLH%2FC0u8U%3D&reserved=0>
>
> A diff can be found here:
> -
> https://services.w3.org/htmldiff?doc1=https://w3.org/tr/act-rules-format/&doc2=https://w3c.github.io/wcag-act/act-rules-format.html
> <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fservices.w3.org%2Fhtmldiff%3Fdoc1%3Dhttps%3A%2F%2Fw3.org%2Ftr%2Fact-rules-format%2F%26doc2%3Dhttps%3A%2F%2Fw3c.github.io%2Fwcag-act%2Fact-rules-format.html&data=02%7C01%7Cath%40siteimprove.com%7C2022748ee0654e27a2de08d706512593%7Cad30e5bc301d40dba10a0e8d40abe0f9%7C1%7C0%7C636984817907921953&sdata=vBlJ6673YLKSOeNz%2BNLEw6m9DdVwiQ3XyiRb2i3bOG4%3D&reserved=0>
>
> The implementation report can be found here:
> - https://w3c.github.io/wcag-act/act-implementations.html
> <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwcag-act%2Fact-implementations.html&data=02%7C01%7Cath%40siteimprove.com%7C2022748ee0654e27a2de08d706512593%7Cad30e5bc301d40dba10a0e8d40abe0f9%7C1%7C0%7C636984817907921953&sdata=kpeBsPuSt7FC2jgq73k9QhQ1Ex61q9PNjFuuidyG1oA%3D&reserved=0>
>
> Kind regards,
>
>
>
> --
>
> *Wilco Fiers*
>
> Axe product owner - Co-facilitator WCAG-ACT - Chair ACT-R / Auto-WCAG
>
> [image: cid:BCBD7D4B-677E-4B95-AE3F-60005DBD9EE4]
>


-- 
*Wilco Fiers*
Axe product owner - Co-facilitator WCAG-ACT - Chair ACT-R / Auto-WCAG