Clearly define our browser support policy, including which browser + screen reader combinations we support

[claviska]

We need to formalize this because screen readers are finicky. Our decision should be based on the most common and reliable combinations. Bugs in other combos can be addressed on an issue-per-issue basis.

As a small team, we unfortunately can't afford spending too much time on edge cases that only impact a small number of users.

[lindsaym-fa]

WebAIM's 2023-24 screen reader survey shows JAWS with Chrome as most common, followed by NVDA with Chrome: https://webaim.org/projects/screenreadersurvey10/#browsercombos

If we want to avoid any commitments to JAWS (NVDA is more common overall than JAWS at this point), I'd vote for verifying the following:

• NVDA with Chrome
• NVDA with Firefox
• VoiceOver with Safari

That said, I wouldn't mind someone on the team having JAWS access. It has significant usage and was a favorite among a lot of the visually impaired users I used to work with.

[KonnorRogers]

I think @lindsaym-fa is correct.

These combos aren't set in stone, but I do think it's a solid start and voice my support for:

• NVDA with Chrome
• NVDA with Firefox
• VoiceOver with Safari

That's not to say we won't support other combos, but these are going to be our main permutations that we test. If someone raises an issue or submits a PR to support a different combo and it doesn't affect these main combinations, I think it'd be fine to add them

Obviously we'd love to add JAWS, but I know licenses can be expensive and a pain to get.

We also haven't touched on mobile devices either, but perhaps thats a discussion for another time.

[claviska]

This seems like a consensus. I'll get the docs updated soon!

[claviska]

Fixed in #958