axe-core-cucumber 2.6.1.pre.78a535c → 4.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 838d6e1aaf41835514c433c6302e8d642b9d363cafdb69c59d39699577151028
-  data.tar.gz: 816f2a84aa43e7342d84e80896c1c53e7809391a0e84ffdc742661d7cb66ab17
+  metadata.gz: 67fd8c4cf6c4fcca6e92c75637ec5cd18ed5a01709461a03d0d4b476409a65a5
+  data.tar.gz: 426529d105770eff0151325b654a5f2d99bbc019def741953f285a6bb53214a9
 SHA512:
-  metadata.gz: 4fdcdcb51ff930607c936392d012745151c810eda7fd8dafb330b86b2b0cfb67b529a3fd80f52758a29852030d20a2fb9920fd2ede115b02bf48d1e613d7507c
-  data.tar.gz: 73da4346c8136517a0b88e621c6980d652591181758beb427d693173cc55eb1e89215ee8aa0fa9de14a48b9774a7cb34577e867c808bb5774ff11207ff394c8f
+  metadata.gz: 39e2d3d7a77218b161bbc206a301933ec640f3f948182ffe7a96e90a3ab1cbdba92026a2c1f18f048e45428cd3fbb44e7a96ffebb7c6927e0c410057ae6ed3dc
+  data.tar.gz: 6e2721dcbcc2938b56f21d417309637d624fceeb5181845e26c6ee59e68f6d555340e1a43111a72031be29d2234c9b16673bc9f69e6f7920c8007d0a8a380498

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,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: axe-core-cucumber
 version: !ruby/object:Gem::Version
-  version: 2.6.1.pre.78a535c
+  version: 4.0.0
 platform: ruby
 authors:
 - Deque Systems
@@ -150,9 +150,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: 2.3.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubygems_version: 3.0.3
 signing_key: