From d0f591a2cbd76ddc7373e55f8a6ceb733605c39e Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Fri, 20 May 2022 18:11:46 +0200 Subject: [PATCH 01/25] Try adding a navbar --- _config.yml | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/_config.yml b/_config.yml index 390ef740..f276c5ea 100755 --- a/_config.yml +++ b/_config.yml @@ -64,9 +64,14 @@ defaults: link: title: About WCAG 2 Test Rules ref: /standards-guidelines/act/rules/about/ - standalone_resource_pager: - name: All Test Rules - ref: /standards-guidelines/act/rules/ + standalone_resource_nav_links: + - name: All Rules + ref: /standards-guidelines/act/rules/ + - name: About + ref: /standards-guidelines/act/rules/about/ + - name: Tool & Methodology Matrix + ref: /standards-guidelines/act/implementations/ + plugins: - jekyll-seo-tag From b6c9cb040409057096e968a3ab64f099b9ae85e2 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Fri, 20 May 2022 18:18:44 +0200 Subject: [PATCH 02/25] hide last menu item --- content-assets/wcag-act-rules/act-styles.css | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content-assets/wcag-act-rules/act-styles.css b/content-assets/wcag-act-rules/act-styles.css index 21b2fd8f..8bc23163 100644 --- a/content-assets/wcag-act-rules/act-styles.css +++ b/content-assets/wcag-act-rules/act-styles.css @@ -1,3 +1,7 @@ +nav.nav li:last-of-type { + display: none; +} + table.act-implementations { width: 100%; } From 8e5d0a8a83a8239543046a8e312ccbbc6e65b97b Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Fri, 20 May 2022 18:21:24 +0200 Subject: [PATCH 03/25] Tweak language --- _config.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_config.yml b/_config.yml index f276c5ea..43eec9c5 100755 --- a/_config.yml +++ b/_config.yml @@ -69,7 +69,7 @@ defaults: ref: /standards-guidelines/act/rules/ - name: About ref: /standards-guidelines/act/rules/about/ - - name: Tool & Methodology Matrix + - name: Test Tools & Methodologies ref: /standards-guidelines/act/implementations/ From 5613864b25f66168908acd3acab8a0bc3824402d Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Fri, 20 May 2022 18:29:59 +0200 Subject: [PATCH 04/25] Remove about link from the header --- _config.yml | 4 ---- 1 file changed, 4 deletions(-) diff --git a/_config.yml b/_config.yml index 43eec9c5..4f15744d 100755 --- a/_config.yml +++ b/_config.yml @@ -61,9 +61,6 @@ defaults: standalone_resource_header: title: WCAG 2 Test Rules subtitle: For developers of evaluation tools and test methodologies - link: - title: About WCAG 2 Test Rules - ref: /standards-guidelines/act/rules/about/ standalone_resource_nav_links: - name: All Rules ref: /standards-guidelines/act/rules/ @@ -72,7 +69,6 @@ defaults: - name: Test Tools & Methodologies ref: /standards-guidelines/act/implementations/ - plugins: - jekyll-seo-tag - jekyll-sitemap From 1d625fd0363ccb5cdf786ef5090edc706ff99202 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Fri, 20 May 2022 18:40:34 +0200 Subject: [PATCH 05/25] Add link to the heading --- _config.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/_config.yml b/_config.yml index 4f15744d..aad7237e 100755 --- a/_config.yml +++ b/_config.yml @@ -60,6 +60,7 @@ defaults: sidebar: true standalone_resource_header: title: WCAG 2 Test Rules + title-ref: /standards-guidelines/act/rules/ subtitle: For developers of evaluation tools and test methodologies standalone_resource_nav_links: - name: All Rules From bec71eb81c6ddeecd92941776c2609a91357283c Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Fri, 20 May 2022 18:46:09 +0200 Subject: [PATCH 06/25] Tweak banner text --- _config.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index aad7237e..ea7b4aa2 100755 --- a/_config.yml +++ b/_config.yml @@ -59,9 +59,9 @@ defaults: rule_type: "atomic rule" sidebar: true standalone_resource_header: - title: WCAG 2 Test Rules + title: Accessibility Conformance Testing (ACT) title-ref: /standards-guidelines/act/rules/ - subtitle: For developers of evaluation tools and test methodologies + subtitle: Harmonised rules for WCAG 2 & ARIA standalone_resource_nav_links: - name: All Rules ref: /standards-guidelines/act/rules/ From 8c16779dec3a44eabd38d16c790faca97bef92be Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Sat, 21 May 2022 12:36:14 +0200 Subject: [PATCH 07/25] Success criterion page --- content/wcag2.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 content/wcag2.md diff --git a/content/wcag2.md b/content/wcag2.md new file mode 100644 index 00000000..4db8020e --- /dev/null +++ b/content/wcag2.md @@ -0,0 +1,18 @@ +--- +layout: standalone_resource +title: "ACT Rules for WCAG 2" +permalink: /standards-guidelines/act/wcag2/ +ref: /standards-guidelines/act/wcag2/ +lang: en +type_of_guidance: false +footer: "" +github: + repository: w3c/wcag-act-rules + path: content/wcag2.md +--- + +{% for requirement in site.data.wcag-act-rules.requirements %} + +## {{ requirement.num }} {{ requirement.handle }} + +{% endfor %} \ No newline at end of file From 352e1f531c6eb62af0315857b6f8dea12c61df40 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Sat, 21 May 2022 12:45:00 +0200 Subject: [PATCH 08/25] fix loop? --- content/wcag2.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/wcag2.md b/content/wcag2.md index 4db8020e..cbb728e0 100644 --- a/content/wcag2.md +++ b/content/wcag2.md @@ -12,7 +12,8 @@ github: --- {% for requirement in site.data.wcag-act-rules.requirements %} - -## {{ requirement.num }} {{ requirement.handle }} +{%- assign scKey = requirement[0] %} +{%- assign criterion = requirement[1] %} +

{{ criterion.num }} {{ criterion.handle }}

{% endfor %} \ No newline at end of file From b26581b09d76073080a937af58990794cae74043 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Mon, 23 May 2022 11:13:23 +0200 Subject: [PATCH 09/25] Update index page --- content/index.md | 43 ++++++++++++++++++++++++++++--------------- 1 file changed, 28 insertions(+), 15 deletions(-) diff --git a/content/index.md b/content/index.md index 62490296..7daa3f00 100755 --- a/content/index.md +++ b/content/index.md @@ -1,6 +1,6 @@ --- layout: standalone_resource -title: "All WCAG 2 Test Rules" +title: "All ACT Rules" permalink: /standards-guidelines/act/rules/ ref: /standards-guidelines/act/rules/ lang: en @@ -15,33 +15,46 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -WCAG 2 Test Rules describe how to test conformance to Web Content Accessibility Guidelines (WCAG) success criteria. They are primarily for developers of evaluation tools and test methodologies. Learn more from [About WCAG 2 Test Rules](/standards-guidelines/act/rules/about/). +ACT Rules describe how to test conformance of accessibility standards such as Web Content Accessibility Guidelines (WCAG). They are primarily for accessibility testers, and for developers of test tools and methodologies. Learn more from [About WCAG 2 Test Rules](/standards-guidelines/act/rules/about/). -This page lists Test Rules formally published by the W3C Accessibility Guidelines Working Group (AG WG), and Proposed Test Rules. Additional Rules are in development and will be listed on this page when published. +This page lists WCAG 2 Rules, and other ACT Rules. WCAG 2 Rules are formally approved by the Accessibility Guidelines Working Group (AG WG). Proposed rules are have not yet gone through the complete approval process. {::nomarkdown} {% include box.html type="end" %} {:/} -## Test Rules -These Test Rules have been approved by the Accessibility Guidelines Working Group. They are fully implemented in at least one evaluation tool or methodology. +## Rules for WCAG 2 + +These ACT Rules are used to test conformance issues of Web Content Accessibility Guidelines (WCAG) version 2.0 and 2.1. These rules have been approved by the Accessibility Guidelines Working Group. They are fully implemented in at least one evaluation tool or methodology. + +
    +{%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} + {%- if rule.proposed == false and rule.successCriteria.size > 0 %} +
  • {{ rule.title }}
    • + {%- endif %} +{%- endfor %} +
