`PopupMenu` accessibility is broken in several ways

[mihe]

Tested versions

• Reproducible in: 4.7.beta [bc19229]

System information

Godot v4.7.beta (bc19229) - Windows 11 (build 26200) - Single-window, 3 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 Laptop GPU (NVIDIA; 32.0.15.9186) - AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (16 threads) - 63.21 GiB memory - WASAPI (48000 Hz, Stereo/mono)

Issue description

This is a recording of using the Windows 11 built-in Narrator feature, while interacting with various parts of PopupMenu:

(I recommend unmuting audio, to hear the screen reader.)

Screen.Recording.2026-05-07.163624.mp4

As you can see/hear, there are a number of issues:

1. The accessibility region is not positioned correctly (even without the exaggarated content margins used here).
2. The accessibility region is way off for submenus specifically.
3. The screen reader includes separators when counting the number of list items.
4. When enabling the search bar, the accessibility focus is always on the search bar, unless you interact with a submenu.
5. When filtering with the search bar, the screen reader includes hidden items in the number of list items.

Steps to reproduce

1. Run the MRP main scene with a screen reader
2. Try doing what's shown in the video

Minimal reproduction project (MRP)

popup-menu-accessibility.zip

[mihe]

I've labeled this as a regression due to things behaving differently when enabling the search bar (as introduced in #114236), but I'll admit I'm conflicted about what the correct behavior is supposed to be here, since the current behavior is arguably consistent with things like the project manager and the "Create New Node" dialog, where focus always remains on the search bar, even when using ui_down/ui_up.

Also, there's likely some overlap between this and #119050.

[mihe]

@bruvzg Since you seem to be heavily involved in the accessibility side of Godot, is there any chance you could either help me finish up #119312, or put up a superseding PR of your own to resolve the remaining issues there? I'm not all that familiar with the accessibility API, nor really accessibility conventions in general, and this all turned into more of a time suck than I expected.

[mihe]

Not fixed until #119312 is merged.