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.

Sign up for GitHub

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

Jump to bottom

4. ACT Rule Structure - Improvement suggestion #232

Closed
annika-FTB opened this issue Jul 24, 2018 · 1 comment
Closed

4. ACT Rule Structure - Improvement suggestion #232

annika-FTB opened this issue Jul 24, 2018 · 1 comment
Assignees
@moekraft
Labels
editorial For CR

Comments

@annika-FTB
Copy link

Add an item in the rule structure that describes the type of the rule (atomic or composed). In this way the types can be distinguished easily without having the refer to indirect information provided in other items such as the "aspects" or "rules list" items.
@annika-FTB annika-FTB mentioned this issue Jul 24, 2018
Closed
@WilcoFiers
Copy link
Collaborator

Suggestion agreed on during the call.

WilcoFiers added a commit that referenced this issue Sep 24, 2018
@WilcoFiers
Add rule type to the rule structure #232
c0921ee
@WilcoFiers WilcoFiers mentioned this issue Sep 24, 2018
Merged
WilcoFiers added a commit that referenced this issue Sep 24, 2018
@WilcoFiers
Lots of small editorial changes (#273)
f6210f2 
* Remove aspects MUST requirement #264

* Updated aspects based on feedback #257

* Make test cases required for all rules

* Change "local laws" to "laws" #231

* Add a paragraph on accessibility of rules #226

* Rewrote benchmark to non-normative section #236 #239 #163

* Consistency in rule-aggregation #266

* Tweaked accessibility support language #221

* Changed test subject from MUST to MAY #220

* Require rule IDs in atomic rules list #261

* Fix rule type example #230

* Add rule type to the rule structure #232

* Update from #274

* Add "satify" explanation for Rules to SCs. #227

* Example to "satisfy" WCAG SCs #250

* Scrub document to ensure correct use of "should" and "may" #267

* Break up the PR
@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
Assignees

@moekraft moekraft

Labels
editorial For CR
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@WilcoFiers @nitedog @moekraft @annika-FTB