+ +## Proposed Rules for WCAG 2 + +These ACT Rules are used to test conformance issues of Web Content Accessibility Guidelines (WCAG) version 2.0 and 2.1. These rules will be considered for approval once they are fully implemented in at least one evaluation tool or methodology.
    -{% for rule in site.data.wcag-act-rules.rules["act-rules"] %} - {% if rule.proposed == false %} +{%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} + {%- if rule.proposed == true and rule.successCriteria.size > 0 %}
  • {{ rule.title }}
    • - {% endif %} -{% endfor %} + {%- endif %} +{%- endfor %}
-## Proposed Test Rules +## Other Proposed ACT Rules -Proposed test rules will be published when they have at least one implementation and are approved by the AGWG. +These ACT Rules are **not** required for conformance to WCAG. They are part of various other accessibility standards and best practices, such as [WAI-ARIA](https://www.w3.org/TR/wai-aria/) and [Techniques for WCAG 2](https://www.w3.org/WAI/WCAG21/Techniques/). These rules will be considered for approval once they are fully implemented in at least one evaluation tool or methodology.
    -{% for rule in site.data.wcag-act-rules.rules["act-rules"] %} - {% if rule.proposed == true %} +{%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} + {%- if rule.successCriteria.size == 0 %}
  • {{ rule.title }}
    • - {% endif %} -{% endfor %} + {%- endif %} +{%- endfor %}
