SRAL Prioritizies NS Speech over Voice Over on Mac OS X

[JRJurman]

Currently, when Voice Over is active, SRAL will still prioritize NS Speech instead. This is unideal, since Voice Over will almost always be configured in a way that a Screen Reader user would prefer (rate, voice, etc).

This looks like it is most likely unintended. It differs from the Windows configuration which prioritizes JAWS and NVDA over SAPI.

When running the example program, this is the output that I saw:

========================================
  Testing: Engine Information
========================================
Available Engines on this Platform:
  - NS Speech (0x100)
  - Voice Over (0x200)
  - AV Speech (0x400)

Currently Active/Usable Engines:
  - NS Speech (0x100)
  - Voice Over (0x200)
  - AV Speech (0x400)

Current Default Engine: NS Speech (0x100)

After reviewing the repo, my sense is that we should either:

1. Re-order the engines (a breaking change) such that Voice Over is first
2. Add a check (maybe in speech_engine_update) that checks for the Voice Over engine on Mac OS X

I'm happy to test and craft a PR for either of those options. Let me know which makes the most sense here, and I'd be happy to help in any way that I can!

[m1maker]

Hello. I can't test this, but I have this comment. If you can test this and make a PR, I would be very grateful!

[JRJurman]

Ah, I see! When testing this library with Love2d, VoiceOver does work for me, but the example c and python programs in this repo don't appear to work. Maybe there is some quirk running it in a terminal application that causes it not to work?

I can try to build a minimal window example to test, and then post a PR.