The one surface a client sees

Same semantic layer, different reading posture: the tool is dense because an operator lives in it, the report is long-form because a client reads it once, carefully, and forwards it to procurement. Hestia is the base identity here too. The client accent is a slot inside it, not a reskin.

Where the client accent may appear

Permitted

The cover rule and the client name
Section-number markers in the document spine
The running header on printed pages

Never

Severity, status, staleness, confidence — any semantic token
The Verified-by-Human stamp
Body text, links, or anything carrying state

A finding must read the same in the tool, in the report, and in a Jira embed. An accent that could tint severity would break that, so the slot is defined by exclusion: decoration and identity, never meaning.

The accent guard

A client hands over one brand colour and it is whatever it is. The report derives two values from it: the raw colour for rules and blocks, and a darkened variant for any text use — the same split Signal Amber takes in the tool. Cover rules are decoration and carry no information, so any brand colour is admissible there; where the raw value falls under 3:1 the rule gains an ink companion so the cover still reads structurally in greyscale and in print.

supplied

#B3122F

Northwind Retail — used as supplied

raw 6.5:1 · text as supplied

supplied

#4CAF50

Fieldhouse Group — derived + ink rule

raw 2.62:1 · text #38813B 4.53:1

supplied

#E8B400

Halden Civic — derived + ink rule

raw 1.81:1 · text #8E6E00 4.52:1

Document specimen

Body text is 18/30 at 17.4:1, clearing the enhanced-contrast AAA target the brief sets for long-form reading. Disclosure is built on native details elements — keyboard-operable and correctly exposed with no script, so the report stays readable with JavaScript disabled and the dogfood gate has nothing to catch.

            Northwind Retail
            Accessibility audit · version 4 · 2026-08-08
          

Three findings regressed since June.

The sample of 42 pages was re-audited against WCAG 2.2 AA on 8 August. Thirty-one findings from version 3 are fixed and verified. Fourteen are new. Three previously fixed findings have returned, all in the checkout flow, and all three are the same missing accessible name on a rebuilt component.

New

Fixed

Regressed

Unchanged

01 Executive summary · always open Expand all sections

02 Methodology EAA annex VPAT / ACR off

Conformance target WCAG 2.2 AA. Sample of 42 pages frozen 2026-05-30 under WCAG-EM, drawn from 1,180 discovered URLs across seven categories. Audit dates 2026-08-06 to 2026-08-08. The active check set is axe-core 4.x plus eleven custom checks, listed in full below.

Annexes are toggled per engagement: the EAA Conformity Declaration is included here, the VPAT/ACR is not. Both render as sections of this document rather than separate files, so the deliverable stays one self-contained artifact.

03 What changed since last audit Open

All three regressions trace to the payment component rebuilt on 14 July. The finding below carried a ticket in version 3, was verified fixed, and has returned unchanged.

critical regressed AA ACME-2291

Interactive control has no accessible name

4.1.2 Name, Role, Value · level A · /checkout/payment

04 Findings by criterion 48 findings

05 Human verification verified by humanv4 · 22 criteria

06 Focus-order appendix 42 pages

07 Inventory appendix 42 of 1,180 URLs

            Hestia Media Group · dollyVision
            Self-contained · 18.2 MB of 25 MB
          

Findings collapsed by default

Section 03 opens; 04 through 07 are shut. The client lands on what changed, not on forty-eight findings. Expand-all sits above the spine for the reader who wants everything, and for print.

The ticket key is text first

A reader without Jira access loses nothing: the key stays legible, the evidence is in the report, and the link is a convenience. In print the URL is not appended — the key is the reference.