Evidence report
One entry per success criterion: method, result, and the artefact behind it (a recording, a data table, a screenshot with annotations). Exceptions carry the reviewer's decision and reasoning.
Product
From accessibility findings to reviewed fixes.
We assess agreed journeys against WCAG 2.2 A and AA, repair scoped defects in your code and document the verification. The report identifies coverage, limitations and any additional procurement requirements.
What we check
All four WCAG principles, in real browsers and real screen readers.
Automated rules cover part of the assessment. Assistive-technology checks and human judgement cover questions that rules alone cannot resolve. The report records the method and scope of each result.
| Principle | Examples of what we test | How |
|---|---|---|
| Perceivable | Text alternatives, captions, contrast of text and controls, reflow at 400% zoom, content order | Rules, rendered-colour analysis, screen-reader runs |
| Operable | Keyboard access, focus order and visibility, skip links, target size, no keyboard traps, time limits | Recorded keyboard runs, rules |
| Understandable | Page language, predictable navigation, form labels, error messages and suggestions | Screen-reader runs, human review of wording |
| Robust | Valid names, roles and values for custom components; status messages announced | Accessibility-tree inspection, NVDA, JAWS, VoiceOver |
What you receive
Three deliverables, one source of truth.
Pull requests
Fixes arrive in your repository as small, reviewable pull requests with a description of the defect, the criterion, and the verification that passed after the change.
Conformance report (ACR)
A completed VPAT 2.5 in the edition your buyer needs (WCAG, 508, EU or INT), backed by the evidence rather than by self-assessment.
One fix, as it reaches your repository
38 <p className="price">{formatPrice(product.price)}</p>39 <div className="card-actions">40Removed: <button className="add" onClick={() => addToBag(product)}>41Removed: <BagIcon />40Added: <button type="button" className="add" onClick={() => addToBag(product)}>41Added: <BagIcon aria-hidden="true" focusable="false" />42Added: <span className="visually-hidden">Add to bag, {product.name}</span>43 </button>44 </div>Verified: NVDA reads "Add to bag, Linen apron, button". Recorded run attached to the report.
WCAG 4.1.2 Name, Role, Value. Sample data from our demo store; the full sample report shows the rest.
Sample
What a page looks like in the report.
Each page or screen gets its own tally. Flagged items are never hidden; they are the work your reviewer does.
Account settings, billing tab
React app · desktop · 14 Oct 2026
39 checks37 verified2 flagged
- All 23 form fields have programmatic labels
- Every control works with the keyboard alone
- Focus order follows the visual order
- Toggle outline is 2.1:1 against the panel
Methods: Automated rules, JAWS + Chrome, VoiceOver + Safari, keyboard-only run
Checkout, step 2 of 3
Shopify storefront · desktop and mobile · 14 Oct 2026
47 checks45 verified2 flagged
- Text contrast meets 4.5:1 on every text node
- Every image has a usable text alternative
- Focus is visible on all 61 focusable elements
- Quantity stepper has no accessible name
Methods: Automated rules, NVDA + Chrome, VoiceOver + Safari, keyboard-only run
Works with
Your stack, not a script tag.
- Storefronts: Shopify themes and apps, WooCommerce, Magento, custom checkouts
- Web apps: React, Next.js, Vue, Angular, server-rendered sites, design systems
- Content sites: WordPress, Webflow, Drupal, documentation sites
- Code hosting: GitHub, GitLab and Bitbucket pull requests; read-only access is enough to start
- Mobile apps: iOS and Android screens tested with VoiceOver and TalkBack (design-partner stage)
See it on your own product.
Start with one agreed user journey at no cost through early 2027. We agree the defects, deliverables and your review effort before the pilot begins.