@simon @jscholes @NoahCarver @Iconfactory I haven't tried it personally either, but I was going to email them with some potential ideas how this could work.

One is obviously using audio, more like the charm utility that @talon made a while ago, which used a continuous sound to indicate things like CPU and memory state.

At that point, maybe the usage stats could sit on the dynamic island, and I think that is actually a place where you could have a voiceover label that would read all the information out.

Another way I thought of is if they had a shortcut that you could assign to a voiceover gesture, which as long as the app was running would also speak this information out.

I think that would probably work to make information like this voiceover accessible.

The audio alerts that are in the app could also potentially be combined with spoken alerts with text-to-speech as well. Sorry for the wall text I was dictating.

@pitermach @simon @jscholes @NoahCarver @Iconfactory @talon We’ve thought about the accessibility issues here and it’s a hard problem.

The main issue is that we’re producing more information than can be read aloud in the one second between updates. There would be a string of information like this:

“12% performance, 34% efficiency, 56% graphics, 100 Mbps download, 200 Kbps upload, 2.2 GB memory”

That can’t be read in a single second, and even if it could, it would be overwhelming.