soundscape icon indicating copy to clipboard operation
soundscape copied to clipboard

Completion of Mobility section separation in the Callouts section of Settings

Open MBtheOtaku opened this issue 4 months ago • 9 comments

Changes should be good hopefully. On my local testing the sections look correct in Settings storyboard

{59226D60-7533-4D0C-9E2C-7AF4C133AB63}

MBtheOtaku avatar Jul 29 '25 17:07 MBtheOtaku

I think you should remove the periods at the end of the callout descriptions in the localized strings. Soundscape will automatically put a comma after the hint so the period may clutter the punctuation. This will make it much easier for Voiceover users to read. The format template should be "Callout Type, Description, state". For example, the Safety callout with the period will look like this: "Safety, Potential hazards like steps and construction areas., on". If we remove the period it looks like this: "Safety, Potential hazards like steps and construction areas, on". Just follow the format of the existing callout descriptions, and you'll be fine.

JJGatchalian avatar Jul 30 '25 14:07 JJGatchalian

Thanks for the updates, but I wonder why your new commits didn't pass all the checks. It says 0/1 checks OK.

JJGatchalian avatar Jul 30 '25 18:07 JJGatchalian

The tests are still in progress.

RDMurray avatar Jul 30 '25 19:07 RDMurray

I've already translated all the callouts, hints, and footer descriptions into Spanish so I should be ready with Weblate after this gets merged. But if there's anything wrong with the text that you think should be changed, let's do so before merging. I'm curious, are these footer descriptions for sighted users to understand what the features do, and if so, does that mean that I won't be able to read them with Voiceover? Thanks.

JJGatchalian avatar Jul 30 '25 20:07 JJGatchalian

They’re primarily just there as extra guidance for sighted users, but I believe VoiceOver will still announce them.

MBtheOtaku avatar Aug 04 '25 18:08 MBtheOtaku

Thanks, so if Voiceover can read the footers, does that mean that we have to turn on the Voiceover hints?

JJGatchalian avatar Aug 04 '25 18:08 JJGatchalian

I don't believe so. Hopefully VoiceOver will naturally read them as you look into section's footer. I think you would only need to add an accessibility hint if you want that text to be announced as a hint on a particular control rather than as its own element.

MBtheOtaku avatar Aug 05 '25 21:08 MBtheOtaku

Sorry I took a while to get round to looking at this. I don't see the footers appearing on device. Is it possible they only show on the storyboard canvas? I'll attach a screenshot.

IMG_4753 IMG_4754

Given that they don't show, and don't actually add anything I think they should be removed.

It seems that the storyboard still has things relating to older versions of the app which are overridden in the ViewController such as the audio section.

Lets keep this PR to just splitting the mobility category - I really want to migrate as much as possible to swiftUI in the future anyway which will be much simpler and more maintainable.

RDMurray avatar Aug 31 '25 23:08 RDMurray

Given that M hasn't separated the footers from this pull request yet, is there a way to get it separated out, like open another pull request with the exact same code minus the footers so that it could be merged? Then I could get to work on the Spanish.

JJGatchalian avatar Oct 12 '25 04:10 JJGatchalian