Audit Workflow

This page walks through the complete process of running an accessibility audit in xyva — from entering a URL to exporting actionable findings.

Step 1: Enter the Target URL

In the Accessibility Auditor panel, enter the URL of the page you want to audit. The URL must be reachable from your machine (HTTP or HTTPS).

URL: https://staging.acme.com/checkout

Local Development

You can audit localhost URLs. Make sure your dev server is running before starting the audit.

Step 2: Select the Standard

Choose the compliance standard from the dropdown:

Standard	When to Use
BFSG	Legal compliance for German-market products/services
WCAG 2.1 AA	International accessibility best practices

Both standards run similar technical checks, but BFSG frames results in terms of legal requirements.

Step 3: Run the Audit

Click Run Audit to start the analysis. xyva:

1. Opens the URL in a headless Chromium instance
2. Captures the fully rendered DOM (including JavaScript-generated content)
3. Runs the accessibility rule engine against the rendered page
4. Applies AI analysis to provide context-aware recommendations

The audit typically completes in 5-15 seconds per page.

Step 4: Review Findings

Results are displayed in three severity groups:

Critical Findings

Issues that block access for users with disabilities. These must be fixed for compliance.

[CRITICAL] Missing form label
  Rule:    WCAG 3.3.2 — Labels or Instructions
  Element: input#email (CSS: form > .field:nth-child(2) > input)
  Fix:     Add <label for="email">Email Address</label> before the input

Warning Findings

Issues that degrade the experience but do not completely block access.

[WARNING] Low contrast ratio
  Rule:    WCAG 1.4.3 — Contrast (Minimum)
  Element: p.subtitle (CSS: .hero > p.subtitle)
  Current: 3.2:1 (required: 4.5:1)
  Fix:     Change color from #999999 to #595959

Info Findings

Best-practice recommendations that improve usability.

[INFO] Missing ARIA landmark
  Rule:    WCAG 2.4.1 — Bypass Blocks
  Element: <nav> without role="navigation"
  Fix:     Add role="navigation" or use <nav aria-label="Main">

Finding Count

The summary bar shows total findings per severity: e.g., 3 Critical | 7 Warning | 12 Info. Use this to gauge overall compliance at a glance.

Step 5: Export Results

Export findings to integrate with your team's workflow:

Export Target	Format	Use Case
YouTrack	Issue per finding	Sprint planning and assignment
PDF	Formatted report	Legal documentation, stakeholder review
JSON	Machine-readable	CI pipeline integration, custom dashboards

CI Integration

Accessibility checks can run in your CI pipeline. Configure whether Critical findings should block the build or only warn in Settings > Accessibility > CI Mode.

Re-Audit After Fixes

After applying fixes, re-run the audit on the same URL. xyva compares results against the previous run, highlighting Resolved, New, and Persistent findings.