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

Accessibility Requirements: Updates requested (Shadi) #250

Closed
moekraft opened this issue Aug 16, 2018 · 3 comments · Fixed by #283
Closed

Accessibility Requirements: Updates requested (Shadi) #250

moekraft opened this issue Aug 16, 2018 · 3 comments · Fixed by #283

Comments

@moekraft
Copy link
Collaborator

Editor’s note: The ACT Task Force is looking for feedback about the use of the term "pass" in relation to rules. While rules can "pass", their corresponding accessibility requirement can fail. A section has been added to make this explicit in the rule, but we would like to know if this is sufficient.
Accessibility requirements are just that: A requirement that content must conform to for it to be considered accessible. These are usually WCAG success criteria but can include other requirements too. For example, an organization might have additional requirements, such as local laws or internal standards. These too are considered accessibility requirements and can be tested using ACT Rules. What the precise requirements are for any particular test is beyond the scope of the ACT Rules Format.
ACT Rules SHOULD identify the accessibility requirements that are not met when the outcome of a rule is Fail. An ACT Rule is a complete or partial test for one or more accessibility requirements. However, an ACT rule MUST NOT test more than the accessibility requirements it lists.
ACT Rules MUST indicate when they can not be used to determine that the accessibility requirement passed.
Outcomes from an ACT Rule SHOULD be consistent with the accessibility requirement, e.g. a rule only returns the outcome Fail when the content does not meet the accessibility requirement. This means that the rule maps to the accessibility requirement, as opposed to it merely being related to the requirement, thematically or otherwise. Because of this, atomic rules used in composed rules often do not map to any accessibility requirement. Failing the composed rule fails the accessibility requirement, but failing any of its atomic rules may not. In such cases the atomic rules MUST NOT list the accessibility requirements. These could be provided as background information instead.

Comments:

  1. An example is needed for this statement, ACT Rules MUST indicate when they can not be used to determine that the accessibility requirement passed.

  2. Is this a rule or precondition? _. In such cases the atomic rules MUST NOT list the accessibility requirements.
    Accessibility Conformance Testing.docx
    _

@WilcoFiers
Copy link
Collaborator

Comment 2 for discussion.

@maryjom
Copy link
Collaborator

maryjom commented Aug 30, 2018

Meeting notes: The group wants the intent to be the same but more specific on when rules MUST indicate the accessibility requirement and when they MUST be consistent with the accessibility requirement and what conditions where this is a MUST NOT condition.

@maryjom
Copy link
Collaborator

maryjom commented Aug 30, 2018

@moekraft Can you edit the content here with help from @nitedog to propose a change to the group based on the discussion and meeting notes? (see above comment)

WilcoFiers added a commit that referenced this issue Sep 24, 2018
WilcoFiers added a commit that referenced this issue Sep 24, 2018
* 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
@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