[VS-NfD] Mode "marked": flag profile-violating configuration options in the UI #244

New Issue

fable-5 · 2026-07-30T11:59:31+02:00

fable-5 commented

2026-07-30 11:59:31 +02:00

Plan reference: M32, option a)
ADR: the one from #243
Effort: M (2 AT)
Depends on: #243

Context

Option a): every configuration option stays available, but any option whose current value - or whose selection - would violate the VS-NfD reference profile carries a clear marking, so the operator sees the deviation at the moment of decision, not in an audit months later.

Acceptance criteria

In mode marked, every catalog-listed control in the admin and pond settings shows an accessible marking when its value violates the profile: text + icon, never colour alone, i18n de+en, announced to screen readers via the control's accessible description (ADR 0017).
Selecting a violating value marks it before saving (the operator is warned at the point of choice).
A summary line on the admin settings page counts the current violations and links to the hardening guide.
No behavioural change to the options themselves - marking only.
e2e: marking appears and disappears with mode and value; the a11y pack covers the marked state.

Out of scope

Hiding or enforcement (follow-ups), pond-level content marking (that is classification, M26).

**Plan reference:** M32, option a) **ADR:** the one from #243 **Effort:** M (2 AT) **Depends on:** #243 ## Context Option a): every configuration option stays available, but any option whose current value - or whose selection - would violate the VS-NfD reference profile carries a clear marking, so the operator sees the deviation at the moment of decision, not in an audit months later. ## Acceptance criteria - [ ] In mode `marked`, every catalog-listed control in the admin and pond settings shows an accessible marking when its value violates the profile: text + icon, never colour alone, i18n de+en, announced to screen readers via the control's accessible description (ADR 0017). - [ ] Selecting a violating value marks it before saving (the operator is warned at the point of choice). - [ ] A summary line on the admin settings page counts the current violations and links to the hardening guide. - [ ] No behavioural change to the options themselves - marking only. - [ ] e2e: marking appears and disappears with mode and value; the a11y pack covers the marked state. ## Out of scope Hiding or enforcement (follow-ups), pond-level content marking (that is classification, M26).

fable-5 added this to the M32 - VS-NfD: deployment profile & UI modes milestone 2026-07-30 11:59:31 +02:00

fable-5 added the

labels 2026-07-30 11:59:31 +02:00

fable-5 referenced this issue

2026-07-30 11:59:32 +02:00

[VS-NfD] Mode "hidden": hide profile-violating options and mark the hiding #245

fable-5 referenced this issue

2026-07-31 18:24:22 +02:00

#243: VS_NFD_MODE and the machine-readable hardening-profile catalog #292

fable-5 referenced this issue from a commit

2026-07-31 18:33:30 +02:00

#244: mode marked — flag profile-violating configuration in the UI

fable-5 referenced this issue

2026-07-31 18:33:47 +02:00

#244: mode marked — flag profile-violating configuration in the UI #293

fable-5 referenced this issue from a commit

2026-07-31 18:49:31 +02:00

#244: mode marked — flag profile-violating configuration in the UI

fable-5 commented

2026-07-31 19:06:36 +02:00

Done via PR #293 (merged after #292, CI run 631 green — including the new vs-nfd-marking e2e pack in CI's marked-mode stack and the a11y admin scan covering the marked state).

All acceptance criteria met: accessible marking (text + icon, never colour alone, i18n de+en, aria-describedby) on every catalog-listed admin control incl. the Nextcloud backup toggle; point-of-choice marking against the current unsaved value (verified in e2e); summary line with violation count + hardening-guide reference on the profile card; no behavioural change to the options. Both e2e halves (marked/off) also verified live locally before push.

Done via PR #293 (merged after #292, CI run 631 green — including the new vs-nfd-marking e2e pack in CI's marked-mode stack and the a11y admin scan covering the marked state). All acceptance criteria met: accessible marking (text + icon, never colour alone, i18n de+en, `aria-describedby`) on every catalog-listed admin control incl. the Nextcloud backup toggle; point-of-choice marking against the current unsaved value (verified in e2e); summary line with violation count + hardening-guide reference on the profile card; no behavioural change to the options. Both e2e halves (marked/off) also verified live locally before push.

fable-5 closed this issue

2026-07-31 19:06:36 +02:00

Sign in to join this conversation.