Overview

Use LoadStrike accessibility testing when a page or browser journey needs a standalone quality check before or alongside load testing. Available on Business and Enterprise plans.

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

What It Supports

Accessibility testing covers two quality gates: accessibility scan results and Browser Web Vitals. Accessibility checks accept page or journey URLs, WCAG standard labels, total violation budgets, critical and serious impact budgets, tag filters, include selectors, and exclude selectors. Web Vitals checks accept budgets for LCP, INP, CLS, FCP, and TTFB.

Standalone By Default

Accessibility and Web Vitals helpers create normal LoadStrike scenarios without adding a load profile. That makes the default behavior a single quality check for CI, release gates, and smoke validation. When you intentionally want repeated accessibility or browser metric checks during a performance run, attach WithLoadSimulations just like any other scenario.

Bring Your Browser Checker

The SDK helper receives your check callback, so teams can plug in Playwright, Selenium, axe, Lighthouse, browser performance APIs, or an in-house collector that already knows how to authenticate and reach the target page. LoadStrike evaluates the returned result against the configured budgets.

Report Output

Accessibility and Web Vitals outcomes appear as normal scenario pass or fail results. They can be included in local reports, HTML reports, portal reporting, realtime reporting sinks, and CI result handling alongside API, browser, and event-stream performance scenarios.

Plan Gate

Accessibility testing and browser Web Vitals checks are available on Business and above. The same runner key validates the language SDK, report output, and any extra features used by the scenario.

Feature usage samples

Use the accessibility helpers as standalone quality gates first. The same scenario can later receive load simulations when you intentionally want repeated accessibility or browser metric checks during a performance run.

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 helper behavior

Single run by default

No load simulation is added by the helper, so the check runs once unless you explicitly add WithLoadSimulations.

Accessibility result

Return URL plus violations from your checker. Violations can include rule id, impact, description, help URL, and target selectors.

Web Vitals result

Use the Browser Web Vitals helper when the check returns LCP, INP, CLS, FCP, or TTFB values instead of rule violations.

Reports

The outcome is a normal LoadStrike scenario result, so it can appear in HTML reports, portal reporting, realtime sinks, and CI output.

Plan gate

The helper requests the Business or Enterprise accessibility entitlement during runner-key validation.

Use the dedicated Accessibility Checks and Browser Web Vitals pages for every supported option and a focused example in each SDK language.