Flutter 3.10 liveRegion: should CustomPaint updates rely on manual Semantics wrapping?

Direct answer

Yes – wrapping a CustomPaint in a Semantics widget with liveRegion: true is a supported, documented pattern in Flutter 3.10 and is expected to remain stable unless the framework explicitly changes how RenderCustomPaint participates in the semantics tree.

Confirmed facts

• CustomPaint is a RenderObjectWidget; its render object (RenderCustomPaint) is inserted into the semantics tree like any other render object.
• Setting liveRegion: true on a Semantics widget causes the framework to announce changes only when the semantics node itself changes (via markNeedsSemanticsUpdate or a rebuild with different properties).
• No painter‑level liveRegion API exists yet; the manual wrapper is the current recommended approach.

Likely explanation

The semantics system treats the Semantics widget as a container node. When its properties change, the node is marked dirty and the accessibility service receives an update. Because CustomPaint does not expose its own semantics properties, the wrapper is the only place to attach liveRegion. Repainting the canvas does not automatically trigger semantics updates unless the wrapper’s configuration changes, which is why you can throttle announcements by controlling when the wrapper rebuilds.

Recommended steps for your dashboard

1. Wrap the CustomPaint with a Semantics widget that sets liveRegion: true and, if the painted area should be announced as a single unit, container: true.
2. Optionally place a RepaintBoundary around the CustomPaint to isolate canvas repaints from the rest of the widget tree.
3. Throttle the announcements: either debounce the setState that changes the painted values (e.g., 200 ms) or only call setState when the value crosses a meaningful threshold.
4. Verify on a device with a screen reader (TalkBack/VoiceOver) that updates are announced politely and not flooded.

One missing diagnostic detail

Do you need the entire painted area to be treated as a single accessibility node? If yes, keep container: true; if you want each logical sub‑element (e.g., separate gauges) to be announced individually, you would need to split the painting into multiple CustomPaint instances or provide custom semantics via Semantics children. This detail determines whether the simple wrapper is sufficient or if a more granular approach is required.