VoiceOver screen reader just reads out 'button' on trigger component.

[trcoffman]

Hi there,

Our app is using Zeego 1.10.0 and I'm having trouble with my trigger component just saying 'button' on iOS when I focus it with VoiceOver.

How can I get the aria label on the trigger to apply?

I really love this library and appreciate all your hard work. I just want to make sure that I can deliver an accessible experience as many users of our app are people with visual impairments.

[nandorojo]

Hey! Want to poke into the code for createIosMenu? Happy to merge a PR for this!

[trcoffman]

@nandorojo I just got the example app running, so this at least works perfectly fine in the example app on v3. We are using v1.10.0 in our app, so i'm not sure yet whether or not I'm doing something wrong or if this isn't supported in older versions.

I'll investigate further but I would guess most likely I'm doing something wrong.

[nandorojo]

Upgrading to Zeego 3 from 1 only really has breaking changes if you use Web. If you don’t use web, it’s basically just a version bump and type fixes (plus the native library version changes)

[trcoffman]

We do use the web version. It looks like upgrading won't fix the issue though. I experimented with turning off new architecture in the example app, and discovered that the new architecture has to be enabled for DropdownMenu.Trigger to be accessible.

If I disable new architecture, the example app shows the same issue we are having in our app, where the Dropdown's trigger simply reads out as 'button'.

What's interesting is that the ContextMenu's trigger does seem to work under old architecture. The issue seems to be only with DropdownMenu.

I'll dive deeper next week. We can't move to new architecture yet as we have too many dependencies that have regressions when going to new architecture.

[nandorojo]

Is it just a matter of forwarding down props to the iOS library?

[trcoffman]

It's too early to say what the issue is. I have no idea yet.

[trcoffman]

@nandorojo I think the issue likely has to be investigated & fixed in @react-native-menu/menu package.

Depending on what I come up with when attempting to fix that library, Zeego might also need changes as well, but I don't know what those would look like yet.

[trcoffman]

@nandorojo I didn't realize that you only use @react-native-menu/menu on android.

I was able to figure out what the problem is there in that library w.r.t. IOS accessibility. But it looks like I was debugging the wrong library. However, I'm betting that the same fix would probably also apply to react-native-context-menu which is to make the UIButton that wraps the trigger view have self.isAccessibilityElement = false.