Accessibility TestingReference
Rule Categories
What the Advanced rules, Best practices, and Needs review toggles actually include.
Rule Categories
TestKase runs axe-core under the hood. Axe groups rules by category (what they check) and by tag (which standard / enablement status they're part of). The three toggles in Scan Settings map to those tags.
Advanced rules (advanced)
- Default: On.
- What it is: axe-core rules that are disabled by default but mapped to WCAG. Examples:
focus-order-semantics,scrollable-region-focusable. - Why leave on: you typically want to catch these issues.
- Why turn off: rarely — only if your program has decided a specific rule produces too much noise.
Best practices (bestPractices)
- Default: Off.
- What it is: rules that improve UX and accessibility but are not WCAG success criteria. Examples:
landmark-unique,heading-order,region. - Why turn on: you want to produce friendlier, more consistent interfaces and you're OK with findings that don't map to formal WCAG failures.
- Why leave off (default): you want a report that's exclusively WCAG conformance-driven, e.g., for an audit.
Needs review (needsReview)
- Default: On.
- What it is: issues axe-core couldn't decide on automatically. They show up with status incomplete in the WCAG conformance matrix. Example: ensuring a custom control has an accessible keyboard handler when the handler isn't statically analyzable.
- Why leave on: catches things that are likely problems; a human can confirm.
- Why turn off: you only want the hard pass/fail list for reporting.
What's always on
- Every rule mapped to your chosen WCAG version and level. This is the core of the scan and can't be disabled — it's what the conformance matrix is measured against.
Where the toggles live
Scan Settings → Accessibility tab. See Web Scanner for screenshots.