Finnish WebView accessibility and performance
Overview
This page defines accessibility and runtime behavior requirements for bookkeeping UI in browser and WebView contexts.
Accessibility and keyboard contract
Grid, form, and dialog interactions must be keyboard-first and follow predictable focus order. Visible focus indicators are required, and status/error communication must not rely on color alone.
Long-running operations must expose accessible status updates. Chart views cannot be the only representation of accounting-critical information; equivalent tabular representation must exist.
Performance baseline
The UI must stay responsive in data-heavy list workflows and large accounting datasets. List virtualization and server-assisted filtering/sorting are required where row volume is high.
WebView runtime behavior
Embedded WebView operation must handle unstable connectivity and constrained local storage. Caching strategy should prefer deterministic stale-while-revalidate behavior for safe read paths and static assets, with explicit cache-budget management.
Offline-aware behavior must include clear connectivity state, safe queueing where possible, and deterministic conflict handling for competing edits.
Validation approach
Validation combines automated accessibility checks with manual keyboard-path testing for grids and dialogs, plus performance profiling on representative data volume and WebView targets.