Tooltip is not defined for "Browse" button. : A11y_Winforms_Sensory Characteristics

[PoojaNamde]

A11y Agency plugin is available to help with accessibility bug remediation.
The required tag has already been added: agency:agent=a11y:a11y-agent@company. Assign the bug to Agency to use it.
Please try it and share feedback on whether the remediation guidance was useful at CAIA11yAgency@microsoft.com.

GitHub Tags:

#A11ySev2; #A11yTCS; #WCAG1.3.3; #Win32; #DesktopApp; #Win11; #WinForms .NET Runtime; #BM_WinForms.NETRuntime_Win32_June2025; #Sensory Characteristics; #agency:agent=a11y:a11y-agent@company; #ES Chat;

Issue Subcategory:

Instructions rely only on shape or icon

User Experience:

Users who cannot perceive visual shapes (blind users, users with certain visual impairments) cannot find the referenced control. Shape descriptions are not conveyed by assistive technology

Repro Steps:

Launch the sample app> Browse button> Observe the issue.

Actual Result:

The Browse button does not have a tooltip associated with it. When users hover over the button, no tooltip is displayed to provide additional context about its functionality.

Expected Result:

A meaningful tooltip should be available for the Browse button and displayed on hover/focus to help users understand its purpose.

How to Fix:

Describe the control by function: “Click the Settings icon.” Supplementary shape references are fine when combined with a functional label.

Environment details:

Application Name: Winforms

Note:

• "Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification."
• "Contact CAI Accessibility Support Channel for Accessibility queries on design, development, test, usability or any processes"
• Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
• "Try ES Chat to learn more about the MAS rule and how to fix the issue. If you need more help, use our Teams channel or office hours."

Attachment:

14692_Issue.mp4

[LeafShi1]

The "Browse" button already exposes a meaningful accessible name ("Browse..."), which is announced by screen readers and allows users to identify and interact with the control without relying on its visual appearance.

WCAG 1.3.3 (Sensory Characteristics) applies when instructions depend solely on shape, size, visual location, orientation, or other sensory characteristics. In this case, the control is identified through its functional name rather than by its icon, shape, or visual presentation.

In addition, screen reader users typically identify controls through accessibility properties such as Name, Role, and ControlType, rather than through mouse-hover tooltips. As a result, the absence of a tooltip does not appear to prevent discovery or operation of the control for assistive technology users.

While adding a tooltip could potentially provide additional contextual information for some mouse users, the button is already clearly named, easily discoverable, and consistent with long-established PropertyGrid interaction patterns. In an information-dense environment such as PropertyGrid, introducing tooltips for editor buttons may also add unnecessary hover-related visual noise without providing significant additional value.

Based on the above, this appears more consistent with a potential usability enhancement than a WCAG 1.3.3 accessibility issue.

@KlausLoeffelmann What do you think?

[nk9699]

@LeafShi1 @KlausLoeffelmann

Thanks for the clarification and detailed accessibility assessment.

To help us meet an upcoming compliance deadline (16-Jul-2026) tied to an active Sev2 accessibility bug, could you please confirm whether the WinForms team plans to pick up this issue for implementation?

If the issue is considered valid and will be addressed by the WinForms team, could you also share the expected ETA or release timeline for the fix?

Alternatively, if the current behavior is considered compliant/by-design and no framework change is planned, an explicit confirmation would be very helpful for our accessibility review and bug disposition process.

We are currently blocked on closure and would appreciate guidance at your earliest convenience. Thank you.