Apple Releases iOS 18.3.1, iPadOS 18.3.1, iPadOS 17.7.5, macOS Sequoia 15.3.1, and watchOS 11.3.1

By AppleVis, 10 February, 2025

Member of the AppleVis Editorial Team

Apple has today released iOS 18.3.1, iPadOS 18.3.1, macOS Sequoia 15.3.1, watchOS 11.3.1; and iPadOS 17.7.5 for iPads that cannot run iPadOS 18.

According to Apple's release notes, the iOS 18.3.1 update contains important bug fixes and security updates:

This update provides important bug fixes and security updates and is recommended for all users.
For information on the security content of Apple software updates, please visit this website: https://support.apple.com/100100

While not stated in the release notes, MacRumors reports that iOS 18.3.1 contains a fix for a security vulnerability that was actively being exploited. MacRumors further reports that Apple has released iPadOS 17.7.5 for iPads that are not able to run iPadOS 18.

As iOS 18.3.1 and its companion updates were not distributed to external testers prior to their release, we do not have any information on whether they contain any accessibility fixes for blind, DeafBlind, or low vision users at the time of writing. However, as these updates appear to have been released to address a small number of specific issues, we do not expect them to contain any such fixes.

How to update

iOS 18.3.1/iPadOS 18.3.1 (and iPadOS 17.7.5) are available via Over-the-Air Update (Settings > General > Software Update), via Finder on a Mac with macOS Catalina or later, or via iTunes on a PC or Mac with macOS Mojave or earlier.

To install macOS Sequoia 15.3.1, choose System Settings from the Apple menu, select General in the table, click Software Update in the scroll area, and click the Update Now button to begin the update process. If other updates are available, you can click "More info" to see details about them and select specific updates to install.

watchOS 11.3.1 is available via Over-the-Air Update (Settings > General > Software Update) or by going to the Watch app on your iPhone and navigating to General> Software Update. To install the update, your Watch must be connected to its charger and have at least 50% battery power.

Options

Comments

By TheBlindGuy07 on Tuesday, February 18, 2025 - 21:47

So since this is the latest stable macos release as of writing I'll post this here.
In the macos 15.2 thread I listed a bunch of bugs that I've been reporting for a while now. Apple just reached out about the bug FB15530138 which is the impossibility to navigate within a math equation in pages and other iwork apps, as well as the impossibility to get them in braille as nemeth code. I provided them with more explanations as well as clarifying some misunderstanding about the bug. I reported about 30-50 bugs and it's the first time they are contacting me directly for more information so I'm kinda happy about that.

By PaulMartz on Tuesday, February 18, 2025 - 21:47

Early in the iOS 18 beta cycle, I noticed and reported that VoiceOver focus jumps incorrectly when using the stopwatch feature of the Clock app. It's still a problem in the current release. It's quite straightforward to reproduce and very repeatable. Place focus on the start button and double-tap. Expected behavior: The stopwatch should start, but VoiceOver focus should stay on the start/stop button. This is how it has always worked, from the inception of VoiceOver through iOS 17.x. Observed behavior: VoiceOver focus jumps to the time display and VoiceOver announces the elapsed time every few seconds. Since this was easily reproducible and clearly a bug, I thought it would be fixed promptly. Instead, crickets.

By João Santos on Tuesday, February 18, 2025 - 21:47

I've been on and off the paid Apple Developer Program since 2011. In the beginning I really did engage in and even actively participated in the developer betas. However at some point I began noticing that they don't really care about any Radar / Feedback reports, so I stopped completely since honestly it's a waste of time. In the overwhelming majority of the situations the bugs that I report are either left open for 5 years, at which point they ask if I'm still experiencing them and then close them off if I don't reply within 15 days, and the rest they either close stating that they can't reproduce them or that it's intended behavior.

At one point I actually spent one of the two Technical Support Incident tickets that we get for free every year with the renewal of the paid developer membership to ask a question about a framework. Those tickets are supposed to put us in contact with engineers inside Apple, and since I could not find an answer to my question anywhere else, nor was anyone able to address my questions on the official forums or on reddit, I resorted to those tickets. In response they suggested using a different framework that did not provide the same functionality, refunded my ticket, and disengaged with the conversation. So if even a developer on a paid program spending a finite and very limited resource to request assistance cannot get it, let alone regular bug reports.

I was going to paste my code-level support E-mail exchange with Apple here, but unfortunately the messages mention that I must not disclose them, so in order to avoid any situations that might lead to issues with my relationship with Apple as a developer, which has always been in good standing, and which I depend a lot on professionally these days, I won't do it.

By TheBlindGuy07 on Tuesday, February 18, 2025 - 21:47

wow sad to hear man. I really think this is the kind of post every blind person considering the mac should choose because details aside I have like 50 bugs opened, 4 corrected officially, 3 by accident and never acknowledged, and the rest in that famous blackhole that is apple accessibility feedback or feedback in general from the horrible stories I've seen on reddit. I really feel that even for us blind it's the past reputation of apple that still drive us to them, not the present time...