You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/implementations/mapping.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,30 +4,30 @@ title: Mapping To Rule
4
4
5
5
## Implementation Scoping
6
6
7
-
An implementation does not need to be a one-to-one mapping to ACT-R rules. A single implementation can test multiple ACT-R. In manual test procedures, it is common to test multiple things at once. For instance, a test procedure looking at the language of a page will simultaneously test whether or not the `<html>` element has a `lang` attribute, if the value of the `lang` attribute is valid, and if the value matches the language of the page. These are 3 separate rules, covered in a single test procedure of an implementation.
7
+
An implementation procedure does not need to be a one-to-one mapping to an ACT rule. A single implementation procedure can test multiple ACT rules. In manual test procedures, it is common to test multiple things at once. For instance, a procedure looking at the language of a page will simultaneously test whether or not the `<html>` element has a `lang` attribute, if the value of the `lang` attribute is valid, and if the value matches the language of the page. These are 3 separate rules, covered in a single test procedure of an implementation.
8
8
9
-
<figurerole="figure"aria-label="Single implementation, mapping to two ACT-R Rules">
10
-
<figcaption>Single implementation, mapping to two ACT-R Rules</figcaption>
9
+
<figurerole="figure"aria-label="Single implementation, mapping to two ACT Rules">
10
+
<figcaption>Single implementation, mapping to two ACT Rules</figcaption>
11
11
<imgsrc="./images/impl-large-scope.svg"alt="">
12
12
</figure>
13
13
14
-
An tool or methodology can also have multiple implementations that when combined, map to a single ACT-R rule. It is common in automated test tools to split up certain rules, to build up more appropriate remediation advise. While ACT-R may have a single rule to test that all elements with the `img` role have an accessible name, an automated tool may implement testing `img` elements separate from `role="img"`, so that it gives different remediation advise for elements that can have an `alt` attribute, from elements that can't.
14
+
An accessibility tool or methodology can also have multiple implementation procedures that when combined, map to a single ACT rule. It is common in automated test tools to split up certain rules to build up more appropriate remediation advice. For example there can be a single ACT rule to test that all elements with the `img` role have an accessible name. An automated tool may implement testing `img` elements separate from `role="img"`, so that remediation advice for elements that can have an `alt` attribute will differ from elements that can't.
15
15
16
-
<figurerole="figure"aria-label="Single ACT-R rule, mapping to two implementation rules">
17
-
<figcaption>Single ACT-R rule, mapping to two implementation rules</figcaption>
16
+
<figurerole="figure"aria-label="Single ACT rule, mapping to two implementation rules">
17
+
<figcaption>Single ACT rule, mapping to two implementation rules</figcaption>
18
18
<imgsrc="./images/impl-small-scope.svg"alt="">
19
19
</figure>
20
20
21
21
## Automated Mapping
22
22
23
-
The correctness of an implementation is based on the results from running the [test cases](../testcases/) in a tool or test procedure. The three types of test cases have a range of outcomes that are allowed:
23
+
The correctness of an implementation procedure is based on the results from running the [test cases](../testcases/) in a tool or test procedure. The three types of test cases have a range of outcomes that are allowed:
| Inapplicable |`inapplicable`, `cantTell` or `passed`|
30
30
31
-
An implementation that returns one of the allowed outcomes for all test cases in an ACT-R rule is a _correct implementation_. An implementation that has all passed and inapplicable test cases correct, but only has some of the failed test cases correct is called a _partial implementation_. If a tool or methodology has partial implementations for an ACT-R rule that together get all failed test cases correct, this _set of implementations_ is considered a _correct implementation_.
31
+
An implementation procedure that returns one of the allowed outcomes for all test cases in an ACT rule is a _correct implementation_. A procedure that has all passed and inapplicable test cases correct, but only has some of the failed test cases correct is called a _partial implementation_. If a tool or methodology has partial implementations for an ACT rule that together get all failed test cases correct, this _implementation procedure set_ is considered a _correct implementation_.
32
32
33
-
An implementations can be _automated_, _semi-automated_ or _manual_. This is based on the **[mode](https://www.w3.org/TR/EARL10-Schema/#mode)** of the test and whether or not any of the outcomes is `cantTell`. An implementation is _automated_ if the test mode is "[automatic](https://www.w3.org/TR/EARL10-Schema/#automatic)" and none of the outcomes are `cantTell`. An implementation is _manual_ if one or more of the mode is "[manual](https://www.w3.org/TR/EARL10-Schema/#manual)". In all other cases, the implementation is considered _semi-automated_. If the test mode is not provided in the results, the implementation's default will be assumed.
33
+
An implementation procedure can be _automated_, _semi-automated_ or _manual_. This is based on the **[mode](https://www.w3.org/TR/EARL10-Schema/#mode)** of the test and whether or not any of the outcomes is `cantTell`. An implementation is _automated_ if the test mode is "[automatic](https://www.w3.org/TR/EARL10-Schema/#automatic)" and none of the outcomes are `cantTell`. An implementation is _manual_ if one or more of the mode is "[manual](https://www.w3.org/TR/EARL10-Schema/#manual)". In all other cases, the procedure is considered _semi-automated_. If the test mode is not provided in the results, the implementation's default will be assumed.
Copy file name to clipboardExpand all lines: pages/implementations/overview.md
+2-12Lines changed: 2 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,20 +6,10 @@ title: ACT Implementations
6
6
7
7
ACT Rules can be implemented in automated test tools and test methodologies. Tools and methodologies based on the same set of rules will produce (largely) the same results. Each rule includes a number of test cases that are used to check if an implementation is correct. The ACT Rules Community keeps a list of implementations that are actively implementing ACT Rules. By comparing how many implementations rules have, we work out which rules are widely agreed upon, and which ones need further discussion.
8
8
9
-
## Status Reports
10
-
11
-
The status of an ACT-R rule is dependent on how many implementations have adopted the rule. Once a sufficient number of implementations is reached, the ACT rule will be considered for submission for publication as a W3C note for WCAG.
|`In Progress`| The rule has less than 3 implementations |
17
-
|`Done`| The rule has 3 or more implementations |
18
-
19
9
## Contribute An Implementation
20
10
21
-
If you developed an accessibility tool or a testing methodology, and would like to have your implementation included in the ACT-R website, there are two ways you can do so.
11
+
If you developed an accessibility tool or a testing methodology, and would like to have your implementation included in the ACT-Rules website, there are two ways you can do so.
22
12
23
13
1. If you have a tool that can return a data format, you will need to run your tests against the [ACT-R test cases](../testcases/) and [submit a report](../reporting/).
24
14
25
-
2. If you have a manual test methodology, where you fill results into some report template or tool, you can [Use the WCAG-EM Report Tool](../wcag-em-tool/) instead to produce implementation reports.
15
+
2. If you have a manual test methodology where you fill results into some report template or semi-automated tool, you can [use the ACT Implementor tool](https://act-implementor.netlify.app/#/) instead to produce implementation reports.
Copy file name to clipboardExpand all lines: pages/implementations/testcases.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,6 @@ Correctness of an implementation is based on the results for test cases. See [im
54
54
55
55
If you developed an accessibility tool or a testing methodology, and would like to have your implementation included in the ACT-R website, there are two ways you can do so.
56
56
57
-
1. If you have a tool that can return a data format, you will need to run your tests against the ACT-R test cases and [submit a report](../reporting/).
57
+
1. If you have a tool that can return a data format, you will need to run your tests against the ACT rule's test cases and [submit a report](../reporting/).
58
58
59
-
2. If you have a manual test methodology, where you fill results into some report template or tool, you can [Use the WCAG-EM Report Tool](../wcag-em-tool/) instead to produce implementation reports.
59
+
2. If you have a manual test methodology where you fill results into some report template or semi-automated tool, you can [use the ACT Implementor tool](https://act-implementor.netlify.app/#/) instead to produce implementation reports.
|`testrunner`|[https://github.com/auto-wcag/testrunner](https://github.com/auto-wcag/testrunner)| JavaScript | A [puppeteer](https://github.com/GoogleChrome/puppeteer) based implementation that allows running a configurable test tool against all the above test cases on a per page basis, and returns raw results. |
9
+
|`testrunner`|[https://github.com/act-rules/testrunner](https://github.com/act-rules/testrunner)| JavaScript | A [puppeteer](https://github.com/GoogleChrome/puppeteer) based implementation that allows running a configurable test tool against all the above test cases on a per page basis, and returns raw results. |
0 commit comments