fix(a11y): announce workspace condition sub-steps to screen readers

Follow-up to the workspace status live-region fix. Condition sub-steps
(StorageReady, RoutingReady, DeploymentReady, etc.) were not being announced
because ProgressStepTitle received mixed children [string, ReactElement] and
the previous typeof check only handled plain-string children.

Changes:

ProgressStepTitle:
- Add extractText() helper that recursively extracts plain text from any
  ReactNode (string, array, or React element with nested children).
- Replace typeof children === 'string' check with extractText(children) so
  the live region is populated regardless of whether children are plain strings
  or mixed string + JSX nodes.
- Add optional parentStepName prop. When set, the live-region announcement
  reads "Step: {parentStepName} / {stepText}" so screen readers hear the full
  context for sub-steps (e.g. "Step: Waiting for workspace to start / StorageReady").

StartingStepWorkspaceConditions:
- Pass parentStepName="Waiting for workspace to start" to ProgressStepTitle so
  each condition sub-step is announced with the parent step context.

Assisted-by: Claude Sonnet 4.6
Signed-off-by: Oleksii Orel <oorel@redhat.com>

Author: olexii4

packages/dashboard-frontend/src/components/WorkspaceProgress/StartingSteps/WorkspaceConditions/index.tsx

@@ -176,6 +176,7 @@ class StartingStepWorkspaceConditions extends ProgressStep<Props, State> {
           hasChildren={hasChildren}
           isError={isError}
           isWarning={isWarning}
+          parentStepName="Waiting for workspace to start"
         >
           {this.name}
           <PureSubCondition distance={distance} title={subConditionTitle} />

packages/dashboard-frontend/src/components/WorkspaceProgress/StepTitle/index.tsx

@@ -21,11 +21,29 @@ export type Props = PropsWithChildren<{
   hasChildren?: boolean;
   isError?: boolean;
   isWarning?: boolean;
+  /** When set, the live-region announcement reads "Step: {parentStepName} / {step text}".
+   *  Use for condition sub-steps so screen readers hear the full context. */
+  parentStepName?: string;
 }>;
 
+/** Recursively extracts plain-text content from any ReactNode. */
+function extractText(node: React.ReactNode): string {
+  if (typeof node === 'string' || typeof node === 'number') {
+    return String(node);
+  }
+  if (Array.isArray(node)) {
+    return node.map(extractText).join('');
+  }
+  if (React.isValidElement(node) && node.props.children) {
+    return extractText(node.props.children as React.ReactNode);
+  }
+  return '';
+}
+
 export class ProgressStepTitle extends React.Component<Props> {
   render(): React.ReactElement {
-    const { children, className, hasChildren, distance, isError, isWarning } = this.props;
+    const { children, className, hasChildren, distance, isError, isWarning, parentStepName } =
+      this.props;
 
     let readiness = styles.ready;
     if (distance === 0) {
@@ -53,10 +71,17 @@ export class ProgressStepTitle extends React.Component<Props> {
             The region is always present so screen readers register it on page load;
             content is only set when the step is active (distance === 0) so the
             announcement fires exactly once per step transition.
+            For sub-steps (parentStepName set) the format is
+            "Step: {parent} / {substep}" so screen readers hear the full context.
             The "Step: " prefix ensures the live region text differs from the visible
             step title, preventing ambiguous matches in DOM queries. */}
         <span role="status" aria-live="polite" aria-atomic="true" className="pf-v6-screen-reader">
-          {distance === 0 && typeof children === 'string' ? `Step: ${children}` : ''}
+          {(() => {
+            if (distance !== 0) return '';
+            const stepText = extractText(children);
+            if (!stepText) return '';
+            return parentStepName ? `Step: ${parentStepName} / ${stepText}` : `Step: ${stepText}`;
+          })()}
         </span>
       </>
     );