From 355b46f66f2aba15bef4e5968994807944a70c95 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Mon, 23 May 2022 11:27:37 +0200 Subject: [PATCH 10/25] Tweak index language --- content/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/index.md b/content/index.md index 7daa3f00..8f4bb7d7 100755 --- a/content/index.md +++ b/content/index.md @@ -15,9 +15,9 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -ACT Rules describe how to test conformance of accessibility standards such as Web Content Accessibility Guidelines (WCAG). They are primarily for accessibility testers, and for developers of test tools and methodologies. Learn more from [About WCAG 2 Test Rules](/standards-guidelines/act/rules/about/). +ACT Rules describe how to test conformance of accessibility standards such as Web Content Accessibility Guidelines (WCAG). They are primarily for accessibility testers, and for developers of test tools and methodologies. -This page lists WCAG 2 Rules, and other ACT Rules. WCAG 2 Rules are formally approved by the Accessibility Guidelines Working Group (AG WG). Proposed rules are have not yet gone through the complete approval process. +ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group (AG WG). Proposed rules are have not yet gone through the complete approval process. Learn more from [About ACT Rules](/standards-guidelines/act/rules/about/). {::nomarkdown} {% include box.html type="end" %} From a061b8ef890dae30a8d8952dcbee01b7d8ef71ca Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Mon, 23 May 2022 12:23:10 +0200 Subject: [PATCH 11/25] Update about page text --- content/about.md | 50 +++++++++++++++++++++++------------------------- content/index.md | 4 +--- 2 files changed, 25 insertions(+), 29 deletions(-) diff --git a/content/about.md b/content/about.md index b109837d..2d62b45e 100644 --- a/content/about.md +++ b/content/about.md @@ -1,6 +1,6 @@ --- layout: standalone_resource -title: "About WCAG 2 Test Rules" +title: "About ACT Rules" permalink: /standards-guidelines/act/rules/about/ ref: /standards-guidelines/act/rules/about/ lang: en @@ -13,66 +13,64 @@ github: {::nomarkdown} {% include box.html type="start" title="Summary" %} {:/} -WCAG 2 Test Rules describe how to test conformance to Web Content Accessibility Guidelines (WCAG) success criteria. The Test Rules are informative — that means they are not required for determining conformance to WCAG. WCAG 2 Test Rules are primarily for developers of evaluation tools and test methodologies. +ACT Rules describe how to test conformance of accessibility standards such as Web Content Accessibility Guidelines (WCAG) and WAI-ARIA. ACT Rules are informative — that means they are not required for determining conformance to WCAG or ARIA. -Guidance for others is in Understanding WCAG and WCAG Techniques. **Learn about the different WCAG support material from [The WCAG 2 Documents {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/docs/).** +ACT Rules are primarily to inform testers on how to handle edge cases in way that is consistent with other accessibility testers, test tools, and methodologies. {::nomarkdown} {% include box.html type="end" %} {:/} +For more information on WCAG 2, visit the [The WCAG 2 Documents {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/docs/). For information on how to apply WAI-ARIA, visit [ARIA Authoring Practices {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/ARIA/apg/). + The [List of Test Rules for WCAG 2](https://www.w3.org/WAI/standards-guidelines/act/rules/) is updated periodically. The rules are developed according to the [Accessibility Conformance Testing (ACT) Rules Format 1.0 {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/act/) standard. [Understanding Conformance](https://www.w3.org/WAI/WCAG22/Understanding/conformance) provides related information, including on [understanding accessibility support](https://www.w3.org/WAI/WCAG22/Understanding/conformance#accessibility-support). -## Test Rules are Informative +## ACT Rules are Informative -*WCAG 2 Test Rules are informative — that means they are not required for determining conformance. The basis for determining conformance to WCAG is the success criteria from the WCAG standard — not the Test Rules.* +*ACT Rules are informative — that means they are not required for determining conformance. The basis for determining conformance to WCAG is the success criteria from the WCAG standard — not the ACT Rules.* -While W3C's [List of Test Rules for WCAG 2](https://www.w3.org/WAI/standards-guidelines/act/rules/) are reviewed by the W3C Accessibility Guidelines Working Group (AGWG), they are not vetted to the same degree as the W3C Web Content Accessibility Guidelines (WCAG) standard (called *W3C Recommendation*). The WCAG standard is the normative reference on determining conformance. +While W3C's [List of ACT Rules for WCAG 2](https://www.w3.org/WAI/standards-guidelines/act/rules/) are reviewed by the W3C Accessibility Guidelines Working Group (AGWG), they are not vetted to the same degree as the W3C Web Content Accessibility Guidelines (WCAG) standard (called *W3C Recommendation*). The WCAG standard is the normative reference on determining conformance. -## Test Rules are Partial Checks +## ACT Rules are Partial Checks -Test Rules typically check specific aspects of WCAG success criteria. For example, that a table cell has a header rather than the entire WCAG 2.2 success criterion 1.3.1 "Info and Relationships", which applies to many more information structures on a web page. In fact, this example rule would not even check the validity of the table header, only if the header exists for a given table cell. +ACT Rules typically check specific accessibility requirement such as the WCAG 2 success criteria. For example, an ACT Rule might test that a table cell has a header, rather than testing success criterion 1.3.1 "Info and Relationships" in its entirety. In fact, this example rule would not even check the validity of the table header, only if the header exists for a given table cell. -Test Rules are also technology-specific. For example, the aforementioned table header example would be specific to HTML, possibly enriched with WAI-ARIA roles and properties, but not to other formats with tables. WCAG 2.2 success criteria are designed to be technology-agnostic and applicable to all web technologies. +ACT Rules are also technology-specific. For example, the aforementioned table header example would be specific to HTML, possibly enriched with WAI-ARIA roles and properties, but not to other technologies with tables. WCAG 2 success criteria are designed to be technology-agnostic and applicable to all web technologies. -## Test Rules Check for Failures +## ACT Rules Check for Failures -Test Rules are designed to check failures in satisfying WCAG success criteria. That is, when content fails Test Rules, it means that the content does not satisfy the corresponding success criteria. However, when content passes Test Rules, it means that no corresponding failures were detected — it does not necessarily mean that the content satisfies all aspects of the corresponding success criteria. +ACT Rules are designed to check failures in satisfying WCAG 2 success criteria and other accessibility requirements. That is, when content fails ACT Rules, it means that the content does not satisfy the corresponding requirement. However, when content passes ACT Rules, it means that no corresponding failures were detected — it does not necessarily mean that the content satisfies all aspects of the corresponding accessibility requirement. -The reason for this is because WCAG success criteria typically cover several aspects and technologies, while Test Rules only check specific aspects. Checking that content satisfies all aspects of WCAG success criteria typically requires further verification by human testers. +WCAG success criteria typically cover several aspects and technologies, while ACT Rules only check specific aspects. Checking that content satisfies all aspects of WCAG success criteria typically requires further verification by human testers. Requirements for WAI-ARIA are often more atomic than the WCAG 2 success criteria, and can therefor often be fully covered with ACT Rules. **Note**: [WCAG 2 Conformance Requirement 1](https://www.w3.org/WAI/WCAG22/Understanding/conformance#cc1) allows for "conforming alternate versions". That means that content may still conform to WCAG 2, even when content fails Test Rules. -## Implementation of Test Rules - -Implementation of a Test Rule can be any automated testing tool, manual testing methodology, or other procedure that provides the same expected results for the test cases defined by the Test Rule. Specifically, when the expected result for a test case is: +## Implementation of ACT Rules -- **Passed**, the test result generated from the implementation is *passed*, *cantTell*, or *inapplicable* -- **Failed**, the test result generated from the implementation is *failed* or *cantTell* -- **Inapplicable**, the test result generated from the implementation is *inapplicable*, *cantTell*, or *passed* +ACT Rules can be implemented by accessibility test tools and methodologies. Each rule comes with a number of passed, failed, and inapplicable examples. By running the tool or methodology against the examples its consistency with the rule can be determined. Vendors who publish such test results are included in the [ACT Test Tools and Methodology Matrix](../implementations/). -## Structure of Test Rules +## Structure of ACT Rules -Test Rules conform to the [Accessibility Conformance Testing (ACT) Rules Format 1.0](https://www.w3.org/WAI/standards-guidelines/act/) standard. They include the following parts: +ACT Rules conform to the [Accessibility Conformance Testing (ACT) Rules Format 1.0](https://www.w3.org/WAI/standards-guidelines/act/) standard. They include the following parts: - **Descriptive Title** – title for the Test Rule, which should describe the rule - **Rule Identifier** – identifier for the Test Rule; the rules use alphanumeric strings - **Rule Type** – there are two basic types of Test Rules, depending on what is being tested: - **Atomic Rule** – test one specific situation, which may be part of a composite rule - **Composite Rule** – combine outcome from multiple atomic rules to one outcome -- **Accessibility Requirements Mapping** – maps the Test Rule to particular accessibility requirements; in this suite of rules we use Web Content Accessibility Guidelines (WCAG) 2 Success Criteria -- **Rule Input** – describes the scope of input into Test Rules, which is one of the following: +- **Accessibility Requirements Mapping** – maps the ACT Rule to particular accessibility requirements; in this suite of rules we use Web Content Accessibility Guidelines (WCAG) 2 Success Criteria +- **Rule Input** – describes the scope of input into ACT Rules, which is one of the following: - **Input Aspects** – input into atomic rules, for example DOM Tree and CSS Styling etc. - **Input Rules** – input into the composite rules, which are the atomic rules in scope - **Applicability** – description of the specific parts of the content, for which the rule applies - **Expectations** – description of the expected characteristics of the applicable rule content - **Assumptions** – assumptions made, for example specific interpretations of the requirements - **Accessibility Support** – known limitations regarding browsers and assistive technology -- **Test Cases** – sample code demonstrating passed, failed, and inapplicable rule conditions -- **Change Log** – history of changes for the Test Rules, to support backward compatibility -- **Glossary** – list of key terms defined by the Test Rule or used by the specific Test Rule -- **Issues List (Optional)** – list of known issues or bugs for the particular Test Rule, if any +- **Examples (Test Cases)** – sample code demonstrating passed, failed, and inapplicable rule conditions +- **Change Log** – history of changes for the ACT Rules, to support backward compatibility +- **Glossary** – list of key terms defined by the ACT Rule or used by the specific ACT Rule +- **Issues List (Optional)** – list of known issues or bugs for the particular ACT Rule, if any - **Background (Optional)** – relevant background, for example additional documentation, if any - **Acknowledgements (Optional)** – for example rule writers, reviewers, and other contributors diff --git a/content/index.md b/content/index.md index 8f4bb7d7..4b153f9c 100755 --- a/content/index.md +++ b/content/index.md @@ -15,9 +15,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -ACT Rules describe how to test conformance of accessibility standards such as Web Content Accessibility Guidelines (WCAG). They are primarily for accessibility testers, and for developers of test tools and methodologies. - -ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group (AG WG). Proposed rules are have not yet gone through the complete approval process. Learn more from [About ACT Rules](/standards-guidelines/act/rules/about/). +ACT Rules describe how to test conformance of accessibility standards such as Web Content Accessibility Guidelines (WCAG). They are primarily for accessibility testers and for creators of test tools and methodologies. ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group (AG WG). Proposed rules are have not yet gone through the complete approval process. Learn more from [About ACT Rules](/standards-guidelines/act/rules/about/). {::nomarkdown} {% include box.html type="end" %} From 047b7e73f33538e39c1980b09cc9ad937859d5ef Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Mon, 23 May 2022 12:34:56 +0200 Subject: [PATCH 12/25] More editorial work --- content/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/index.md b/content/index.md index 4b153f9c..de824d8f 100755 --- a/content/index.md +++ b/content/index.md @@ -15,7 +15,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -ACT Rules describe how to test conformance of accessibility standards such as Web Content Accessibility Guidelines (WCAG). They are primarily for accessibility testers and for creators of test tools and methodologies. ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group (AG WG). Proposed rules are have not yet gone through the complete approval process. Learn more from [About ACT Rules](/standards-guidelines/act/rules/about/). +ACT Rules describe how to test conformance of accessibility standards such as [Web Content Accessibility Guidelines (WCAG) {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/) and [WAI-ARIA {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/ARIA/). They are primarily for accessibility testers and for creators of test tools and methodologies. ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group (AG WG). Proposed rules are have not yet gone through the complete approval process. Learn more from [About ACT Rules](/standards-guidelines/act/rules/about/). {::nomarkdown} {% include box.html type="end" %} @@ -23,11 +23,11 @@ ACT Rules describe how to test conformance of accessibility standards such as We ## Rules for WCAG 2 -These ACT Rules are used to test conformance issues of Web Content Accessibility Guidelines (WCAG) version 2.0 and 2.1. These rules have been approved by the Accessibility Guidelines Working Group. They are fully implemented in at least one evaluation tool or methodology. +These ACT Rules are used to test conformance issues of WCAG 2.0 or 2.1. These rules have been approved by the Accessibility Guidelines Working Group. They are fully implemented in at least one evaluation tool or methodology.
    {%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} - {%- if rule.proposed == false and rule.successCriteria.size > 0 %} + {%- if rule.proposed == false %}
  • {{ rule.title }}
    • {%- endif %} {%- endfor %} @@ -35,7 +35,7 @@ These ACT Rules are used to test conformance issues of Web Content Accessibility ## Proposed Rules for WCAG 2 -These ACT Rules are used to test conformance issues of Web Content Accessibility Guidelines (WCAG) version 2.0 and 2.1. These rules will be considered for approval once they are fully implemented in at least one evaluation tool or methodology. +These ACT Rules are used to test conformance issues of WCAG 2.0 or 2.1. These rules will be considered for approval once they are fully implemented in at least one evaluation tool or methodology.
      {%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} From f759168a855ef357652febeb4453b7d280b57587 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Mon, 23 May 2022 12:35:34 +0200 Subject: [PATCH 13/25] Delete wcag2 doodle page --- content/wcag2.md | 19 ------------------- 1 file changed, 19 deletions(-) delete mode 100644 content/wcag2.md diff --git a/content/wcag2.md b/content/wcag2.md deleted file mode 100644 index cbb728e0..00000000 --- a/content/wcag2.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -layout: standalone_resource -title: "ACT Rules for WCAG 2" -permalink: /standards-guidelines/act/wcag2/ -ref: /standards-guidelines/act/wcag2/ -lang: en -type_of_guidance: false -footer: "" -github: - repository: w3c/wcag-act-rules - path: content/wcag2.md ---- - -{% for requirement in site.data.wcag-act-rules.requirements %} -{%- assign scKey = requirement[0] %} -{%- assign criterion = requirement[1] %} -

      {{ criterion.num }} {{ criterion.handle }}

      - -{% endfor %} \ No newline at end of file From 3809f07fd360188dd2c4a51a201397505a473f17 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Mon, 23 May 2022 12:54:34 +0200 Subject: [PATCH 14/25] More editorial work --- _config.yml | 4 ++-- content/about.md | 40 +++++++++++++++++++++++++------------- content/implementations.md | 2 +- content/index.md | 13 +++++++++---- 4 files changed, 38 insertions(+), 21 deletions(-) diff --git a/_config.yml b/_config.yml index ea7b4aa2..4777b1b4 100755 --- a/_config.yml +++ b/_config.yml @@ -54,9 +54,9 @@ defaults:

      Date: Updated @@ Month 2021. First published Month 20@@.

      Editors: @@name, @@name. Contributors: @@name, @@name, and participants of the @@WG. ACKNOWLEDGEMENTS lists contributors and credits.

      Developed by the @@ Working Group (@@WG). Developed as part of the WAI-@@ project, @@co-funded by the European Commission.

      - type_of_guidance: "Test Rule" + type_of_guidance: "ACT Rule" rule_meta: - rule_type: "atomic rule" + rule_type: "Atomic rule" sidebar: true standalone_resource_header: title: Accessibility Conformance Testing (ACT) diff --git a/content/about.md b/content/about.md index 2d62b45e..7642b409 100644 --- a/content/about.md +++ b/content/about.md @@ -1,4 +1,5 @@ --- +doc-note-type: draft layout: standalone_resource title: "About ACT Rules" permalink: /standards-guidelines/act/rules/about/ @@ -11,53 +12,64 @@ github: path: content/about.md --- -{::nomarkdown} {% include box.html type="start" title="Summary" %} {:/} +
      +

      This page is under development and has not been approved by the working group.

      +
      -ACT Rules describe how to test conformance of accessibility standards such as Web Content Accessibility Guidelines (WCAG) and WAI-ARIA. ACT Rules are informative — that means they are not required for determining conformance to WCAG or ARIA. +{::nomarkdown} +{% include box.html type="start" title="Summary" class="" %} +{:/} -ACT Rules are primarily to inform testers on how to handle edge cases in way that is consistent with other accessibility testers, test tools, and methodologies. +ACT Rules describe how to test conformance of accessibility standards such as [Web Content Accessibility Guidelines (WCAG) {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/) and [WAI-ARIA {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/ARIA/). ACT Rules inform accessibility testers on how to evaluate edge cases in way that is consistent with other accessibility testers, test tools, and methodologies. ACT Rules are informative — that means they are not required for determining conformance to WCAG or ARIA. {::nomarkdown} {% include box.html type="end" %} {:/} -For more information on WCAG 2, visit the [The WCAG 2 Documents {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/docs/). For information on how to apply WAI-ARIA, visit [ARIA Authoring Practices {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/ARIA/apg/). - -The [List of Test Rules for WCAG 2](https://www.w3.org/WAI/standards-guidelines/act/rules/) is updated periodically. The rules are developed according to the [Accessibility Conformance Testing (ACT) Rules Format 1.0 {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/act/) standard. +## What are ACT Rules -[Understanding Conformance](https://www.w3.org/WAI/WCAG22/Understanding/conformance) provides related information, including on [understanding accessibility support](https://www.w3.org/WAI/WCAG22/Understanding/conformance#accessibility-support). +ACT Rules are designed to harmonize how edge cases for WCAG and other accessibility guidance are tested. Each ACT Rule describes in technology specific language how to test one particular aspect of a WCAG success criterion or other requirement. Rules have passed, failed, and inapplicable examples which can be used as test cases to determine the consistency of [test tools and methodologies](../implementations/). -## ACT Rules are Informative +### ACT Rules are Informative *ACT Rules are informative — that means they are not required for determining conformance. The basis for determining conformance to WCAG is the success criteria from the WCAG standard — not the ACT Rules.* While W3C's [List of ACT Rules for WCAG 2](https://www.w3.org/WAI/standards-guidelines/act/rules/) are reviewed by the W3C Accessibility Guidelines Working Group (AGWG), they are not vetted to the same degree as the W3C Web Content Accessibility Guidelines (WCAG) standard (called *W3C Recommendation*). The WCAG standard is the normative reference on determining conformance. -## ACT Rules are Partial Checks +### ACT Rules are Partial Checks ACT Rules typically check specific accessibility requirement such as the WCAG 2 success criteria. For example, an ACT Rule might test that a table cell has a header, rather than testing success criterion 1.3.1 "Info and Relationships" in its entirety. In fact, this example rule would not even check the validity of the table header, only if the header exists for a given table cell. ACT Rules are also technology-specific. For example, the aforementioned table header example would be specific to HTML, possibly enriched with WAI-ARIA roles and properties, but not to other technologies with tables. WCAG 2 success criteria are designed to be technology-agnostic and applicable to all web technologies. -## ACT Rules Check for Failures +### ACT Rules Check for Failures ACT Rules are designed to check failures in satisfying WCAG 2 success criteria and other accessibility requirements. That is, when content fails ACT Rules, it means that the content does not satisfy the corresponding requirement. However, when content passes ACT Rules, it means that no corresponding failures were detected — it does not necessarily mean that the content satisfies all aspects of the corresponding accessibility requirement. WCAG success criteria typically cover several aspects and technologies, while ACT Rules only check specific aspects. Checking that content satisfies all aspects of WCAG success criteria typically requires further verification by human testers. Requirements for WAI-ARIA are often more atomic than the WCAG 2 success criteria, and can therefor often be fully covered with ACT Rules. -**Note**: [WCAG 2 Conformance Requirement 1](https://www.w3.org/WAI/WCAG22/Understanding/conformance#cc1) allows for "conforming alternate versions". That means that content may still conform to WCAG 2, even when content fails Test Rules. +**Note**: [WCAG 2 Conformance Requirement 1](https://www.w3.org/WAI/WCAG22/Understanding/conformance#cc1) allows for "conforming alternate versions". That means that content may still conform to WCAG 2, even when content fails ACT Rules. ## Implementation of ACT Rules ACT Rules can be implemented by accessibility test tools and methodologies. Each rule comes with a number of passed, failed, and inapplicable examples. By running the tool or methodology against the examples its consistency with the rule can be determined. Vendors who publish such test results are included in the [ACT Test Tools and Methodology Matrix](../implementations/). +## Related Pages + +- [Accessibility Conformance Testing (ACT) Rules Format 1.0 {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/act/) +- [The WCAG 2 Documents {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/docs/) +- [Understanding WCAG 2 Conformance](https://www.w3.org/WAI/WCAG22/Understanding/conformance) +- [understanding accessibility support](https://www.w3.org/WAI/WCAG22/Understanding/conformance#accessibility-support) +- [ARIA Authoring Practices {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/ARIA/apg/) +- [Web Accessibility Evaluation Tools List](https://www.w3.org/WAI/ER/tools/) + ## Structure of ACT Rules ACT Rules conform to the [Accessibility Conformance Testing (ACT) Rules Format 1.0](https://www.w3.org/WAI/standards-guidelines/act/) standard. They include the following parts: -- **Descriptive Title** – title for the Test Rule, which should describe the rule -- **Rule Identifier** – identifier for the Test Rule; the rules use alphanumeric strings -- **Rule Type** – there are two basic types of Test Rules, depending on what is being tested: +- **Descriptive Title** – title for the ACT Rule, which should describe the rule +- **Rule Identifier** – identifier for the ACT Rule; the rules use alphanumeric strings +- **Rule Type** – there are two basic types of ACT Rules, depending on what is being tested: - **Atomic Rule** – test one specific situation, which may be part of a composite rule - **Composite Rule** – combine outcome from multiple atomic rules to one outcome - **Accessibility Requirements Mapping** – maps the ACT Rule to particular accessibility requirements; in this suite of rules we use Web Content Accessibility Guidelines (WCAG) 2 Success Criteria diff --git a/content/implementations.md b/content/implementations.md index a080deea..689e2240 100644 --- a/content/implementations.md +++ b/content/implementations.md @@ -71,6 +71,6 @@ For information on how to add your accessibility test tool or methodology to the Inclusion of tools and methodologies in these tables does not indicate endorsement by W3C. Tools and figures are listed for informational purposes only. -Information in these pages is derived from data published by the vendors behind these tools and methodologies. Only tools and methodologies for which public data is available can be listed on this page. Tools and methodologies often have test procedures not yet described using ACT Rules. These are not included in the implementation reports. +Information in these pages is derived from data published by the vendors behind these tools and methodologies. Only tools and methodologies for which public data is available can be listed on this page. Tools and methodologies often have test procedures not yet described using ACT Rules. These are not included in the implementation reports. More information about these and other tools can be found on the [Web Accessibility Evaluation Tools List](https://www.w3.org/WAI/ER/tools/). The data is taken as-is, and is not verified by the W3C. If there are any questions or concerns about the information on these pages, [open an issue on GitHub](https://github.com/w3c/wcag-act-rules/issues/new) or e-mail [wai@w3.org](mailto:wai@w3.org?subject=[en]%20Accessibility%20Test%20Tools%20&%20Methodologies). diff --git a/content/index.md b/content/index.md index de824d8f..0a704f20 100755 --- a/content/index.md +++ b/content/index.md @@ -1,4 +1,5 @@ --- +doc-note-type: draft layout: standalone_resource title: "All ACT Rules" permalink: /standards-guidelines/act/rules/ @@ -11,11 +12,15 @@ github: path: content/index.md --- +
      +

      This page is under development and has not been approved by the working group.

      +
      + {::nomarkdown} {% include box.html type="start" title="Summary" class="" %} {:/} -ACT Rules describe how to test conformance of accessibility standards such as [Web Content Accessibility Guidelines (WCAG) {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/) and [WAI-ARIA {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/ARIA/). They are primarily for accessibility testers and for creators of test tools and methodologies. ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group (AG WG). Proposed rules are have not yet gone through the complete approval process. Learn more from [About ACT Rules](/standards-guidelines/act/rules/about/). +This page contains list of ACT Rules to test conformance [Web Content Accessibility Guidelines (WCAG) {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/), [WAI-ARIA {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/ARIA/) and other accessibility practices. ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group. Proposed rules have not yet completed the approval process. Learn more from [About ACT Rules](/standards-guidelines/act/rules/about/). {::nomarkdown} {% include box.html type="end" %} @@ -23,7 +28,7 @@ ACT Rules describe how to test conformance of accessibility standards such as [W ## Rules for WCAG 2 -These ACT Rules are used to test conformance issues of WCAG 2.0 or 2.1. These rules have been approved by the Accessibility Guidelines Working Group. They are fully implemented in at least one evaluation tool or methodology. +These ACT Rules are used to test conformance issues of WCAG 2.0 or 2.1. These rules have been approved by the Accessibility Guidelines Working Group. They are fully implemented in at least one [test tool or methodology](../implementations/).
        {%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} @@ -35,7 +40,7 @@ These ACT Rules are used to test conformance issues of WCAG 2.0 or 2.1. These ru ## Proposed Rules for WCAG 2 -These ACT Rules are used to test conformance issues of WCAG 2.0 or 2.1. These rules will be considered for approval once they are fully implemented in at least one evaluation tool or methodology. +These ACT Rules are used to test conformance issues of WCAG 2.0 or 2.1. These rules will be considered for approval once they are fully implemented in at least one test tool or methodology.
          {%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} @@ -47,7 +52,7 @@ These ACT Rules are used to test conformance issues of WCAG 2.0 or 2.1. These ru ## Other Proposed ACT Rules -These ACT Rules are **not** required for conformance to WCAG. They are part of various other accessibility standards and best practices, such as [WAI-ARIA](https://www.w3.org/TR/wai-aria/) and [Techniques for WCAG 2](https://www.w3.org/WAI/WCAG21/Techniques/). These rules will be considered for approval once they are fully implemented in at least one evaluation tool or methodology. +These ACT Rules are **not** required for conformance to WCAG. They are part of various other accessibility standards and best practices, such as [WAI-ARIA {% include_cached icon.html name="different-view" %}](https://www.w3.org/TR/wai-aria/) and [Techniques for WCAG 2 {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/WCAG21/Techniques/). These rules will be considered for approval once they are fully implemented in at least one test tool or methodology.
            {%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} From 2dd7c7dad4763c1a095d2eaf955faeafe652328d Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Thu, 26 May 2022 17:36:46 +0200 Subject: [PATCH 15/25] Fix incorrect inline linke --- _layouts/act_implementation.html | 4 ++-- content/implementations.md | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/_layouts/act_implementation.html b/_layouts/act_implementation.html index 35e5cf00..8f30074f 100644 --- a/_layouts/act_implementation.html +++ b/_layouts/act_implementation.html @@ -50,7 +50,7 @@ , and {{ standard }} {%- endif -%} {%- endfor %}. - See understanding ACT consistency. + See understanding ACT consistency.

            @@ -166,7 +166,7 @@

            {{ ruleMapping.ruleName | remove: '` {% else %} The implementation correctly reports no success criteria are failed by this rule. {% endif %} - See understanding ACT consistency. + See understanding ACT consistency.

            {% if ruleMapping.accessibilityRequirements %} diff --git a/content/implementations.md b/content/implementations.md index 689e2240..d1eea28c 100644 --- a/content/implementations.md +++ b/content/implementations.md @@ -20,13 +20,13 @@ github: {::nomarkdown} {% include box.html type="start" title="Summary" %} {:/} -The tables on these pages show how many ACT Rules different accessibility test tools and methodologies have consistently implemented. Each implementation links to a report with more details on how rules are implemented. See [understanding ACT consistency](#understandingactconsistency) for details. +The tables on these pages show how many ACT Rules different accessibility test tools and methodologies have consistently implemented. Each implementation links to a report with more details on how rules are implemented. See [understanding ACT consistency](#understanding-act-consistency) for details. {::nomarkdown} {% include box.html type="end" %} {:/} ## Test Methodologies Test methodologies provide step by step instructions on how to test accessibility standards. -See [understanding ACT consistency](#understandingactconsistency) for details. +See [understanding ACT consistency](#understanding-act-consistency) for details. {% assign methodologies = implementations | where: "type", "Test methodology" %} {% include_relative _implementations-table.html implementations=methodologies %} @@ -34,7 +34,7 @@ See [understanding ACT consistency](#understandingactconsistency) for details. ## Semi-automated Test Tools Tools that combine user input and automated testing to test accessibility standards. -See [understanding ACT consistency](#understandingactconsistency) for details. +See [understanding ACT consistency](#understanding-act-consistency) for details. {% assign semiAutoTools = implementations | where: "type", "Semi-automated tool" %} {% include_relative _implementations-table.html implementations=semiAutoTools %} @@ -42,7 +42,7 @@ See [understanding ACT consistency](#understandingactconsistency) for details. ## Automated Test Tools Automated tools test accessibility standards fully automatically. -See [understanding ACT consistency](#understandingactconsistency) for details. +See [understanding ACT consistency](#understanding-act-consistency) for details. {% assign automatedTools = implementations | where: "type", "Automated tool" %} {% include_relative _implementations-table.html implementations=automatedTools %} From 58969174fe73f794d6920474966fff888a21c03a Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Tue, 7 Jun 2022 14:47:57 +0200 Subject: [PATCH 16/25] Various textual changes --- _config.yml | 6 +++--- content/about.md | 2 +- content/implementations.md | 2 +- content/index.md | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/_config.yml b/_config.yml index 4777b1b4..860669ba 100755 --- a/_config.yml +++ b/_config.yml @@ -59,15 +59,15 @@ defaults: rule_type: "Atomic rule" sidebar: true standalone_resource_header: - title: Accessibility Conformance Testing (ACT) + title: ACT Rules title-ref: /standards-guidelines/act/rules/ - subtitle: Harmonised rules for WCAG 2 & ARIA + subtitle: Rules for accessibility conformance testing (ACT) standalone_resource_nav_links: - name: All Rules ref: /standards-guidelines/act/rules/ - name: About ref: /standards-guidelines/act/rules/about/ - - name: Test Tools & Methodologies + - name: Implementations in Tools and Methodologies ref: /standards-guidelines/act/implementations/ plugins: diff --git a/content/about.md b/content/about.md index 7642b409..bb669fbf 100644 --- a/content/about.md +++ b/content/about.md @@ -46,7 +46,7 @@ ACT Rules are also technology-specific. For example, the aforementioned table he ACT Rules are designed to check failures in satisfying WCAG 2 success criteria and other accessibility requirements. That is, when content fails ACT Rules, it means that the content does not satisfy the corresponding requirement. However, when content passes ACT Rules, it means that no corresponding failures were detected — it does not necessarily mean that the content satisfies all aspects of the corresponding accessibility requirement. -WCAG success criteria typically cover several aspects and technologies, while ACT Rules only check specific aspects. Checking that content satisfies all aspects of WCAG success criteria typically requires further verification by human testers. Requirements for WAI-ARIA are often more atomic than the WCAG 2 success criteria, and can therefor often be fully covered with ACT Rules. +WCAG success criteria typically cover several aspects and technologies, while ACT Rules only check specific aspects. Checking that content satisfies all aspects of WCAG success criteria typically requires further verification by human testers. Requirements for WAI-ARIA are often more atomic than the WCAG 2 success criteria, and can therefore often be fully covered with ACT Rules. **Note**: [WCAG 2 Conformance Requirement 1](https://www.w3.org/WAI/WCAG22/Understanding/conformance#cc1) allows for "conforming alternate versions". That means that content may still conform to WCAG 2, even when content fails ACT Rules. diff --git a/content/implementations.md b/content/implementations.md index f8c7a1e6..58a0927e 100644 --- a/content/implementations.md +++ b/content/implementations.md @@ -1,7 +1,7 @@ --- doc-note-type: draft layout: standalone_resource -title: "Test Tool & Methodology Matrix" +title: "ACT Rules Implementation in Test Tools and Methodologies" permalink: /standards-guidelines/act/implementations/ ref: /standards-guidelines/act/implementations/ lang: en diff --git a/content/index.md b/content/index.md index 0a704f20..0fb69665 100755 --- a/content/index.md +++ b/content/index.md @@ -20,7 +20,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -This page contains list of ACT Rules to test conformance [Web Content Accessibility Guidelines (WCAG) {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/), [WAI-ARIA {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/ARIA/) and other accessibility practices. ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group. Proposed rules have not yet completed the approval process. Learn more from [About ACT Rules](/standards-guidelines/act/rules/about/). +This page contains list of ACT Rules for determining conformance to [Web Content Accessibility Guidelines (WCAG) {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/), [WAI-ARIA {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/ARIA/) and other accessibility practices. ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group. Proposed rules have not yet completed the approval process. ACT Rules are informative — that means they are not required for determining conformance to WCAG or ARIA. Learn more from [About ACT Rules](/standards-guidelines/act/rules/about/). {::nomarkdown} {% include box.html type="end" %} @@ -28,7 +28,7 @@ This page contains list of ACT Rules to test conformance [Web Content Accessibil ## Rules for WCAG 2 -These ACT Rules are used to test conformance issues of WCAG 2.0 or 2.1. These rules have been approved by the Accessibility Guidelines Working Group. They are fully implemented in at least one [test tool or methodology](../implementations/). +These ACT Rules are used to test conformance to WCAG 2.0 or 2.1. These rules have been approved by the Accessibility Guidelines Working Group. They are fully implemented in at least one [test tool or methodology](../implementations/).
              {%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} From 3cdf31afcd6685a8d5ec0ff55978b2386fec94d0 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Wed, 8 Jun 2022 12:59:01 +0200 Subject: [PATCH 17/25] More textual work --- _data/wcag-act-rules/act-implementations.yml | 14 +++++++------- content/index.md | 10 +++++----- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/_data/wcag-act-rules/act-implementations.yml b/_data/wcag-act-rules/act-implementations.yml index acdeadc0..c1b1f826 100644 --- a/_data/wcag-act-rules/act-implementations.yml +++ b/_data/wcag-act-rules/act-implementations.yml @@ -3,7 +3,7 @@ uniqueKey: alfa type: Automated tool standards: - - WCAG 2.1 all levels + - WCAG 2.1 Level A, AA, AAA - WAI-ARIA 1.2 jsonReport: https://raw.githubusercontent.com/Siteimprove/alfa-act-r/main/reports/alfa-w3c.json @@ -14,7 +14,7 @@ uniqueKey: axe-core type: Automated tool standards: - - WCAG 2.1 all levels + - WCAG 2.1 Level A, AA, AAA - WAI-ARIA 1.2 jsonReport: https://raw.githubusercontent.com/dequelabs/act-reports-axe/main/reports/axe-core.json description: | @@ -27,7 +27,7 @@ uniqueKey: axe-devtools-pro type: Semi-automated tool standards: - - WCAG 2.1 all levels + - WCAG 2.1 Level A, AA, AAA - WAI-ARIA 1.2 jsonReport: https://raw.githubusercontent.com/dequelabs/act-reports-axe/main/reports/axe-devtools-igt.json description: | @@ -43,7 +43,7 @@ uniqueKey: equal-access type: Automated tool standards: - - WCAG 2.1 all levels + - WCAG 2.1 Level A, AA, AAA - WAI-ARIA 1.2 jsonReport: https://raw.githubusercontent.com/IBMa/equal-access/master/accessibility-checker/test-act/earlResult.json description: | @@ -62,7 +62,7 @@ uniqueKey: qualweb type: Automated tool standards: - - WCAG 2.1 all levels + - WCAG 2.1 Level A, AA, AAA - WAI-ARIA 1.2 jsonReport: https://raw.githubusercontent.com/qualweb/ACT-implementation-report/main/qualweb-report.json @@ -72,7 +72,7 @@ uniqueKey: sort-site type: Automated tool standards: - - WCAG 2.1 all levels + - WCAG 2.1 Level A, AA, AAA - WAI-ARIA 1.2 jsonReport: https://raw.githubusercontent.com/act-rules/act-rules-implementation-sortsite/master/report.json @@ -81,5 +81,5 @@ uniqueKey: trusted-tester type: Test methodology standards: - - WCAG 2.0 Level A & AA + - WCAG 2.0 Level A, AA jsonReport: https://raw.githubusercontent.com/Section508Coordinators/act-tt/main/act-trusted-tester.json diff --git a/content/index.md b/content/index.md index 0fb69665..f15feedd 100755 --- a/content/index.md +++ b/content/index.md @@ -20,7 +20,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -This page contains list of ACT Rules for determining conformance to [Web Content Accessibility Guidelines (WCAG) {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/), [WAI-ARIA {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/ARIA/) and other accessibility practices. ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group. Proposed rules have not yet completed the approval process. ACT Rules are informative — that means they are not required for determining conformance to WCAG or ARIA. Learn more from [About ACT Rules](/standards-guidelines/act/rules/about/). +This page contains list of ACT Rules to test conformance [Web Content Accessibility Guidelines (WCAG) {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/standards-guidelines/wcag/), [WAI-ARIA {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/ARIA/) and other accessibility practices. ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group. Proposed rules have not yet completed the approval process. ACT Rules are informative — that means they are not required for determining conformance to WCAG or ARIA. Learn more from [About ACT Rules](/standards-guidelines/act/rules/about/). {::nomarkdown} {% include box.html type="end" %} @@ -28,7 +28,7 @@ This page contains list of ACT Rules for determining conformance to [Web Content ## Rules for WCAG 2 -These ACT Rules are used to test conformance to WCAG 2.0 or 2.1. These rules have been approved by the Accessibility Guidelines Working Group. They are fully implemented in at least one [test tool or methodology](../implementations/). +The ACT Rules in this section directly relate to WCAG 2 success criteria. These rules have been approved by the Accessibility Guidelines Working Group. They are fully implemented in at least one [test tool or methodology](../implementations/).
                {%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} @@ -40,7 +40,7 @@ These ACT Rules are used to test conformance to WCAG 2.0 or 2.1. These rules hav ## Proposed Rules for WCAG 2 -These ACT Rules are used to test conformance issues of WCAG 2.0 or 2.1. These rules will be considered for approval once they are fully implemented in at least one test tool or methodology. +The ACT Rules in this section directly relate to WCAG 2 success criteria. These rules will be considered for approval once they are fully implemented in at least one test tool or methodology.
                  {%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} @@ -50,9 +50,9 @@ These ACT Rules are used to test conformance issues of WCAG 2.0 or 2.1. These ru {%- endfor %}
                -## Other Proposed ACT Rules +## Rules beyond WCAG -These ACT Rules are **not** required for conformance to WCAG. They are part of various other accessibility standards and best practices, such as [WAI-ARIA {% include_cached icon.html name="different-view" %}](https://www.w3.org/TR/wai-aria/) and [Techniques for WCAG 2 {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/WCAG21/Techniques/). These rules will be considered for approval once they are fully implemented in at least one test tool or methodology. +The ACT Rules below do not directly relate to WCAG success criteria. They relate to other accessibility guidance such as [WAI-ARIA {% include_cached icon.html name="different-view" %}](https://www.w3.org/TR/wai-aria/) or [Techniques for WCAG 2 {% include_cached icon.html name="different-view" %}](https://www.w3.org/WAI/WCAG21/Techniques/). These rules will be considered for approval once they are fully implemented in at least one test tool or methodology.
                  {%- for rule in site.data.wcag-act-rules.rules["act-rules"] %} From 2cff52f92611871458c5bfd578ba5f78d10f8d16 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Wed, 8 Jun 2022 13:23:22 +0200 Subject: [PATCH 18/25] Style link icons --- content-assets/wcag-act-rules/act-styles.css | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content-assets/wcag-act-rules/act-styles.css b/content-assets/wcag-act-rules/act-styles.css index 9a7417e6..507348e8 100644 --- a/content-assets/wcag-act-rules/act-styles.css +++ b/content-assets/wcag-act-rules/act-styles.css @@ -6,6 +6,12 @@ table.act-implementations { width: 100%; } +table.act-implementations a > img { + padding: 0.25rem; + border-radius: 0.25em; + border: solid 1px var(--wai-green); +} + table.act-requirements ul, table.act-implementations ul { list-style: none; From abb720a9a91ac20619562d9b9506d51ec3e6d716 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Wed, 8 Jun 2022 15:47:30 +0200 Subject: [PATCH 19/25] Update links to implementations --- _data/wcag-act-rules/act-implementations.yml | 30 ++++++++++++++++++- .../implementations/axe-core.json | 1 - content/_implementations-table.html | 4 ++- 3 files changed, 32 insertions(+), 3 deletions(-) diff --git a/_data/wcag-act-rules/act-implementations.yml b/_data/wcag-act-rules/act-implementations.yml index c1b1f826..bca90380 100644 --- a/_data/wcag-act-rules/act-implementations.yml +++ b/_data/wcag-act-rules/act-implementations.yml @@ -1,5 +1,24 @@ +### EXAMPLE, using all permitted fields +### Fields with a * are optional +# - name: Acme Accessibility Tool +# homepage: https://acme.com/acme-tool/ * +# hidden: true # This lists the implementation as "coming soon". +# version: 4.5 * +# vendor: Acme Corp +# vendorHomepage: https://acme.com/ * +# uniqueKey: acme-tool +# type: Automated Tool | Semi-automated tool | Test methodology +# standards: # Add as needed, remove what is not applicable +# - WAI-ARIA 1.2 +# - WCAG 2.1 Level A, AA, AAA +# jsonReport: https://acme.com/acme-tool-earl.json +# description: | +# Some text here, which may contain markdown. * + - name: Alfa + homepage: https://alfa.siteimprove.com/ vendor: Siteimprove + vendorHomepage: https://www.siteimprove.com/ uniqueKey: alfa type: Automated tool standards: @@ -8,7 +27,8 @@ jsonReport: https://raw.githubusercontent.com/Siteimprove/alfa-act-r/main/reports/alfa-w3c.json - name: Axe-core - homepage: https://github.com/dequelabs/axe-core/ + homepage: https://www.npmjs.com/package/axe-core + version: 4.5-prerelease vendor: Deque Systems vendorHomepage: https://deque.com/ uniqueKey: axe-core @@ -23,7 +43,9 @@ Checks with “unsupported” in its ID are disabled, which deal with issues of accessibility support issues which ACT Rules do not account for, often by design. - name: Axe DevTools Pro + homepage: https://www.deque.com/axe/devtools/ vendor: Deque Systems + vendorHomepage: https://deque.com/ uniqueKey: axe-devtools-pro type: Semi-automated tool standards: @@ -38,8 +60,10 @@ the `alt-text-not-meaningful` issue type reported by the `Images` tool. - name: Equal Access Accessibility Checker + homepage: https://www.ibm.com/able/toolkit/ hidden: true vendor: IBM Accessibility + vendorHomepage: https://www.ibm.com/ uniqueKey: equal-access type: Automated tool standards: @@ -58,7 +82,9 @@ `RuleId1:ReasonCode1,ReasonCode2|RuleId2:ReasonCode3,ReasonCode4`. - name: QualWeb + homepage: http://qualweb.di.fc.ul.pt/evaluator/ vendor: LASIGE, Faculdade de Ciências da Universidade de Lisboa + homepage: http://qualweb.di.fc.ul.pt/evaluator/ uniqueKey: qualweb type: Automated tool standards: @@ -67,8 +93,10 @@ jsonReport: https://raw.githubusercontent.com/qualweb/ACT-implementation-report/main/qualweb-report.json - name: SortSite + omepage: https://www.powermapper.com/products/sortsite/ hidden: true vendor: PowerMapper + vendorHomepage: https://www.powermapper.com/ uniqueKey: sort-site type: Automated tool standards: diff --git a/_data/wcag-act-rules/implementations/axe-core.json b/_data/wcag-act-rules/implementations/axe-core.json index 438d0e8b..819ba177 100644 --- a/_data/wcag-act-rules/implementations/axe-core.json +++ b/_data/wcag-act-rules/implementations/axe-core.json @@ -1,7 +1,6 @@ { "vendor": "Deque Systems", "name": "Axe-core", - "version": "4.5-prerelease", "approvedRules": { "complete": 9, "partial": 2, diff --git a/content/_implementations-table.html b/content/_implementations-table.html index fa716920..69d91b15 100644 --- a/content/_implementations-table.html +++ b/content/_implementations-table.html @@ -12,7 +12,9 @@ {%- assign report = siteData.implementations[implementation.uniqueKey] %} {%- if implementation.hidden != true %} - {{ implementation.name }} {{ report.version }} + {{ implementation.name }} + {%- if report.version %} {{ report.version }}{% else %} {{ implementation.version }}{% endif -%} +
                    {% for standard in implementation.standards %}
                  • {{ standard }}
                    • {% endfor %}
                  From 69d519bc128b604e7bfe2af57b03ebf717fbceac Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Wed, 8 Jun 2022 15:48:59 +0200 Subject: [PATCH 20/25] Add link to report format --- content/implementations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/implementations.md b/content/implementations.md index 58a0927e..96eace75 100644 --- a/content/implementations.md +++ b/content/implementations.md @@ -49,7 +49,7 @@ See [understanding ACT consistency](#understanding-act-consistency) for details. ## Understanding ACT Consistency -Each ACT rule has examples. Vendors of test tools and methodologies run their implementations against the examples and report the outcome in a standard format. Reports are based on publicly available data. +Each ACT rule has examples. Vendors of test tools and methodologies run their implementations against the examples and report the outcome in a [standard format](https://act-rules.github.io/pages/implementations/earl-reports/). Reports are based on publicly available data. A test tool or methodology is considered **consistent** when all the following are true: From 92b0b2d34d8aa4e70dae7dce89b34d285507fd2f Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Wed, 8 Jun 2022 18:59:57 +0200 Subject: [PATCH 21/25] Fix missing version from yml file --- _layouts/act_implementation.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_layouts/act_implementation.html b/_layouts/act_implementation.html index b638fcfa..d6554294 100644 --- a/_layouts/act_implementation.html +++ b/_layouts/act_implementation.html @@ -24,7 +24,7 @@ {{ implementationInfo.name }} {% endif %} {% unless implementation.versionDate %} - version {{ implementation.version }} + version {% if implementation.version %}{{ implementation.version }}{% else %}{{ implementationInfo.version }}{% endif %} {% endunless %} is an {{ implementationInfo.type }} {% if implementationInfo.vendorHomepage %} @@ -36,7 +36,7 @@ {% endif %} {% if implementation.versionDate %} - Version {{ implementation.version }} + version {% if implementation.version %}{{ implementation.version }}{% else %}{{ implementationInfo.version }}{% endif %} was published on {{ implementation.versionDate | date: '%e %B %Y' }}. {% endif %} From 12dba7f124a376bde933d8063c4480bebc9f60c1 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Thu, 9 Jun 2022 11:51:17 +0200 Subject: [PATCH 22/25] Tweak vender listing --- _data/wcag-act-rules/act-implementations.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_data/wcag-act-rules/act-implementations.yml b/_data/wcag-act-rules/act-implementations.yml index bca90380..04afe9ec 100644 --- a/_data/wcag-act-rules/act-implementations.yml +++ b/_data/wcag-act-rules/act-implementations.yml @@ -84,7 +84,7 @@ - name: QualWeb homepage: http://qualweb.di.fc.ul.pt/evaluator/ vendor: LASIGE, Faculdade de Ciências da Universidade de Lisboa - homepage: http://qualweb.di.fc.ul.pt/evaluator/ + vendorHomepage: https://www.lasige.pt/ uniqueKey: qualweb type: Automated tool standards: @@ -105,7 +105,7 @@ jsonReport: https://raw.githubusercontent.com/act-rules/act-rules-implementation-sortsite/master/report.json - name: Trusted Tester - vendor: Access Board + vendor: US federal government uniqueKey: trusted-tester type: Test methodology standards: From 6db6ab72cf9f3fdab4ccc5d05c420fd705822ec5 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Thu, 9 Jun 2022 17:50:10 +0200 Subject: [PATCH 23/25] Shorten implementation navbar item --- _config.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_config.yml b/_config.yml index 860669ba..95bfc304 100755 --- a/_config.yml +++ b/_config.yml @@ -67,7 +67,7 @@ defaults: ref: /standards-guidelines/act/rules/ - name: About ref: /standards-guidelines/act/rules/about/ - - name: Implementations in Tools and Methodologies + - name: Implementations ref: /standards-guidelines/act/implementations/ plugins: From f0f669eac3ed8aeab734562104a1fa8741e5660a Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Thu, 16 Jun 2022 13:27:25 +0200 Subject: [PATCH 24/25] Update content/implementations.md Co-authored-by: daniel-montalvo <49305434+daniel-montalvo@users.noreply.github.com> --- content/implementations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/implementations.md b/content/implementations.md index 96eace75..f2cfe928 100644 --- a/content/implementations.md +++ b/content/implementations.md @@ -20,7 +20,7 @@ github: {::nomarkdown} {% include box.html type="start" title="Summary" %} {:/} -The tables on these pages show how many ACT Rules different accessibility test tools and methodologies have consistently implemented. Each implementation links to a report with more details on how rules are implemented. See [understanding ACT consistency](#understanding-act-consistency) for details. +The tables on these pages show how many ACT Rules different accessibility test tools and methodologies have "consistently implemented". Each implementation links to a report with more details on how rules are implemented. See [understanding ACT consistency](#understanding-act-consistency) for details. {::nomarkdown} {% include box.html type="end" %} {:/} ## Test Methodologies From c54795c8a641a4471418570d6ec309af4f07faa8 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Thu, 16 Jun 2022 13:27:39 +0200 Subject: [PATCH 25/25] Update content/implementations.md Co-authored-by: daniel-montalvo <49305434+daniel-montalvo@users.noreply.github.com> --- content/implementations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/implementations.md b/content/implementations.md index f2cfe928..4034ca5e 100644 --- a/content/implementations.md +++ b/content/implementations.md @@ -33,7 +33,7 @@ See [understanding ACT consistency](#understanding-act-consistency) for details. ## Semi-automated Test Tools -Tools that combine user input and automated testing to test accessibility standards. +Semi-automated tools combine user input and automated testing to test accessibility standards. See [understanding ACT consistency](#understanding-act-consistency) for details. {% assign semiAutoTools = implementations | where: "type", "Semi-automated tool" %}