Navigation section present under hamburger are programmatically define as table :A11y_.NET maui_User can get all the insights of Dashboard_Devtools

[kapilvaishna]

Please do not close this bug. This bug should only be closed by Trusted Tester after verification.
"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."

GitHub Tags

#A11yTCS; #A11yMAS; #WCAG1.3.1; #Devtools; #BM_.NETMaui_Mac_JUL2025; #DesktopApp; #Device; #FTP; #A11ySev2; #.NET MAUI SDKs; #Mac;

Environment Details:

Application: Developer Balance (.NET Maui)
MAC
M2

Repro Steps:

1. Install and open the Developer Balance app
2. TAB till Hamburger control and press ENTER key.
3. Inspect the expanded section
4. Observe the issue

Actual Result:

Navigation section present under hamburger is not a table but programmatically define as table.

Expected Result:

For left navigation section role should not be define as table.

User Impact:

Screen reader use will face difficulty, if they navigate to navigation section and screen reader will announce table they will try to access table but there is not table.

Attachment

This issue has been verified in Visual Studio Code 1.101.0 with MAUI versions 9.0.0 and 9.0.90. It can be reproduced on MacCatalyst platform.

[SuthiYuvaraj]

Hi @kapilvaishna, The issue “Navigation section present under hamburger is programmatically defined as a table” is not related to .NET MAUI directly, but rather is a native accessibility issue specific to the Mac platform.

In this scenario, the navigation menu rendered under the hamburger icon is exposed to accessibility services as a table, which may not be the expected semantic structure. Since this behavior comes from the underlying macOS implementation, it cannot be fully controlled at the MAUI framework level.
This concern has already been reported and tracked in the following issue: dotnet/maui#16245.

[PureWeen]

@kapilvaishna can we close this one based on @SuthiYuvaraj 's findings?

[kapilvaishna]

@PureWeen we can not close this bug as this bug depends on external team could you please share external team STID/STID name and if external team is third party please share the third part name and sample app to log external bug as external bug process.