Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear split between requirements for rule authors vs. rule implementers #272

Closed
annethyme opened this issue Sep 20, 2018 · 1 comment · Fixed by #283
Closed

Clear split between requirements for rule authors vs. rule implementers #272

annethyme opened this issue Sep 20, 2018 · 1 comment · Fixed by #283

Comments

@annethyme
Copy link

annethyme commented Sep 20, 2018

These sections are as the only ones in the ACT Rules Format related to the implementation of rules rather than the ACT rules themselves:

Mixed in with these are these sections that are actually requirements for ACT rules themselves:

These three requirements for ACT Rules are however not listed in the 4. ACT Rule Structure, making them seem less of a requirement for ACT Rules.

I suggest we:

  • somehow make it clear from the structure of the document and in the wording of the sections which sections are specifically implementation related
  • Add Test Cases, Change log and Issues list to the 4. ACT Rule Structure
@annethyme
Copy link
Author

@WilcoFiers, you mentioned that this would go on the agenda this Thursday, but I don't see it explicitly. Do you see it as covered by the items on the agenda, #277 or #276?

@maryjom maryjom added the For CR label Oct 1, 2018
@WilcoFiers WilcoFiers mentioned this issue Oct 11, 2018
WilcoFiers added a commit that referenced this issue Oct 14, 2018
### Issues resolved by this PR: 

- Clear split between requirements for rule authors vs. rule implementers : Closes #272
- Need a definition of Test Target : Closes #271
- 16. Rule Aggregation - Add Requirement : Closes #252
- Accessibility Requirements: Updates requested (Shadi) : Closes #250
- 15.2. Accuracy Benchmarking - Update definition : Closes #236
- Outcomes of atomic tests : Closes #235
- clarifying the relationship between rule application and accessibility conformance : Closes #227
- ACT i18n checks : Closes #226
- Clarify the definition of Rule Aggregation : Closes #165
- Clarify how to do "Implementation validation" and "accuracy benchmarking" for manual or semi-automated rules : Closes #163
- Clarify the output format definition : Closes #162
- Mark all Informative sections as such : Closes #280
- "Failed" / "Passed" or "Fail"/"Pass"? : Closes #279
- Require Rule ID's in Atomic Rule List : Closes #261
- Scope sections states ACT rules should not be used for conformance : Closes #281
- Section “13. Accessibility Support” unclear : Closes #221
- Examples need to be identified accessibly : Closes #187

### Outstanding discussions before CR: 

- List of features for exit criteria #224

### Outstanding editorials before CR:

- Need non-versioned biblio reference tags #216


<!--
    This comment and the below content is programatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<a href="https://pr-preview.s3.amazonaws.com/w3c/wcag-act/pull/283.html" title="Last updated on Oct 12, 2018, 12:04 PM GMT (1776294)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag-act/283/38370ea...1776294.html" title="Last updated on Oct 12, 2018, 12:04 PM GMT (1776294)">Diff</a>
@nitedog nitedog added For CR and removed For CR labels Mar 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants