Skip to main content
How We Verify · Methodology

A nine-stage verification flow — not a scanner report.

Every finding travels through the same nine stages, from intake to trace. Two stages — NVDA behavioral capture and evidence sufficiency — are where we commit to what assistive technology actually exposes.

Book a Readiness CallDownload Capability Statement
Nine-stage verification flow
  1. 01Intake & Scoping
  2. 02Static Extraction
  3. 03Rule Analysis
  4. 04NVDA Behavioral Capture
  5. 05Event Normalization
  6. 06Reconciliation
  7. 07Conflict Resolution
  8. 08Evidence Sufficiency
  9. 09Finding & Trace
TRACE-001

Every finding is a verifiable record.

StatusVerified
Verification Standard

Every conclusion is tied to captured assistive-technology behavior — reproducible from its trace, not from a scanner's rule name.

  • Capture
    NVDA behavioral session
  • Mapping
    WCAG 2.1 AA success criteria
  • Output
    Finding record with trace ID
Verification Flow

Nine stages, one trace.

Intake, static extraction, behavioral capture, reconciliation, evidence sufficiency — the same order on every engagement, so findings stay comparable over time.

  1. 01Intake & Scoping
  2. 02Static Extraction
  3. 03Rule Analysis
  4. 04NVDA Behavioral Capture
  5. 05Event Normalization
  6. 06Reconciliation
  7. 07Conflict Resolution
  8. 08Evidence Sufficiency
  9. 09Finding & Trace
Nine-stage verification flow: Intake & Scoping, Static Extraction, Rule Analysis, NVDA Capture (behavioral emphasis), Event Normalization, Reconciliation, Conflict Resolution, Evidence Sufficiency (evidence emphasis), Finding & Trace. Each stage feeds the next, with NVDA Capture and Evidence Sufficiency highlighted as the two moments where behavioral truth is committed.
Structure vs. Exposure

What's in the document is not what the user hears.

Static analysis tells you the document's tag structure. Behavioral verification tells you what the accessibility tree actually exposes to a screen reader. The gap between the two layers is where compliance risk lives.

Tags
  • H1
    Heading
  • P
    Text
  • BUTTON
    no name
  • IMG
    no alt
  • DIV
    ignored
Discrepancy zone
Exposed to the screen reader
Two-layer diagram contrasting a document's tag structure with what a screen reader actually exposes. The top layer shows document tags (H1, P, BUTTON, IMG, DIV). The bottom layer shows the assistive technology accessibility tree (Heading, Text, — no name —, Image without alt, and an ignored group). A shaded band between the two layers marks the discrepancy — the gap where behavioral verification lives.
Approach Comparison

Static-only vs. behavioral.

Scanners are a valid first pass. They are not a verification record.

Dimension
What it examines
Static onlyTags only
Behavioral verificationWhat's exposed to assistive technology
Ambiguous cases
Static onlyDefaults to pass
Behavioral verificationNames the limitation
Evidence trail
Static onlyRule output only
Behavioral verificationReproducible trace
What you receive
Static onlyA scanner export with rule names and a score
Behavioral verificationA finding record with trace ID, WCAG criterion, and behavior log
Limits of the record

Scoped non-conclusions.

Where evidence is insufficient to support a conclusion, we say so and record the limitation in the finding. We do not convert an untestable case into a silent pass, and we do not certify coverage we did not observe.

Evidence Artifact

Every finding ships as a record — not a screenshot.

Trace ID, WCAG mapping, the assistive-technology behavior observed, and the raw log it came from. Reproducible by anyone who reads it.

Excerpt from a verification finding record — F-2027-0142CONFIRMED
NVDAFirefoxWin 11
element
button#submit-form
issue
accessible name absent
wcag
2.1 · 4.1.2 Name, Role, Value (A)
scanner
axe: pass · lighthouse: pass
behavior
NVDA announces "button" — no name reaches AT
evidence
screen-reader-log/f-2027-0142.txt
status
confirmed · defensible
Who This Is For

What each reader gets from the record.

  • Procurement officerA defensible record, not a vendor's word.
  • Accessibility coordinatorA methodology that explains its limits.
  • Technical evaluatorA trace you can scrutinize line by line.
  • Legal counselFindings built to hold up outside the room.
Book a Readiness Call

Ask us to verify one page before you commit.

A single behavioral verification tells you more about your exposure than a full scanner export.

Book a Readiness CallDownload Capability Statement