{"version":"2.1.238","anchor":"screen-reader-announcements-are-queued-and-held-back-at-star","canonical_anchor":"screen-reader-announcements-are-queued-and-held-back-at-star","heading":"Screen reader announcements are queued and held back at startup","tier":"use","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/screen-reader-announcements-are-queued-and-held-back-at-star","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Screen reader announcements are queued and held back at startup\n\nScreen reader announcements are queued and held quiet during startup, under the `axScreenReader` setting.\n\n**What**\n\nSpoken announcements now go through a queue with a bounded buffer instead of firing immediately, and a quiet window suppresses them during startup until an explicit end point. This runs under the existing `axScreenReader` setting.\n\n**Details**\n\n- The controller records when the first announcement was written and when the startup quiet window opened, and clears both on reset.\n- Whether accessibility output is enabled is now passed in as a function rather than read from a module-level global.\n\n**Evidence**\n\n`startupQuietOpenedAtMs`\n\n- Area: Elsewhere\n- Names: `axScreenReader`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}