[P2] Audit: Dynamic output updates do not consistently announce status to assistive technology

[baixiangcpp]

Imported from the byteflow.tools deep audit on 2026-06-22.

Problem: many tools update output live after input changes or button actions, but status changes are not consistently announced to screen readers. Examples include generated output, validation errors, copy success, run log updates, external request status, and Pipeline Builder step results.

Affected components:

• Tool output panels
• Error banners
• Toast/status messages
• Pipeline Builder run log
• External-request preview status

Reproduction steps:

1. Use a screen reader or accessibility inspector.
2. Run JSON Formatter with valid and invalid input.
3. Generate UUIDs or hashes.
4. Run a Pipeline Builder recipe.
5. Trigger copy/download actions and external preview failure states.
6. Check whether status changes are announced.

Expected behavior: important dynamic changes should be exposed through aria-live or equivalent status roles without excessive noise.

Actual behavior: visual feedback exists, but assistive technology announcements are not consistently verified.

Impact: screen reader users may not know when output changed, copy succeeded, or an error occurred.

Proposed fix:

• Add shared status and error components with aria-live support.
• Mark validation errors with role=alert where appropriate.
• Announce copy/download/run success states.
• Add accessibility tests for dynamic updates.
• Avoid announcing large output text automatically.

Acceptance criteria:

• Core status changes are announced once and clearly.
• Errors are associated with relevant inputs.
• Output updates do not spam screen readers.
• Pipeline Builder run log changes are accessible.

[baixiangcpp]

Closed as completed by the canonical BF audit backlog work. This older non-BF audit issue duplicates work now merged through PRs #209-#219, with the BF issues closed and guard/test coverage in place. The remaining non-duplicate follow-up is #7, which stays open because the upstream Next/PostCSS advisory is not fixed yet.

[baixiangcpp]

Reopening after acceptance review on 2026-06-24. The merged work adds aria-live/status coverage for All Tools, Pipeline Builder run log, file upload status, and representative axe tests, but this older audit issue is not fully satisfied: copy/download/share result states and external-request status changes are still not consistently announced, and related issues #166 and #141 are reopened. Keep this open until shared status/error components announce core dynamic changes once and clearly across outputs, validation errors, copy/download results, Pipeline Builder, and external-request failures without announcing large output bodies.