VPAT and ACR Findings to Accessibility Tickets

A VPAT or Accessibility Conformance Report is useful for procurement and risk review. It is rarely enough for engineering. Remediation work needs tickets that name the affected feature, user impact, evidence, owner, and retest path.

Use this guide when a VPAT, ACR, EN 301 549 review, or WCAG conformance matrix contains "partially supports", "does not support", exception notes, or audit evidence that should become backlog work.

Do not turn every VPAT row into a ticket automatically. Start with rows that point to real user tasks, legal procurement blockers, or repeated product defects.

Open this VPAT note in the generator

What to extract from a VPAT or ACR row

Criterion and status: keep the WCAG, Revised 508, or EN 301 549 reference and the support level stated in the report.
Product area: name the page, flow, feature, document, or platform where the exception appears.
Exception wording: preserve the exact note as evidence, but rewrite the ticket in user-task language.
Observed impact: explain who is affected and what becomes blocked, confusing, or slower.
Retest method: identify whether QA should use keyboard testing, screen reader testing, scanner retest, document inspection, or procurement evidence review.

Prioritize rows before ticket creation

Ticket first: failures in checkout, login, registration, account management, search, support contact, documents needed to buy or use the product, and shared components.
Group as component work: the same missing accessible name, focus order, contrast token, form error pattern, or table structure across many screens.
Keep as report note: broad policy statements, future roadmap language, or unsupported features that have no current user-facing path.
Escalate carefully: anything that changes the public conformance statement, legal wording, or contractual promise needs product/legal ownership before publication.

Example conversion

VPAT / ACR row:
WCAG 2.4.3 Focus Order - Partially Supports.
Exception: In the checkout shipping drawer, keyboard focus moves behind the open drawer before the Continue button.

Developer ticket:
[Critical] Checkout shipping drawer lets keyboard focus leave the active step

User impact:
Keyboard users can lose their position inside the shipping step and tab through page controls hidden behind the drawer before they can continue checkout.

Evidence:
- Source: VPAT / ACR exception note
- Criterion: WCAG 2.4.3 Focus Order
- Area: checkout shipping drawer
- Observed behavior: focus moves behind the open drawer before the Continue button

Acceptance criteria:
- Opening the shipping drawer places focus on the first useful control or drawer heading.
- Tab and Shift+Tab move through drawer controls in a predictable order while the drawer is open.
- Focus does not move to background page controls until the drawer is closed or completed.
- Closing or completing the drawer returns focus to a logical next control in checkout.
- The original VPAT exception can be retested and marked resolved by the product accessibility owner.

Generate a draft ticket from this VPAT row

Common VPAT row patterns

Partially supports due to repeated component defect

Ticket framing:
Create one component ticket when the same problem appears across many screens.

Evidence to include:
- VPAT criterion and support status
- Representative screens or URLs
- Component name or design system token
- One concrete reproduction path

Acceptance criteria:
- The shared component is fixed at source.
- Representative screens from the VPAT evidence are retested.
- Any remaining exceptions are listed as separate follow-up work.

Does not support due to document or exported file

Ticket framing:
Create a document remediation ticket if users need the file to understand, buy, submit, or comply.

Evidence to include:
- Document name, version, language, and page range
- Missing tags, reading order, table headers, form labels, title, language, or alt text
- Tool or manual review path used in the ACR evidence

Acceptance criteria:
- The fixed document has a logical structure and reading order.
- Tables, forms, links, and images expose the needed relationships and alternatives.
- The report owner can retest the exact ACR exception.

Support statement is unclear

Ticket framing:
Do not create an engineering ticket from vague VPAT language alone. Create an investigation ticket that asks for reproducible evidence.

Acceptance criteria:
- The affected feature, user task, platform, and assistive technology context are identified.
- The finding is either converted into a remediation ticket or closed with documented evidence.

Paste-ready input for the generator

Raw finding:
VPAT / ACR row:
Criterion:
Support status:
Exception note:
Affected product area:
Observed user impact:
Retest method:

Ticket goal:
Draft a remediation ticket that preserves the conformance evidence but gives engineering a concrete user task, reproduction path, and acceptance criteria.