19.2
Axe-checks with QF-Test

Errors when checking a website with axe can be found in the run log with the following error code:
QF-Test-errorcode: ERR_AXE-CORE_CHECKS

NoteQF-Test extends axe with the function of checking elements in closed shadow roots for accessibility. However, this is only possible when using the CDP-Driver connection mode.

19.2.1
Parameters of axe-checks

The procedure runAxeChecks has the following additional parameters:

rules
The rule-IDs of the axe rules or the tags defined by axe, separated by a comma (https://dequeuniversity.com/rules/axe/html).

Examples:

  • button-name
  • button-name,color-contrast,aria-required-attr
  • wcag2aa
  • wcag2aa,best-practice,cat.aria
If this parameter is left empty, all rules are checked.
Default: wcag2a,wcag2aa,wcag21a,wcag21aa,wcag22aa, also die Tags der für die Erfüllung der WCAG relevanten Axe-Regeln
rulesToSkip
If the rules parameter is empty or filled with tags, it is possible to exclude individual rules from the check here. A comma-separated list of Axe rule IDs must be specified for this.

Examples:

  • button-name
  • button-name,color-contrast,aria-required-attr
If this parameter is left blank, no rules are excluded from the check.
Default: -
19.2.2
Axe-core's "impact" rating

The developers of axe-core assigned an “impact” to each individual rule. This value is listed by QF-Test in the error messages for the rules and quantifies the impact of a problem on a user with a disability. Listed in ascending order (by severity of the impact on disabled users), there are the following categories:

Minor: low priority
A nuisance or an annoying bug.
Moderate: medium priority
Causes difficulties for people with disabilities, but generally does not prevent them from accessing basic features.
Serious: high priority
Creates serious barriers for people with disabilities and prevents them from accessing basic functions or content in whole or in part.
Critical: top priority
The problem blocks people with disabilities from using the basic functionalities of the site and accessing the content.

Note The "impact" rating allows to prioritize problems for bugfixing. To comply with the WCAG guidelined, however, all errors must be fixed - even low priority ones!