Unable to get pass the personalized adds screen in app-store

By SeasonKing, 16 January, 2024

Forum
iOS and iPadOS

On my IPhone 15 Pro Max, when I launch App-store, it shows a personalized adds page, with dimmed buttons for both enable and disable personalized adds.
There's also a learn more button, which opens another page with even more links and learn more button, but, I don't see any obvious way to get passed this screen.
I need to download apps, and not sure what to do.
Back jesture doesn't do anything.
Would apreciate any help.

Options

Comments

By Brian on Monday, January 15, 2024 - 08:59

This reminds me of a grocery delivery app I have, that occasionally advertises deals, etc, and VO cannot access the 'close' button. What I have to do is disable VO, and single tap the top-left area of the screen.

And that is my first suggestion for you, try disabling VO, and tapping the top-left area of your screen.

My other suggestion, would be to completely close the App Store, and reopen it. Sometimes this will bypass splash screens.

HTH. 😅

By Lee on Monday, January 15, 2024 - 08:59

I had this issue. only happens when you first use appstore. in the end I had to get sighted assistance to solve it. Another app direct from apple that isn't fit for voiceover purpose.

By Siobhan on Monday, January 15, 2024 - 08:59

Turn off voice over as brian said, but this time memorize where the disable or enable button is, depending on your preference. Then try to tap it and toggle on voice over. Also I wonder if screen recognition will be of some use here. Good luck.

By Sebby on Monday, January 15, 2024 - 08:59

You can go to the account page, Personalized Recommendations, and see whether it's on or not. You can then double-tap the switch in your account settings to toggle it (note that it, too, is inaccessible). (The fact that such a critical privacy switch is inaccessible is shameful.)

By Brian on Monday, January 15, 2024 - 08:59

This reminds me of the recent thread about Uber's new terms of service, which is also inaccessible with VO.

Ah, good times. . . 😑

By Siobhan on Monday, January 15, 2024 - 08:59

I'm curious how one button which was poorly mislabeled, is so shameful. My viewpoint is common sense should prevail here. Case in point, I think it was IOS15 something or other, that when you went to set up your contacts with Emergency Bypass, the button was labeled in the binary code. How do I know given I don't write that code? I know enough to understand that there are two numbers used. A 0 for no, a 1 for Yes. Given this information or even just by trial and error, I figure out that Zero means the switch is not toggled on, a 1 means it is. This is why there needs to be not only more people working with any type of disability working in every avenue of this and many companies world wide, but also we can at least understand and accept, things happen and really understand that what might be a fault, is easily dealt with and doesn't need everyone to up in arms. Focus on accessibility as a whole before braking this down into such small issues. Just my two sense.

By Ash Rein on Monday, January 15, 2024 - 08:59

Believe it or not, they actually said turn screen recognition on, and the button was accessible at that point. Little by little they’re making it so that screen recognition becomes more more part of our overall lives where we’re gonna have to start turning it on and off. To do certain things.

By OldBear on Monday, January 15, 2024 - 08:59

I'm just wondering, in what situation would you need to turn Screen Recognition off to do something? I can only think of if it were too verbose, like in an app that already describes images.
I was very pleased to learn the function is built into the newer phones, rather than sending data off to a remote server to be analyzed.

By Sebby on Monday, January 15, 2024 - 08:59

It doesn't need to be intentional, just to be an unforgivable failure of process. Of course I'd like more blind people to be part of the solution; it still doesn't excuse the fact the internal processes at Apple made it possible for an error like that to get out of the barn. Maybe it was a lack of automated accessibility testing, maybe a lack of manual testing, maybe it was the choice to forego audits that would have caught it, whatever the reason. Not to speak of the fact that this switch is so critical (a privacy control) and the user experience hit it represents. I think it's important that we be constructive, but that doesn't mean we should excuse process failures like this. It's one reason I think Apple should have accessibility reviews for the App Store; it would give Apple, itself, a strong incentive to get it right. Just my (not-so-humble) opinion.

By Siobhan on Monday, January 15, 2024 - 08:59

What I find accessible, you might not. What you find accessible might drive me insane. Things are so subjective such as verbosity. I don't want voice over yammering on at me whereas someone else might want it to describe every element and not shut up. Apple's needing to be taken to task for it's failure to be accessible year in year out for just about every project they release is getting tiresome. There are users who are happy and claim apple's the best at accessibility. If you believe that smoke screen, all the more power to you. Until we get some real representation in a nonjudgmental, helpful, creative solution, we won't get anywhere. I don't mean showing posts of this magnitude as between language barriers, spelling issues, and other factors, this is not a site i'd ever direct a serious bigwig at apple to even attempt to hear us out on anything. Nor would i go the big organization route as all that cements is, if they bitch, we'll do something when it's convenient to our time table. Here's hoping someone will join apple and other big tech firms to eventually get their head out of the dark back end and into bright sunshine. I'm glad we're accessible. We can and should want to do more. Join the beta programs, even on your primary device. Stop letting the idea of something going wrong worry you. You have a 10% chance of that happening. I'd rather brick my devices giving honest feedback then let the scare tactics win over. Before anyone says anything else, no these are not cheap so buying a backup device or another brand new device isn't and shouldn't be expected. I'm also not suggesting just throw caution to the wind. I'll wait until beta three or so then start installing once I've done my research. I also will leave one device on a stable release, such as my watch so even if catastrophe hits, I am not without communication for my elderly parent.

By Sebby on Monday, January 15, 2024 - 08:59

They can't fix it if they don't know about it, so you're absolutely right that we should keep up the pressure, thirsty and depressing as that process can be sometimes.

I just checked because I'm sure this was something I'd formerly told Apple about, so egregious is it. Sure enough, I'd filed this as FB9734824, "Personalized Recommendations" Switch State Not Accessible, on 2 Nov 2021. That's 2 years, 3 months ago, according to Siri. I have every confidence that this issue will eventually be fixed, in the fullness of time. Sarcasm.

And, honestly, I think this is a big part of the problem--the cynnicism and mistrust. It really is very, very draining when we put our best foot forward and it doesn't help. Must. Keep. Going. Must. Not. Surrender.

By Ash Rein on Monday, January 15, 2024 - 08:59

Unfortunately, the accessibility team at Apple seem to all be cited. And funny enough, when you call them, they have the audacity to turn voiceover on during the phone call. That says (and they admit it themselves) that they aren’t using voiceover 24 hours a day. Realistically, I depend on voiceover. There’s no way around it. If it wasn’t on, the iPhone would be an expensive glass paperweight. I have to use it for both simple and complicated things. These representatives don’t. And even though they are quote specialists, they really aren’t aware of the vast majority of issues. Most of the time, they are generally very surprised to find out that there’s any bug. My question to them is always how can they miss it? But if they’re not using voiceover the way that people dependent on it are, of course they’re going to miss it. if you turn on voiceover for 5 to 10 minutes and use the device and then turn it off, the screen reader is a magical thing. If you use it for more than a few hours at a time, you’re gonna realize different problems exist.

My problem isn’t really with voiceover itself. I have two fundamental issues beyond it. I do not like Apple marketing accessibility and using someone like me as a way to convince people to invest in their ecosystem. Especially not when there are so many bugs all over the place. My second problem is that they have no visually impaired or blind Accessibility quote specialists. No one that I can tell in their management and definitely no one when I call or email them. I think the focus really needs to change. Instead of demanding that bugs be fixed, I wish that the community would request that there be a focus on hiring Full-time 24 hour a day voiceover screenreader users. And full-time braille users. And all the other accessibility features that these phones and computers offer.

If they had representatives who relied on the software to try to fill out a PDF and couldn’t, that would really change the game because the need for fixes will be more internal. But getting anybody on this website, or in the blind community to agree on doing anything is not easy. Everybody’s got different opinions and ideas.

By Siobhan on Monday, January 15, 2024 - 08:59

Holy crap, is my mother alive? We agree on something? being sarcastic just to be funny. Really, you're absolutely right. Remember when the watch had the workouts? It took like two months for them to realize, oh there's people in wheelchairs, maybe we should fix that? Insulting at the very least. someone with a brain should've said, people in wheelchairs usually can't stand. Seriously ash, yeah I'm with you. Excuse me while i pray my cold med kicks in, third one I've tried in three days.

By Chrissy on Monday, June 24, 2024 - 08:59

Recently i had this issue and i try to fixed it with the VO thing, but it’s not working. Then i try to turn on the screen recognition button and finally the personalized button on app store is accessible! Thank you so much and sorry for my bad grammar