Accessibility Checks

Wrap accessibility scan results in a LoadStrike scenario so violations become a run result, report row, and CI-friendly pass or fail outcome.

Use this page when

Visual guide

Sequence diagram showing how a LoadStrike workflow moves from setup to report output.
This page fits into the same setup, run, correlate, and report flow as the rest of the public LoadStrike runtime.

Guide

Options

Set Url to the page or journey target, Standard to the accessibility profile you want to label in the test, Tags to pass rule groups to your checker, IncludeSelectors to focus the scan on important page regions, and ExcludeSelectors to ignore known non-product regions such as third-party widgets or consent banners.

Quality Budgets

Set MaxViolations, MaxCriticalViolations, and MaxSeriousViolations to define the pass or fail budget. A scenario fails when the returned result exceeds any configured limit. Use a total budget for broad regressions and impact budgets when high-severity issues must fail independently.

Result Shape

Return a LoadStrikeAccessibilityResult with the evaluated URL and the violations reported by your checker. Each violation can carry rule id, impact, description, help URL, and target selectors. LoadStrike counts critical, serious, moderate, and minor impacts from that result.

Single Check Or Load

The generated scenario disables warmup and does not add a load profile by default. Add WithLoadSimulations only when the same accessibility check should be repeated during a load run.

Reports And Automation

Because the check is a normal scenario, it works with runner keys, report formats, portal reporting, realtime sinks, thresholds around the run, and CI pass or fail handling.

Feature usage samples

Use this pattern when your browser automation, axe runner, Lighthouse job, or internal checker already has the scan result and LoadStrike should own the budget evaluation, reporting, and CI result.

If you run these examples locally, add a valid runner key before execution starts. Set it with WithRunnerKey("...") or the config key LoadStrike:RunnerKey.

Accessibility Check

using LoadStrike;

var options = new LoadStrikeAccessibilityOptions
{
    Url = "https://example.com/checkout",
    Standard = "WCAG2AA",
    MaxViolations = 2,
    MaxCriticalViolations = 0,
    MaxSeriousViolations = 1,
    Tags = new[] { "wcag2a", "wcag2aa", "best-practice" },
    IncludeSelectors = new[] { "main", "#checkout-form" },
    ExcludeSelectors = new[] { ".cookie-banner", "[data-testid='support-widget']" }
};

var scenario = LoadStrikeAccessibility.CreateScenario(
    "checkout-accessibility",
    options,
    _ => new LoadStrikeAccessibilityResult
    {
        Url = options.Url,
        Violations = new[]
        {
            new LoadStrikeAccessibilityViolation
            {
                RuleId = "color-contrast",
                Impact = "serious",
                Description = "Text must meet contrast requirements.",
                HelpUrl = "https://dequeuniversity.com/rules/axe/4.10/color-contrast",
                Targets = new[] { ".payment-summary .total" }
            }
        }
    });

_ = scenario;

Accessibility options and result fields

Url

The page or browser journey target. It must be an absolute URL.

Standard

The accessibility profile label for the check, such as WCAG2AA, WCAG2A, WCAG21AA, or the naming convention your checker uses.

Tags

Rule groups to pass to your scanner, commonly WCAG tags, best-practice tags, or project-specific rule groups.

IncludeSelectors

CSS selectors for the page regions that should be checked, such as main content, checkout forms, account panels, or authenticated app shells.

ExcludeSelectors

CSS selectors for regions that should not fail the product check, such as cookie banners, third-party widgets, or known external embeds.

MaxViolations

Fails the scenario if the total returned violation count is higher than this limit.

Impact budgets

MaxCriticalViolations and MaxSeriousViolations fail independently from the total count.

Violation fields

Each violation can include RuleId, Impact, Description, HelpUrl, and Targets so report readers know what failed and where.

LoadStrike evaluates the returned result. Your callback decides how to run the browser, authenticate, collect rule results, and map them into the LoadStrike result shape.