U11.02.5View changes caused by interaction must be announceddesign

A filter or zoom that changes the chart needs to be announced, since screen-reader users can't just glance

Aliases: change announcement · dynamic update announcement

What it is

In interactive charts, user operations (switching filters, drilling down, zooming) cause view changes—the dataset changes, axes change, the chart type changes. Sighted users see these changes directly; screen-reader users may hear nothing at all: the focus remains where it was, and the announced structure is stale. An unannounced view change means, to a non-visual user, "the operation seemed to do nothing," or worse—"it worked, but I don't know the data has completely changed." Change announcement (aria-live or equivalent) is the closing loop of interactive-chart accessibility: every operation gets an audible receipt.

Why it happens

Change announcement works by converting view-state transitions into an audible event stream: after filtering, announce "filter applied: mobile only, 8 data points remain"; after drilling down, announce "entered: East region, showing 12 months of detail"; after auto-refresh, announce "data updated as of 14:32." The content essentials match the same group's three elements, but the emphasis is a summary of the new state rather than a point-by-point enumeration—users need "what the world looks like now" to plan their next move. Timing and throttling are the implementation crux: rapid consecutive operations (tapping filters repeatedly) trigger rapid successive changes, and announcing each one drowns the others; the sound strategy merges changes within a short window into one summary announcement ("filters updated; now showing East region, 2024"), while the live region's politeness level (polite vs assertive) decides whether announcements interrupt current reading—routine view changes use polite; key state switches the user explicitly triggered may use assertive. Focus management is announcement's sister requirement: when a view change eliminates the focused element (fewer points after filtering), focus must migrate to a sensible position in the new structure with a synchronized announcement, or the user is stranded on a context-free dangling focus.

Where it stops holding

Announcement granularity and frequency need restraint: announcing every micro-change creates auditory noise (isomorphic to alert fatigue); what should be announced are changes that alter the user's operating context (dataset, structure, time range), not every frame of a visual animation. Auto-refresh changes (not user-triggered) need an even more conservative strategy—when background updates are frequent, announce only an "update available" hint and let the user fetch details; interruptive announcements are reserved for user-triggered changes. Multi-chart linked views are another boundary: one filter updating several charts at once would create an announcement storm if announced per chart; the sound approach announces the filter action itself ("filtered to East region"), with each chart's update announced when the user focuses that chart.

Applying it

  • Maintain a change-announcement inventory per interactive chart: which operations cause view changes, what the announcement says, which politeness level is used.
  • Merge high-frequency change announcements (continuous changes within a 500-millisecond window merge into one summary).
  • When a view change invalidates the focus, migrate focus in sync and announce the new location.
  • Verification: complete a "filter → drill down → return" flow using only a screen reader; every step needs an audible receipt—any silent step means announcement is missing.

Related

  • Same group: U11.02.1 Chart elements need a predictable keyboard traversal order · U11.02.2 Traversal should support switching between series and data-point levels · U11.02.3 Announcements must include identifier, value, and unit · U11.02.4 Overall trends need a readable summary layer rather than point-by-point listening
  • Nearby: U7.06.4 Comparison baselines must update in sync when the time range changes · U11.02.3 Announcements must include identifier, value, and unit
  • Search terms: aria-live · status announcement · dynamic content accessibility

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/U11.02.5