DataStatePanel

DataStatePanel has no keys of its own. The action in the empty and error statuses, and the caller's content once ready, are reached in reading order.

The root takes no aria-busy while loading. Screen readers may hold back a busy element's live regions until it is no longer busy, which would silence "Loading", and nothing inside the root is half-built while it loads: the content is not rendered at all.

What axe won't catch, from the contract, each with how this component meets it:

• Everything the eye is told, the ear is told, for every shape each prop accepts: the message is the visible title, sentence and action, read in place and announced through the message part's role="status"; a caller's icon is aria-hidden inside EmptyState and the title says what it shows.
• Every landmark and named region has an accessible name: none here; the root is not a landmark, and a status region takes no name.
• Every default label can be overridden: loadingLabel, noDataLabel and loadFailedLabel.
• Every shape the type accepts renders, in every variant: children, description and action each render a string, an element and an array; description and action land in EmptyState's div parts, so block content is valid in them.
• A hidden copy kept for animation is aria-hidden, and a collapsed region is inert: none here; a status not shown is not rendered at all, so nothing hidden stays in the tree.
• Native semantics first: plain divs and EmptyState's p title; role="status" only on the message part, where no element says it; the action holds the caller's own button or a href.
• Focus moves in reading order and returns on close: the message comes before the content in the DOM, the action after the sentence; when a change of status removes the element that had focus inside the message, focus moves to the message part (CR-6), never to the page's top.
• Every target is at least size.target-min square: DataStatePanel has no target of its own; the action's targets are the caller's components, which keep their own sizes.
• Loops stop when the system asks for less motion: none here; nothing moves.

Each status but ready shows one string of its own as the EmptyState's title. loading is in packages/perron/src/locale/en.ts already; noData and loadFailed are new keys, and agents write their Danish, Swedish and Norwegian.

The empty status's owned string is noData, "No data to show", with noDataLabel for the caller to name what is missing. It says only what the panel knows, that the data came back with nothing in it, without claiming why; a caller that knows says more through noDataLabel or description. The error status's owned string is a new key, loadFailed, "Could not load the data", not "Data feed problems". "Data feed problems" is the fixed name of a kind of disruption on a line, which content design keeps for that alone; a panel whose request failed may have lost the network, not the feed, and "Could not load the data" says only what happened.

For a caller using the pattern, with the reason. Each row is a rule: a must row's Don't is never right, a should row's needs a reason, and Checked by says what catches the Don't in a caller's code.