Skip to content

Run Accessibility Audits in CI and Export SARIF

Accessibility work should be continuous, not last-minute.

The Web Content Accessibility Guidelines (WCAG) are the international accessibility standard. https://www.w3.org/WAI/standards-guidelines/wcag/

SARIF means Static Analysis Results Interchange Format, a standard file format for tool findings. https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html

This guide shows how to automate both using Gasoline Agentic Devtools.

  • Accessibility audit: Scan for issues that block people with disabilities.
  • CI (Continuous Integration): Automated checks on every change.
  • SARIF file: Structured report your tools can ingest and track.

You want to catch accessibility issues before users do.

Step-by-Step with Gasoline Agentic Devtools

Section titled “Step-by-Step with Gasoline Agentic Devtools”
analyze({what: "accessibility", summary: true})
generate({what: "sarif", save_to: "./reports/accessibility.sarif"})

In your CI job, run your scripted Gasoline checks and archive accessibility.sarif as a build artifact.

analyze({what: "accessibility", force_refresh: true, summary: true})

Accessibility is quality. Continuous checks help teams ship inclusive experiences by default.

[Image Idea] Sample SARIF report snippet with one issue explained in plain language.

[Diagram Idea] CI pipeline stage: build -> run accessibility audit -> export/report -> fail or pass.

You’re Building Better Software for Everyone

Section titled “You’re Building Better Software for Everyone”

Teams that automate accessibility early move faster and cause less harm. Gasoline Agentic Devtools makes this practical for everyday workflows.