After some digging (and banging my head against the wall), I narrowed things down to two core issues. I’ve posted them as new topics since this thread title no longer fits and I can't update it. How to force VoiceOver to read decimal point even when there are 6 or more decimal digits? Programmatically force VoiceOver to read parentheses for math expressions

[Since I haven’t heard back, I’m re-posting my comment as a thread reply in case it got overlooked—comments can be easy to miss in this forum.] @Systems Engineer, thanks for the reply! Any pointers to a sample implementation of AXMathExpressionProvider? That doc is pretty thin and doesn't show examples…I learn best through examples! GitHub searches haven't turned up anything useful either. :( Also, my app is a SwiftUI iOS app—can I implement this with SwiftUI alone, or will I need UIKit?

@Systems Engineer, I'm willing to drop back to UIKit if it solved the VoiceOver/braille display issues. Any pointers to an example UIKit implementation of AXMathExpressionProvider? There’s not much to go on in that doc or its related topics. I even tried deep-research mode in both Gemini and Claude Opus. Gemini flat-out gave up, while Claude surfaced this after reviewing 297 sources: The AXMathExpressionProvider protocol does not exist in the current iOS/SwiftUI accessibility APIs. After extensive research across Apple’s documentation, developer forums, GitHub repos, and WWDC sessions, there’s no evidence this protocol exists in the current iOS SDK. It may be hypothetical, planned for the future, or confused with other accessibility APIs.

Animated GIF showing the issue. iOS 18.5 sim on the left, iOS 26.0 beta 3 on the right. [Sorry for the choppiness—can't upload a proper video.]

✅ Submitted FB18909853.

This appears to be fixed in Xcode 26.0 beta 4 (17A5285i).

Looks like this is fixed—the animation now works as expected in iOS 26.0 Dev Beta 4 (23A5297i) and Public Beta 1 (23A5297m). I’ll wait for the next set of betas before calling it fully solved, but so far it's promising.

Changing to .plain, does make make the .disabled() modifier work on an iOS 26 device (toolbar button visually becomes "grayed out"): But I’m trying to match the behavior of stock iOS 26 apps like Reminders and Calendar, where the checkmark/save button is disabled when there are no changes, then .borderedProminent when there are. What's the best way to do this? 👇 Reminders on iOS 26 Calendar on iOS 26

Thanks for the reply. Even with that button declaration, it still won't work when the label: closure contains a Text() element like this: Code Button { print("Checkmark button tapped") } label: { Text("Checkmark") } .buttonStyle(.borderedProminent) .disabled(isButtonDisabled) Recording As I mentioned in my original post, I already filed this as FB19313064. But I’ll update the report to clarify that it only affects buttons that don’t use the label: closure with a Label() element.

Looks like it's still fixed in iOS 26 Dev Beta 5/Public Beta 2 (23A5308g). Hopefully it stays that way. I’ll mark my last update as the answer.

As a workaround, I'm temporarily using ellipsis.circle.badge: But this isn't the recommended More icon anymore. Apple now suggests the standard ellipsis for "More": The problem is, there’s no badged version—so I need a custom "combined" symbol that stays vertically centered, with or without the badge.

It looks like it does have to do with how the button's label is declared. Here's my post about another bug where a button's hit target shrinks based on its label declaration: SwiftUI Button with Image view label has smaller hit target So if I change this sample code to use a label: closure with a Label() view, the button does appear gray when disabled. Interestingly though, it still responds to taps with a bounce animation, even though the action isn’t triggered. That’s still inconsistent with how disabled buttons behave outside of a toolbar. Also, the button grows slightly wider when disabled. Code var body: some View { NavigationStack { VStack { Button{ print("Body button tapped") } label: { Label("Body Button", systemImage: "checkmark") } .labelStyle(.titleOnly) .buttonStyle(.borderedProminent) .disabled(isButtonDisabled) Toggle("Disable buttons", isOn: $isButtonDisabled) Spacer() } .padding() .navigationTitle("Device: \(osTitle)") .navigationBarTitleDisplayMode(.large) .toolbar { ToolbarItem { Button { print("Toolbar button tapped") } label: { Label("Toolbar", systemImage: "checkmark") } .labelStyle(.titleOnly) .buttonStyle(.borderedProminent) .disabled(isButtonDisabled) } } } }

Thanks @Etresoft, that's good to know! Though it’s a bit disappointing that we have to rely on a third-party tool for this. I filed FB20741470 in hopes they eventually fill in the missing availability. 🤞

Turns out that there's a setting to turn this off, so probably something that shouldn't be suppressed by the developer. The setting can be found in: Settings › Accessibility › VoiceOver › VoiceOver Recognition › Text Recognition Screenshot

BTW, if anyone knows how to force a specific size for an inline image in a post, I’d love to know! Whenever I include high-DPI images, I set the width and height so they don’t display huge like the ones above—but it never seems to work. Is this a forum software bug, or am I missing something?