Files
jobtrackingapp/docs/ui-modernisation/visual-correction/ADMIN_HEADINGS_REVIEW.md
T

2.1 KiB

Administration heading hierarchy

Runtime c7e8627ca782b37ed553299a1db93af192e420e4 on codex/a3-ui-10. V21 covers Users, Audit, System and Processing. Each route now uses the shell's single page title and existing description. Section headings follow it directly. The System action buttons remain together, and refresh restores focus to its initiating control when available. If the control disappears, focus stays on the named System region. Role guards, actions, filters, tables and data contracts are preserved.

The old export reproduced two exact “Users” headings at 320 px. The successor pilot at 320 and 1440 px passed 18 captured states across both configurations. The same verifier checks one exact route title at level 1, the existing description, System keyboard refresh, and the earlier fixture checks for last-admin actions, populated/empty audit, normal/unavailable System, benchmark/settings views and Processing detail focus.

Passed 66 targeted Jest tests across six suites, type-checking, full lint and the static export build. The initial type check rejected a Jest role selector option. The passing rerun uses an anchored name matcher.

The full matrix passed 36 configurations and 324 captures, including axe checks with zero violations. No page errors, write requests or export requests occurred. The 144 intentional System 503 responses and 216 unavailable company reads remain separate from passing checks. The two-config pilot overlaps the matrix and is not added to its totals.

Compared the built System view at 320 and 1440 px, Users at 390 px and Audit at 768 px against the frozen A3 Administration reference. The single title and open sections match the intended hierarchy. Distinct user records and forms retain their boundaries. The actual application keeps four Admin routes and their real controls. The 768 px Bokmål Audit capture also exposes a separate timestamp wrapping problem, tracked as V25.

All browser responses are synthetic. Review does not qualify role enforcement on a server, live health, provider/model activity or administrative mutations. Creation, action errors, permission states, native devices and final owner acceptance remain open.