axe-core-cucumber 2.6.1.pre.0f0b25b → 4.0.0.pre.2b814f9

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 12c622105a18aa0c9cbdd6e80f451c96f47affc06a65a3c449028faed045e889
-  data.tar.gz: f4ea28f8bd25cd74ec153cd215350ff73716f07a3043f52a4f944ee2dba84ad4
+  metadata.gz: 2609b6f24be811bd13ad2f4107cb6c1e3cd87595a253ccb9a8b151eed1630355
+  data.tar.gz: e845f086e404d0ba06250584478aeaf412f3150c1886cf8124cbef6533c47f44
 SHA512:
-  metadata.gz: d9ed5c60dcb494caf603e3e17133903800e7b9c56a25f3aa8d63a4a6459b47a48ef525a4705024cda35c892d4101a0fc63ba394c68fc123d352a2fbe2035bf2b
-  data.tar.gz: c93a94dc5456b6719f3e7e3be694c385cba0afda0edbfb0dee1fc66b48fd29875bc7ab6293aaac232d2a1b296efeb9a00d4992189780a76b18db33e573c30c7d
+  metadata.gz: fc4226176942a0102f58453107dfc80553df95c711d83481a01587336eaf554f672aea6cf96d80d15bf24f3efc2f272e0a1727f3f2dfeecce3371946b4b2f914
+  data.tar.gz: e9b891d8cc5b9c4b2388c3a043894887e66b65f64fef9c1b99c057fae461f2cc45e7f0fe7a3cb9cef589cfda71821a1ed6ac1752c52dd92140fde8f506dd3034

data/README.md

@@ -23,15 +23,15 @@ require 'axe-cucumber-steps'
 
 ### Base Step
 
-The base step `be accessible` is the core component of the step. It is a complete step on its own and will verify the currently loaded page is accessible using the default configuration of [axe.run][axe-run] (the entire document is checked using the default rules).
+The base step `be axe clean` is the core component of the step. It is a complete step on its own and will verify the currently loaded page is axe clean using the default configuration of [axe.run][axe-run] (the entire document is checked using the default rules).
 
 ```gherkin
-Then the page should be accessible
+Then the page should be axe clean
 ```
 
 #### Clauses
 
-Clauses are chainable methods for the `be accessible` custom step.Configurable clauses allows for greater granularity with testing and expectaions.
+Clauses are chainable methods for the `be axe clean` custom step.Configurable clauses allows for greater granularity with testing and expectaions.
 
 ##### `within` - Inclusion clause
 
@@ -39,7 +39,7 @@ The inclusion clause ( `within "#selector"` ) specifies which elements of the pa
 *see additional [context parameter documentation][context-param]*
 
 ``` gherkin
-Then the page should be accessible within "#selector"
+Then the page should be axe clean within "#selector"
 ```
 
 ##### `excluding` - Exclusion clause
@@ -48,14 +48,14 @@ The exclusion clause ( `excluding "#selector"` ) specifies which elements of the
 *see additional [context parameter documentation][context-param]*
 
 ``` gherkin
-Then the page should be accessible excluding "#selector"
+Then the page should be axe clean excluding "#selector"
 ```
 
 If desired, a semicolon ( `;` ) or the word `but` may be used to separate the exclusion clause from the inclusion clause (if present).
 
 ``` gherkin
-Then the page should be accessible within "main"; excluding "aside"
-Then the page should be accessible within "main" but excluding "aside"
+Then the page should be axe clean within "main"; excluding "aside"
+Then the page should be axe clean within "main" but excluding "aside"
 ```
 
 ##### `according to` - Accessibility Standard (Tag) clause
@@ -64,13 +64,13 @@ The tag clause specifies which accessibility standard (or standards) should be u
 The acceptable [tag names are documented][options-param] as well as a [complete listing of rules][rules] that correspond to each tag.
 
 ``` gherkin
-Then the page should be accessible according to: tag-name
+Then the page should be axe clean according to: tag-name
 ```
 
 If desired, a semicolon ( `;` ) may be used to separate the tag clause from the preceding clause.
 
 ``` gherkin
-Then the page should be accessible within "#header"; according to: best-practice
+Then the page should be axe clean within "#header"; according to: best-practice
 ```
 
 ##### `checking` - Checking Rules clause
@@ -78,7 +78,7 @@ Then the page should be accessible within "#header"; according to: best-practice
 The checking-rules clause specifies which *additional* rules to run (in addition to the specified tags, if any, or the default ruleset). The rules are specified by comma-separated rule IDs.
 
 ``` gherkin
-Then the page should be accessible checking: ruleId
+Then the page should be axe clean checking: ruleId
 ```
 
 *see [rules documentation][rules] for a list of valid rule IDs*
