Does 2.5.3 fail for user menu control when the text on the control is not included in accessible name?

[Ashritha-98]

I am seeking clarification on scenario related to success criteria 2.5.3 Label in Name.

In this implementation, a profile menu button has the text "AC" acting as the visible label which is the short form of the profile holder name.
But the current accessible name of the button is "User menu for Antara Choudhury" which does not contain the "AC" text in it.
As this is not a logo or universally recognized icon and as the visible label text is missing from the programmatic name, speech input users who say "Click AC" will likely find the control unresponsive. So, can this be failed under 2.5.3 Label in Name and suggested with an accessible name such as "User menu for AC Antara Choudhury" which has the visible label text included in it?

Your insights and guidance on addressing this issue would be greatly appreciated.

[patrickhlauke]

yes, it fails unless the text as seen visually on the control is present somewhere in the accessible name