Developers

Structured Findings Your Pipeline Can Read.

Every conformance finding as structured JSON. Route findings to Jira, feed dashboards, trigger alerts, or build your own integration layer.

Structured findings, stable schema, no SDK required — parse it with whatever you already run. Direct line: zeerohr@wegendigital.com

Output format

Every finding is a data object.

Conformance findings arrive as structured JSON with consistent field names, severity levels, and standard references. Parse them the same way every time.

// Single finding object from a WeGen review
{
  "id": "f-a8c2e491",
  "standard": "WCAG 2.2",
  "criterion": "1.4.3 Contrast (Minimum)",
  "severity": "high",
  "page": "https://example.gov/about",
  "element": "nav > a.menu-link",
  "observed": "Contrast ratio 2.8:1 on #777 over #fff",
  "expected": "Minimum 4.5:1 for normal text",
  "remediation": "Darken text to #595959 or darker",
  "category": "accessibility",
  "timestamp": "2026-06-28T14:30:00Z"
}

Schema

Consistent fields across every category.

Whether the finding is accessibility, security, privacy, or plain language, the shape stays the same. Your integration code handles all categories with one parser.

id string Unique finding identifier (standard + criterion + sequence)
standard string The standard being reviewed against (WCAG 2.2, NIST, etc.)
severity enum critical | high | medium | low | informational
page url The exact URL where the finding was observed
element string CSS selector or XPath to the affected element
category enum accessibility | security | privacy | readability | performance
remediation string Specific fix guidance the dev team can act on

Integrations

Findings that fit your existing workflow.

Structured output means you decide where findings go. Route to the tools your team already uses.

CI/CD

Pipeline Gates

Parse findings by severity. Fail the build on critical accessibility regressions. Pass on informational items. Your threshold, your rules.

Ticketing

Issue Creation

Map findings directly to Jira, Linear, or GitHub Issues. Each finding has enough context (page, element, remediation) to be an actionable ticket without manual triage.

Dashboards

Trend Tracking

Feed findings into Grafana, Datadog, or your internal dashboard. Track finding counts by category over time. See whether your accessibility posture is improving or regressing.

Alerting

Severity-Based Routing

Critical security findings go to your security team's Slack channel. Accessibility findings route to your design system lead. Readability issues go to content ops.

How to integrate

Three steps to structured findings in your workflow.

Request a review

Send us your URLs. We run the conformance review against the standards you specify (accessibility, security, privacy, readability, or all).

Receive JSON output

Findings delivered as a JSON array. Each object follows the schema above. Consistent shape regardless of which standards were reviewed.

Route and act

Parse the output with your existing tools. Create tickets, update dashboards, gate deployments, or trigger notifications based on severity and category.

Conformance findings that your code can parse as easily as your team can read.