fortify

Start by distinguishing error types: validation, system, network, permission, and timeout errors each need different messaging and recovery paths. Every error state should specify what the user sees, what they can do, and how they recover, never a generic 'Something went wrong' message.

A state inventory enumerates all states of a screen or component: default, empty, loading, partial, error, success, offline, disabled, and overflow. For each state, document what the user sees, available actions, and the recovery or progress path in a matrix format.

Run systematic stress prompts across six categories: content extremes, volume extremes, time and latency, network conditions, device constraints, and unexpected user behavior. Record each scenario as pass, fail, or untested with recommended behavior for failures.

No, accessibility methodology and assistive technology requirements belong to a separate inclusion skill. Fortify overlaps on real-world conditions like slow connections and small screens, but WCAG conformance and screen reader experience are out of scope.

Fortification covers internationalization readiness: text expansion tolerance, RTL layout implications, date and number formats, and character set support. Actual translation and cultural adaptation are handled separately by a localization process.