Help & accessibility

State glossary

What public status language means

Loading: Content is being requested. It does not mean zero, empty or no result.
Empty: The collection has no public items. It is not a game outcome.
Stale: Last-known facts can be read, but currentness is not established and relative time is suppressed.
Unavailable: No safe current projection can be supplied. The page does not infer a cause.
Under review: A current publishable outcome is unavailable; evidence and likely direction remain protected.
Checking final status: A status read is being requested; a local clock has not declared closure.

Accessibility conventions

Built for more than a pointer and a wide screen

Keyboard

Semantic links, visible focus, logical order, skip navigation and 44px primary targets.

Screen readers

One page heading, labelled landmarks, real status/alert roles, text state cues and meaningful time elements.

Zoom & reflow

Content reflows at 320 CSS px and supports 200% text without two-dimensional page scrolling.

Motion & contrast

Reduced-motion preferences remove non-essential animation; semantic colors retain AA-oriented contrast.

Timing

The hard close cannot be extended by a client. Exact absolute time and early explanation reduce timed pressure.

Language & script

Ethiopic and Latin font fallbacks, long-copy layouts and locale-independent message IDs are ready for approved catalogs.

Localization status

English fixture copy only

No V1 launch language or controlling translated content has been selected by this implementation. A requested unapproved locale falls back explicitly to the English fixture catalog; machine translation never silently replaces governed rules or policy content.

Result review guidance

This fixture cannot receive a result dispute.

The governed ordinary dispute window is publication plus exactly 24 consecutive hours with strict-before comparison. Unsupported contact does not pause, extend or reopen it; only accepted material review creates authoritative tolling. A production evidence/support route remains separate authority and is intentionally not invented here.