@@ -86,8 +86,8 @@ Then the page should be accessible checking: ruleId
 If desired, a semicolon ( `;` ) or the word `and` may be used to separate the checking-rules clause from the preceding clause.
 
 ``` gherkin
-Then the page should be accessible according to: wcag2a; checking: color-contrast
-Then the page should be accessible according to: wcag2a and checking: color-contrast
+Then the page should be axe clean according to: wcag2a; checking: color-contrast
+Then the page should be axe clean according to: wcag2a and checking: color-contrast
 ```
 
 ##### `checking only` - Exclusive Rules clause
@@ -95,7 +95,7 @@ Then the page should be accessible according to: wcag2a and checking: color-cont
 This clause is not really a separate clause. But rather, by adding the word `only` to the checking-rules clause, the meaning of the step can be changed. As described above, by default the checking-rules clause specifies *additional* rules to run. If the word `only` is used, then *only* the specified rules are checked.
 
 ``` gherkin
-Then the page should be accessible checking only: ruleId
+Then the page should be axe clean checking only: ruleId
 ```
 
 ##### `skipping` - Skipping Rules clause
@@ -103,7 +103,7 @@ Then the page should be accessible checking only: ruleId
 The skipping-rules clause specifies which rules to skip. This allows an accessibility standard to be provided (via the tag clause) while ignoring a particular rule. The rules are specified by comma-separated rule IDs.
 
 ``` gherkin
-Then the page should be accessible skipping: ruleId
+Then the page should be axe clean skipping: ruleId
 ```
 
 *see [rules documentation][rules] for a list of valid rule IDs*
@@ -111,8 +111,8 @@ Then the page should be accessible skipping: ruleId
 If desired, a semicolon ( `;` ) or the word `but` may be used to separate the skipping-rules clause from the preceding clause.
 
 ``` gherkin
-Then the page should be accessible according to: wcag2a; skipping: accesskeys
-Then the page should be accessible according to: wcag2a but skipping: accesskeys
+Then the page should be axe clean according to: wcag2a; skipping: accesskeys
+Then the page should be axe clean according to: wcag2a but skipping: accesskeys
 ```
 
 ##### Interoperability between clauses
@@ -120,13 +120,13 @@ Then the page should be accessible according to: wcag2a but skipping: accesskeys
 All of the described clauses may be mixed and matched with method chaining. Below are some examples.
 
 ``` gherkin
-Then the page should be accessible within "main, header" but excluding "footer"
+Then the page should be axe clean within "main, header" but excluding "footer"
 
-Then the page should be accessible excluding "#sidebar" according to: wcag2a, wcag2aa but skipping: color-contrast
+Then the page should be axe clean excluding "#sidebar" according to: wcag2a, wcag2aa but skipping: color-contrast
 
-Then the page should be accessible checking only: document-title, label
+Then the page should be axe clean checking only: document-title, label
 
-Then the page should be accessible according to: best-practice and checking: aria-roles, definition-list
+Then the page should be axe clean according to: best-practice and checking: aria-roles, definition-list
 ```
 
 [inclusion-clause]: #inclusion-clause

data/lib/axe-cucumber.rb

@@ -1,6 +1,6 @@
 require "yaml"
 
-require "axe/matchers/be_accessible"
+require "axe/matchers/be_axe_clean"
 require "axe/finds_page"
 require "axe/expectation"
 
@@ -16,7 +16,7 @@ module AxeCucumber
     # Extracting regex into variable to allow for easier consumption elsewhere
     ###############
     # require initial phrasing, with 'not' to negate the matcher
-    REGEX_CAPTURE_NEGATE = "(?-x:the page should( not)? be accessible)"
+    REGEX_CAPTURE_NEGATE = "(?-x:the page should( not)? be axe clean)"
     # optionally specify which subtree to check, via CSS selector
     REGEX_CAPTURE_INCLUSION = '(?-x:;? within "(.*?)")?'
     # optionally specify subtrees to be excluded, via CSS selector
@@ -52,7 +52,7 @@ module AxeCucumber
       skip_rules = "",
       options = nil
     )
-      is_accessible = Axe::Matchers::BeAccessible.new.tap do |a|
+      is_axe_clean = Axe::Matchers::BeAxeClean.new.tap do |a|
         a.within(*selector(inclusion))
         a.excluding(*selector(exclusion))
         a.according_to(*split(tags))
@@ -62,7 +62,7 @@ module AxeCucumber
         a.with_options to_hash(options)
       end
 
-      Axe::AccessibilityExpectation.create(negate).assert @page, is_accessible
+      Axe::AccessibilityExpectation.create(negate).assert @page, is_axe_clean
     end
 
     private

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: axe-core-cucumber
 version: !ruby/object:Gem::Version
-  version: 2.6.1.pre.0f0b25b
+  version: 4.0.0.pre.2b814f9
 platform: ruby
 authors:
 - Deque Systems
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-08-25 00:00:00.000000000 Z
+date: 2020-12-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: dumb_delegator