From 53eec58b3e4c7846fb52f3e8be368a2a6667183f Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Fri, 7 Jul 2017 14:46:32 +0200 Subject: [PATCH 1/3] Expand accessibility requirements section --- act-rules-format.bs | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/act-rules-format.bs b/act-rules-format.bs index e2320986..3a339d20 100644 --- a/act-rules-format.bs +++ b/act-rules-format.bs @@ -59,7 +59,9 @@ Each ACT Rule MUST have a description that is in plain language and provides a b Accessibility Requirements {#structure-accessibility-requirements} ------------------------------------------------------------------- -Explain the accessibility requirement being tested such as the WCAG 2 Success criterion and / or the technique the rule maps to; For example WCAG 2.0 Technique H67. +Explain the accessibility requirement being tested such as the WCAG 2 Success criterion and / or the technique the rule maps to; For example WCAG 2.0 Technique H67. An ACT Rule DOES NOT have to test the entire accessibility requirement. The Rule COULD be used to test multiple accessibility requirements, when such requirements overlap each other. + +Outcomes from an ACT Rule MUST be consistent within a rule, e.g. if a rule results in a fail, this must be a failure for that particular accessibility requirement. This means that the rule maps to that accessibility requirement, as opposed to it merely being related to the requirement, thematically or otherwise. Limitations, Assumptions or Exceptions {#structure-limitations-assumptions-exceptions} From 9abf4ebf20561690072fda003ca4ff7142cb5720 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Thu, 20 Jul 2017 12:37:27 +0200 Subject: [PATCH 2/3] Update Acc Req section --- act-rules-format.bs | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/act-rules-format.bs b/act-rules-format.bs index 3a339d20..cb0a6390 100644 --- a/act-rules-format.bs +++ b/act-rules-format.bs @@ -59,10 +59,12 @@ Each ACT Rule MUST have a description that is in plain language and provides a b Accessibility Requirements {#structure-accessibility-requirements} ------------------------------------------------------------------- -Explain the accessibility requirement being tested such as the WCAG 2 Success criterion and / or the technique the rule maps to; For example WCAG 2.0 Technique H67. An ACT Rule DOES NOT have to test the entire accessibility requirement. The Rule COULD be used to test multiple accessibility requirements, when such requirements overlap each other. +This section should explain the accessibility requirement the rule maps to, (for example, WCAG 2.0 success criterion 1.1.1). An ACT Rule DOES NOT have to test the entire accessibility requirement. The Rule COULD be used to test multiple accessibility requirements, when such requirements overlap each other. Outcomes from an ACT Rule MUST be consistent within a rule, e.g. if a rule results in a fail, this must be a failure for that particular accessibility requirement. This means that the rule maps to that accessibility requirement, as opposed to it merely being related to the requirement, thematically or otherwise. +Note: For WCAG 2, the Success Criteria are the accessibility requirements. Often organizations have accessibility requirements in addition to the WCAG success criteria. These too can be tested using ACT Rules. + Limitations, Assumptions or Exceptions {#structure-limitations-assumptions-exceptions} ------------------------------------------------------------------- From a83f98fd54a22078d050748e06a383c4b0265db4 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Mon, 31 Jul 2017 17:01:36 +0200 Subject: [PATCH 3/3] Update acc requirements based on ACT call --- act-rules-format.bs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/act-rules-format.bs b/act-rules-format.bs index cb0a6390..fd1c18d9 100644 --- a/act-rules-format.bs +++ b/act-rules-format.bs @@ -59,11 +59,11 @@ Each ACT Rule MUST have a description that is in plain language and provides a b Accessibility Requirements {#structure-accessibility-requirements} ------------------------------------------------------------------- -This section should explain the accessibility requirement the rule maps to, (for example, WCAG 2.0 success criterion 1.1.1). An ACT Rule DOES NOT have to test the entire accessibility requirement. The Rule COULD be used to test multiple accessibility requirements, when such requirements overlap each other. +Each ACT Rule MUST identify the accessibility requirements to which the rule maps, (for example, WCAG 2.0 success criterion 1.1.1). An ACT Rule MAY be a complete or partial test for one or more accessibility requirements. -Outcomes from an ACT Rule MUST be consistent within a rule, e.g. if a rule results in a fail, this must be a failure for that particular accessibility requirement. This means that the rule maps to that accessibility requirement, as opposed to it merely being related to the requirement, thematically or otherwise. +Outcomes from an ACT Rule MUST be consistent with the accessibility requirement, e.g. if the rule returns a Failed result, this MUST be a failure for 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. -Note: For WCAG 2, the Success Criteria are the accessibility requirements. Often organizations have accessibility requirements in addition to the WCAG success criteria. These too can be tested using ACT Rules. +The actual definition of specific accessibility requirements is beyond the scope of ACT Rules and of this document. For WCAG 2, Success Criteria are considered to be accessibility requirements. Some organizations may have particular requirements, such as specific implementation techniques to meet WCAG 2 Success Criteria; in these too would be accessibility requirements. Limitations, Assumptions or Exceptions {#structure-limitations-assumptions-exceptions}