I’m sure there are people at Apple Accessibility who care, but I don’t think
it’s a coincidence that in general accessibility feature announcements are
coordinated with OS releases which generate PR headlines for Apple. In the end,
Apple are a business, accessibility was something they
What a pitty.
One of the biggest issues concerning Apple Products in my opinion is the
reliability of accessibility.
I really do believe the accessibility team really works hard to keep the OS as
accessible as possible for VoiceOver. But it’s like two steps forward and one
step back. And that’s
The RC came out, so I took the plunge. Sorry to say that the problems are still
there.
If you use Books and run into this bug, however infrequently, please let Apple
know so they’ll be more inclined to fix for the next point-version. I don’t
know about you, but I’m foolish enough to live by
Hi,
it seems to me Apple Books is broken in many ways. Just deleted the app and
reinstalled it. Let see if that‘s helpful.
The issues I had:
• stopped turning pages using VO
• stopped randomely reading in middle of a page
• the special reader doesn‘t work at all since iOS 15
• using the bar at
Thanks for the suggestion but, alas, it didn't work at all. In fact, curiously,
the problems occurred in exactly the same places, accounting for font size.
It's very, very bizarre.
Cheers,
Sabahattin
--
The following information is important for all members of the Mac Visionaries
list.
If
Twice in the iOS 15 cycle I’ve been unable to interact with the Books screen -
both times solved by Scott Davert’s suggestion of deleting and tgen
redownloading the Books app.
Harry
> On 15 Oct 2021, at 22:53, 'Tim Kilburn' via MacVisionaries
> wrote:
>
> Hi,
>
> I’ve had this happen as
Thanks. I’m using the 15.0.2 stable release, but I’ve sent in a feedback on it
anyway. Here’s to hoping the fix is due in an upcoming release. I’m reluctant
to move onto the betas again right now while I’m standardising my clean
installs on 15 stable, but once the release notes are in for the
Hi,
I’ve had this happen as well. It’s fixed for me though now and I can’t recall
if it was fixed before the release of of the latest update, or if it is in one
of the Betas of 15.1. I’d submit a frustration report anyway.
Later…
Tim Kilburn
Jamf Certified Tech
Apple Professional Learning
