20 lines
1.2 KiB
Markdown
20 lines
1.2 KiB
Markdown
# Contract: Operational Visual Extensions
|
|
|
|
Part of [web-visual-baseline](../contract.md).
|
|
|
|
## Operational Extensions
|
|
|
|
- A compact header may include build version, current ISO week, sync state and a display
|
|
privacy toggle. Keep these in normal flex flow so they cannot overlap navigation.
|
|
- Navigation uses links with `aria-current="page"`; in-page actions use buttons.
|
|
Quiet text-colored links are allowed in dense data cells, with visible hover and keyboard
|
|
focus treatment. Do not apply the quiet treatment indiscriminately to every link.
|
|
- Summary metrics may sit above tables; they supplement the records rather than replace them.
|
|
Use the baseline's small radii, surfaces and spacing.
|
|
- If row backgrounds communicate status, use opaque `--ok-bg`, `--warn-bg`, `--crit-bg`
|
|
tokens and retain an explicit status indicator. Do not stack translucent status tints.
|
|
- A discrete probability/level indicator may use filled bars plus its exact numeric value
|
|
and accessible name. This is a defined quantitative encoding, not permission for arbitrary
|
|
per-field colors. Risk status remains a separate concept; product-specific levels and
|
|
thresholds stay in the project's local bible.
|