Skip to content

includedImpacts is being ignored #218

@kirkpams

Description

@kirkpams

I'm trying to use checkA11y for just serious and critical impact levels, but I keep getting moderate violations reported. Here is my call to checkA11y:


await checkA11y(page, null, {
  axeOptions: {
    includedImpacts: [ "serious", "critical" ],
  }});

Is there something I'm missing in the syntax (or a typo somewhere)? I keep getting the following results:

Running 14 tests using 4 workers
[chromium] › tests.spec.ts:337:2 › Remaining Basic Elements › Checking for accessibility
┌─────────┬─────────────────────┬────────────┬──────────────────────────────────────────────────────┬───────┐
│ (index) │         id          │   impact   │                     description                      │ nodes │
├─────────┼─────────────────────┼────────────┼──────────────────────────────────────────────────────┼───────┤
│    0    │ 'landmark-one-main' │ 'moderate' │      'Ensures the document has a main landmark'      │   1   │
│    1    │      'region'       │ 'moderate' │ 'Ensures all page content is contained by landmarks' │   9   │
└─────────┴─────────────────────┴────────────┴──────────────────────────────────────────────────────┴───────┘
  1) [chromium] › tests.spec.ts:337:2 › Remaining Basic Elements › Checking for accessibility 

    AssertionError: 2 accessibility violations were detected

How do I get checkA11y to stop reporting these two errors (which are known and I want to ignore)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions