Warning! It is impossible to enter passcode from iPhone screen in iOS 26.3 (23D5103d)

It is possible if you explore by touch. It is possible just more difficult. I've already sent feedback.

Sorry, I don't track the full and rather confusing codes for the betas. I'm on beta 2 of the public fork. Is this Beta 3?

I've turned off automatic update just in case.

A bit of a catch 22 here as we need to report it but, it sounds like if we upgrade to experience and report we're going to be in trouble.

I'm guessing this is voiceover specific? Just another example of why Apple Accessibility are dreadful. We're stuck in a nightmarish loop of needing to be part of the beta to point out the issues which Apple Accessibility rarely fix, but to go into it is to risk our main form of communication.

They should be paying a big bunch of blind users to iron these out or, at the very least, send out second phones for us to test. The consequences of our phones not working, or being locked out, are far more severe than they are for sighted customers. This needs to be recognised.

Is working just fine for me regarding entering passcode using iPhone 15 pro.

I think the next update will be on Monday. Thanks, I was going to update my iPad 9 but will hold on. Will wait for letter A to do so. Long live cats.

Do alternative methods of typing work? I.e, b s i? I know not everyone uses b s i but, i'm wundering if this is a possible workaround?

I'm also not having this issue on a 15 Pro Max. To be clear, this is running the latest dev beta released this week. That's kind of bad news. I mean, good that I can unlock my phone, but bad because when these bugs do not show up for all, it makes them more tough to pin down and resolve.

For those who are experiensing the bug, what's exactly what's going on? I.e, you swipe up to enter the passcode then what? The text field doesn't show up at all? I'm trying to see if I can possibly pinpoint the cause of this.

I am curious if you turn VO off and on, will that help? Long live cats.

That doesn't fix the issue. It also is not impacting everyone.

I was giving a suggestion, I am not using it now. If did not work, well hope the person can get it fix or wait until Monday for the next beta. Long live cats.

It's a good reminder that, unless you are using a secondary device, betas are a bad idea.

16 pro max and iPad 9. Was going to install the beta there, but will wait for next beta. Long live cats.

Imagine if no one beta tested? Beta testing helps catch things like this. So this is an absolutely good reason to beta test.

Agree. However not to many have several devices. Long live cats.

What I think is happening is that users are not able to swipe between elements on the keypad. Wherever VoiceOver focus is, that's where it's going to be stuck unless you move your finger around the screen to a different element.

I always slide my finger around hence hadn't seen this. After what Michael said just tried and it is as suggested. My phone says "swipe up with one finger to unlock" and swiping does absolutely nothing. Only sliding around works and that still works perfectly.

I know that nobody is actually doing what I am about to suggest, but could this be some sort of interaction glitch? For example, the default two finger swipe left and two finger swipe right gestures are for interacting with content, elements, etc. I'm wondering if this bug is forcing VoiceOver focus to act as though the user has interacted (individually) with each element?
Hope that makes sense to everyone.

I'm guessing this is only happening when using 6 digit passccodes?

Hope face ID works but just thought if you update, you need to put your code when phone restart. What about keyboard. For those who use external keyboard be it Braille or regular, does it work? Long live cats.

I can confirm that this is an issue on my 17 Pro Max with beta two of iOS 26.3. If you use explore by touch or braille screen input, you can still enter your passcode, but this is a problem that needs to be fixed, regardless of existing workarounds.

You are, of course, free to beta test: it's down to the individual.

If someone is reliant on their phone, as most of us are,, I'd advise against it.

Imagine if Apple Accessibility did their damn job? They can whinge about us not reporting all they like. we all know we do until we're blue in the face and nothing gets fixed. I simply don't have the time to run down bugs for them.

Apple need to incentivise us to go through the far more protracted and frustrating process of bug reporting (compared with sighted peers), beyond the prospect of our device shitting itself. Holding us ransom with such a prospect is the typical sly and self serving way Apple works. Virtue signalling on one hand, scraping in the money with the other. A gross company, more so because of it's duplicity.

That is bullshit and absolutely incorrect the statement that Apple fixes nothing. If you’re so unhappy with it, then use something else! Better yet, if
you think you can do better, develop your own OS with features that work for everyone! See if, after years, it doesn’t take you time to fix things! Apple
does a damn good job! Are they perfect? No no company is! Does it need to be fixed? Yes. Let’s see what happens when version 26.3 is released. Is it fixed
by then?

-----

For almost everyone, I do not recommend beta testing Apple software on primary devices. Too much can go wrong with very few good options to fix something beyond a device restore or waiting for the next beta, which is inconvenient at best. If you have a secondary device, great. But a daily driver... Hard pass.

Navigation on safari still broken after multiple reports. Apple may fix some bugs and, you're right, I'd like to think this will be fixed by beta 4 and certainly by 26.3, which is to be expected, it's IOS. My main fury is aimed at the stacking pile of failures on Mac though, my displeasure has been stated, con gusto, elsewhere.

We'll always disagree, Denis. We have a fundamentally different view on the service that Apple offers. I understand you are more forgiving of their errors and behaviour. I, on the other hand, am not.

I pay for a working device. I expect a working device. I do not expect to put any work, what so ever, into making my device work. that is the contract and, if the device does not work, the effort must be on the side of the provider, not the consumer.

You don't buy a dog only to bark yourself... though, for those who enjoy such pass times, I don't judge. Woof.

sorry, but if what apple is doing isn't doing it for you, you have the option to vote with your money. IE go over to android, or perhaps another OS if there are others. haven't really checked out the other stuff. Apple is a huge company, dealing in quite litterelly billions of iOS devices. it takes time to track down bugs even in the simplest program, which iOS is not. beta testing shouldn't ever be done on a primary device. if you chose to do that, that's your choice, and apple always warns that it might go wrong. if you didn't listen to that, well, that's was your choice. it's why i don't beta test iOS these days, cause i haven't got a secondary device to play with, and i won't mess up my primary.

Agree with Michael. Only put beta if is the letter A or the RC. Took 3 weeks to fix beta on my iPad 9 when VO did not work. Do not want that again. FYI, Apple still has not fix VO and notifications since 18. Long live cats.

What I really want is a device that's running windows on arm, the size of my iPhone 17 pro max maybe a little bigger but still pocketable, think the form factor of the first generation GPD win but a little thinner and running an arm chip so it'll be fanless and have longer battery than an x86 processor. Think of all the possibilities I could do with a full windows OS and no mobile bullshit restricting me. Apple doesn't want me to run logic on my iPhone 17 pro max because the display is too small? Who cares I'm blind. With this hypothetical real windows phone not mobile I could just open reaper and mix on the go or goldwave for simple edits, web browsing would be way more comfortable with a desktop screen reader like NVDA or Narrator. With this device I wouldn't have to worry about apple or google restricting what I do because in theory it's just a windows computer with a cellular plan and the ability to make calls/texts. This phone would be the ultimate power user phone lol. It's honestly sad how restrictive mobile operating systems are. I'm just really pissed off that apple's gatekeeping logic pro to the iPad purely based on display size even though my 17 pro max could very easily run it and not break a sweat. It's stupid.

I've already paid. I've done my part, they need to do theirs.
Moving on isn't an option in many cases, especially for those of us who use Mac specific software.

You are quite correct. Don't join the beta if you need a working device 100 % of the time. If people are happy to put in the time to fix bugs, good for them and they are doing God's own work, but I do also feel we're doing Apple's job for them. Where is the internal testing? Where is the closed betas done by professionals? The whole beta concept can work well for the sighted market base as it wins on sheer numbers. Expecting a fringe group of users to catch all bugs, report them, feed back just so they can use their devices is kinda nuts though.

IOS is still the best and most accessible platform on the planet... As it damn well should be considering the cost of devices. I simply hold the providers of these devices, the takers of our money, to the advertised standard.

Maybe, if they included in their self congratulatory disability porn that such users had to beta test to fix their own devices, I'd let them off... Funnily enough though, they didn't mention it.

Thank god for beta testers. Thank someone else for the virtue signalling capitalists.