Has anyone run into this scenario?
I have an app on my phone where one section is laid out in a grid format, but all others are laid out as a list. This app, which happens to be sponsored by a church, has their Media tab, where they list all their message series, laid out as a grid. If you were to select one of these series, you get its page laid out as a list.
The result of this is that Voice-over is not able to read the main Media tab, and you're left guessing as to which series you've selected. I have enlisted some help to try and get the buttons labeled manually. This works for the first 6 or 7 main listings, but it doesn't work as well after that. If you go into the newer listings and go back, everything works. Once you get past this and try to label the rest, you run into your labels being mismatched. I'm guessing that this is due to the grid layout.
My manual labels do work as a stop gap to get access to something until the app developer updates it.
Evidently, the app displayed this main tab as a list, then switched to a grid layout. The switch didn't work well with Voice-over, so anything shown after a certain number of icons causes the labels to be out of wack.
It seems that the content provider likes the grid layout, but Voice-over is not able to keep up.
Also, only the first few selections are shown. If you go in one of them, then go back out, another selection shows up. Once you get past a certain number, the labels don't work right. Yet the content provider seems to favor this grid layout.
I have suggested that in the next update, the developer give the user a choice. I have also had to remind the developer to pull the labels so Voice-over can get to them.
In short, I have attempted to create my own labels with some help, and I have discussed this with the developer, but that's about all I can do.
I know that there are at least 2 other people that are having this same problem with the app.
If you've run into an app where this has happened, what suggestions would you have? Is there anything else I can do short of what I've already done to ensure that accessibility is not lost whenever it gets updated? Thanks.