AccessibleName runtime announcement behavior in VB.NET Windows Forms
0 reputation · 02 Feb 2025, 15:58 UTC
AccessibleName runtime announcement in Visual Basic Windows Forms
The goal is to clarify whether a programmatic change to a control's AccessibleName property is reflected in the live accessibility tree immediately, without a focus change or navigation event, in a Visual Basic .NET Windows Forms user-facing workflow.
The Windows Forms accessibility layer exposes AccessibleName through MSAA/IAccessible, but it does not specify that every runtime change must be announced to assistive technology. It is unclear whether the control must recreate its accessibility object or raise a property-change notification before screen readers read the new name. Behavior may also vary by screen reader and by .NET runtime version.
Assume Visual Basic .NET Windows Forms on Windows; legacy VB6 is outside scope. AccessibleName does not replace visible labels, focus order, keyboard access, or an appropriate AccessibleRole.
Does changing AccessibleName at runtime update the live accessible tree immediately without refocus? Is a property-change notification or accessibility-object recreation required before screen readers announce the new name? Does the required behavior differ between .NET Framework and later .NET releases?
