Yeah, neither of those are remotely popular screen readers, and should not be your primary platforms for testing.
Here’s the major industry survey of screen reader users, from WebAIM.
https://webaim.org/projects/screenreadersurvey9/ (they re-run this survey once every few years; this is from 2021)
Now, you’ve gotta read this survey carefully, because it first talks about desktop browsers, and has a chart “Primary Screen Reader” https://webaim.org/projects/screenreadersurvey9/#primary but it’s specifically referring to primary “desktop/laptop” screen reader.
That chart indicates that “VoiceOver” isn’t very popular, but it’s referring to macOS VoiceOver in that section. (If you scroll down to the “Operating Systems” section, you’ll see that macOS itself isn’t very popular among screen reader users.)
JAWS for Windows is the leading screen reader, followed by NVDA for Windows. macOS VoiceOver is a distant third. Windows Narrator clocks in at 0.5% usage!
Note that JAWS costs money (and its licensing scheme is onerous), and NVDA is free. But also, NVDA tends to be buggier than JAWS; IME, anything that works in NVDA also works in JAWS.
Later, it talks about “Mobile Screen Readers Used” https://webaim.org/projects/screenreadersurvey9/#mobilescreenreaders
That chart shows that the OS builtin screen readers dominate, with iOS VoiceOver (71.5%) and Android TalkBack (29.1%). (These add up to more than 100% because some people use both.)
Missing from this survey is a “time on mobile vs. time on desktop” survey, but, in my experience, the vast majority of bug reports I hear from screen reader users are from iOS users and NVDA users.
So, therefore, I recommend testing in this priority order:
- iOS Safari VoiceOver. I recommend mobile over desktop (because, I claim without data, that mobile is significantly more popular among visually impaired users) and iOS over Android, because iOS is overwhelmingly more popular than Android among visually impaired users.
- Windows NVDA on Chrome. NVDA is not quite as popular as JAWS, but it’s buggier. Anything that works in NVDA will also work on JAWS, but not necessarily vice versa.
- Windows JAWS on Chrome.
- Android TalkBack on Chrome.
- macOS VoiceOver on Safari.
But I think you’ll find that just testing in iOS Safari VoiceOver gets excellent bang for your buck. I normally test iOS Safari only, and then Windows NVDA on Chrome when I want to be very thorough, and then I typically stop.
It’s been at least five years since I’ve seen a user report a bug that occurs in Windows JAWS but not Windows NVDA. I think I’ve never seen a user report a bug on Android TalkBack at all.