Skip to content

Latest commit

 

History

History
 
 

rules

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
accesskeys
accesskeys
 
 
area-alt
area-alt
 
 
aria-allowed-attr
aria-allowed-attr
 
 
aria-allowed-role
aria-allowed-role
 
 
aria-braille-equivalent
aria-braille-equivalent
 
 
aria-command-name
aria-command-name
 
 
aria-conditional-attr
aria-conditional-attr
 
 
aria-deprecated-role
aria-deprecated-role
 
 
aria-dialog-name
aria-dialog-name
 
 
aria-hidden-focus
aria-hidden-focus
 
 
aria-input-field-name
aria-input-field-name
 
 
aria-meter-name
aria-meter-name
 
 
aria-progressbar-name
aria-progressbar-name
 
 
aria-prohibited-attr
aria-prohibited-attr
 
 
aria-required-attr
aria-required-attr
 
 
aria-required-children
aria-required-children
 
 
aria-required-parent
aria-required-parent
 
 
aria-roledescription
aria-roledescription
 
 
aria-roles
aria-roles
 
 
aria-text
aria-text
 
 
aria-toggle-field-name
aria-toggle-field-name
 
 
aria-tooltip-name
aria-tooltip-name
 
 
aria-treeitem-name
aria-treeitem-name
 
 
aria-valid-attr-value
aria-valid-attr-value
 
 
aria-valid-attr
aria-valid-attr
 
 
audio-caption
audio-caption
 
 
autocomplete-valid
autocomplete-valid
 
 
avoid-inline-spacing
avoid-inline-spacing
 
 
blink
blink
 
 
button-name
button-name
 
 
color-contrast-enhanced
color-contrast-enhanced
 
 
color-contrast
color-contrast
 
 
definition-list
definition-list
 
 
dlitem
dlitem
 
 
duplicate-id-active
duplicate-id-active
 
 
duplicate-id-aria
duplicate-id-aria
 
 
duplicate-id
duplicate-id
 
 
empty-heading
empty-heading
 
 
empty-table-header
empty-table-header
 
 
focus-order-semantics
focus-order-semantics
 
 
form-field-multiple-labels
form-field-multiple-labels
 
 
frame-focusable-content
frame-focusable-content
 
 
frame-title-unique
frame-title-unique
 
 
frame-title
frame-title
 
 
heading-order
heading-order
 
 
hidden-content
hidden-content
 
 
identical-links-same-purpose
identical-links-same-purpose
 
 
image-alt
image-alt
 
 
image-redundant-alt
image-redundant-alt
 
 
input-button-name
input-button-name
 
 
input-image-alt
input-image-alt
 
 
label-content-name-mismatch
label-content-name-mismatch
 
 
label-title-only
label-title-only
 
 
label
label
 
 
landmark-unique
landmark-unique
 
 
link-in-text-block
link-in-text-block
 
 
link-name
link-name
 
 
list
list
 
 
listitem
listitem
 
 
marquee
marquee
 
 
meta-refresh
meta-refresh
 
 
meta-viewport-large
meta-viewport-large
 
 
meta-viewport
meta-viewport
 
 
nested-interactive
nested-interactive
 
 
object-alt
object-alt
 
 
p-as-heading
p-as-heading
 
 
presentation-role-conflict
presentation-role-conflict
 
 
role-img-alt
role-img-alt
 
 
scope-attr-valid
scope-attr-valid
 
 
scrollable-region-focusable
scrollable-region-focusable
 
 
select-name
select-name
 
 
server-side-image-map
server-side-image-map
 
 
summary-name
summary-name
 
 
svg-img-alt
svg-img-alt
 
 
tabindex
tabindex
 
 
table-duplicate-name
table-duplicate-name
 
 
table-fake-caption
table-fake-caption
 
 
target-size
target-size
 
 
td-has-header
td-has-header
 
 
td-headers-attr
td-headers-attr
 
 
th-has-data-cells
th-has-data-cells
 
 
valid-lang
valid-lang
 
 
video-caption
video-caption
 
 
README.md
README.md
 
 
preprocessor.js
preprocessor.js
 
 
runner.js
runner.js
 
 

README.md

Rule Integration Tests

Rule Integration tests take an HTML snippet file and runs an axe-core rule against it. The results for the run are then compared against the companion JSON file to ensure that every node returns as the expected result (passes, violation, incomplete, inapplicable).

To run the rule integration tests, run npm run test:unit:integration. You can run and debug the tests in a non-headless browser by running npm run test:debug -- testDirs=integration. You can either use that browser's debugger or attach an external debugger on port 9765; a VS Code launch profile is provided.

When the tests are run, each JSON file is converted into a test suite file using Karmas preprocessor and runner.js as the test suite template.

The JSON file for a rule integration test contains the following information:

  • description - string(required). The title of the test. Used in the describe block of the test suite
  • rule - string(required) The axe-core rule to run
  • violations array(optional). List of axe-core selectors of nodes that should return as Violations
  • passes array(optional). List of axe-core selectors of nodes that should return as Passes
  • incomplete array(optional). List of axe-core selectors of nodes that should return as Needs Review

The JSON file should have at least one of the violations, passes, or incomplete arrays. Inapplicable results are not listed as the test will fail if any node is found in one of the 3 arrays that is not explicitly listed.