Meridian Field Services: instructional example, not project evidence
The regime mapping is footprint-specific; the NFR catalog committed the level. This artifact operationalizes it and never re-decides it.
Regime mapping, this footprint: Ontario's accessibility law (AODA) binds the employer's web content at WCAG AA for an Ontario-based workforce (the mandatory regime, per the compliance scoping[1]); the enterprise contract's procurement schedule elects a conformance report on request. Target: WCAG 2.1 AA, committed at NFR-U3[2] and cited, not re-decided; 2.2's new AA criteria adopted as forward guidance, flagged distinctly.
| Criteria | Bound surface | Class |
|---|---|---|
| 4.1.2 name/role/value · 2.1.1 keyboard | Every interactive design-system component | component-first: the fix propagates |
| 4.1.3 status messages · 2.4.3 focus order | The dispatch board (SCR-001[3]), the high-risk surface: live position updates announce without stealing focus; suggestion-panel updates are polite live regions; the degradation notice (suggestions_unavailable[4]) is a status message, not a focus trap | page + component |
| 1.4.3 contrast · 1.4.11 non-text contrast | The board's status chips and map bands (SCR-001 tokens[5]) | component |
| 3.3.1 error identification · 3.3.3 suggestions | The intake form (SCR-003[3]; VR-04 inline errors[6]) | page + component |
| 2.4.7 focus visible | All four screens | page |
Page rules exist only for landmarks, titles, and focus order; everything else lives at the component.
Tested versus best-effort is explicit per cell; the tested set carries its audience rationale: dispatcher workstations run Windows and Chrome; technicians carry iPhones.
| Combination | Class | Note |
|---|---|---|
| NVDA + Chrome · Windows | TESTED | The dispatcher floor |
| VoiceOver + Safari · iOS | TESTED | The technician app |
| Keyboard-only | TESTED | Both platforms |
| JAWS + Chrome | best-effort | No current JAWS users on the floor; flips to tested if the enterprise buyer's procurement requires it (a costed decision, stated) |
| TalkBack + Chrome · Android | best-effort | No Android fleet at pilot |
| Magnification 200% | best-effort | Spot checks |
| Component contract (story ACs inherit by citation: acceptance rows[7]) | Spec |
|---|---|
| Board row | Role row; name from the job id and status; selection announced |
| Suggestion card | Button role; accessible name carries rank and technician code; activation assigns |
| Toast / notice | Status message, polite; auto-dismiss no faster than the reading floor |
| Map band | The text alternative is the band list; the map is never the only path (content slots[5]) |
Automated is the floor and says so; the tiers are the plan.
| Tier | Method · cadence | Owner |
|---|---|---|
| Automated scanning | In the pipeline, every merge; the floor: roughly a third of criteria by count, stated so nobody mistakes the green gate for conformance (testing gates[8]) | Committing engineer |
| Manual expert audit | Before pilot exit: the NFR fit criterion's audit (NFR-U3[2]) | QA owner |
| AT testing | The tested matrix, per release candidate | QA with the UX owner |
| Users with disabilities | One session set, pilot weeks 3 to 4, dispatchers who use assistive tech (recruited via the accessibility office); findings route to the register (register[9]) | UX owner |
Conformance report: produced on the enterprise buyer's request per the elected schedule; edition matched to the buyer. A11y cases live in the test register by id: documented here, executed there.
| Question | Owner | Answer by | Blocks |
|---|---|---|---|
| Does the enterprise buyer's procurement schedule require the conformance report at contract renewal (which flips JAWS to tested)? | QA owner with the sponsor | Oct 15, 2026 | The AT matrix's JAWS row only |