Limits of CKEditor 5 inline validation announcement for screen readers in Drupal 10.x

When using Drupal’s CKEditor 5 inline editor, form validation messages (e.g., required‑field warnings) appear visually but are not automatically exposed to screen‑reader users via an ARIA live region.

The goal is to determine whether the core should add a polite live region to announce these errors, and if so, what markup and placement would satisfy accessibility guidelines without interfering with existing visual styling or custom overrides.

Uncertainties remain about the optimal container role, the timing of the announcement relative to the visual alert, and how to handle cases where themes or modules already provide their own live regions.

• Should Drupal core inject an aria-live="polite" element alongside each inline validation message, or rely on a single global live region for all editor errors?
• What HTML role or attributes (e.g., role="alert") best convey the error while preserving the polite behavior?
• How can the implementation avoid duplicating announcements when a custom theme or contributed module already adds a live region for the same message?