Flutter 3.10 liveRegion: should CustomPaint updates rely on manual Semantics wrapping?
Accessibility boundary for custom painters Flutter 3.10 added the liveRegion property to SemanticsConfiguration , letting developers mark dynamic content so screen readers announce changes. I am building a dashboard where a CustomPaint canvas redraws values continuously, and I want those updates announced politely without flooding the accessibility tree. The