docs: specify the screen reader versions that are supported #11449
Description
Bug, enhancement request, or proposal:
Proposal
What is the expected behavior?
In addition to specifying the supported browsers, the docs should specify the screen readers that we support.
What is the current behavior?
We build "accessible UI components" but we don't specify any further details.
What is the use-case or motivation for changing an existing behavior?
There needs to be guidance on which screen readers we can support. This is partially due to incompatibilities between different versions and partially due to our limited resources to support a wide range of screen reader products (each significantly different).
The proposal is the support the last 2 major screen reader versions. This means the following
- JAWS 18 and 2018
- NVDA 2017.4 and 2018.2
- VoiceOver macOS High Sierra and Mojave
- VoiceOver iOS 11 and 12
- Android Accessibility Suite 6.1 and 6.2
Which versions of AngularJS, Material, OS, and browsers are affected?
- AngularJS: All
- AngularJS Material: 1.1.11+
- OS: Windows, macOS, iOS, Android
- Browsers: IE11, Edge, Chrome, Firefox, Safari
Is there anything else we should know? Stack Traces, Screenshots, etc.
This proposal is inline with the recommendation that we received from the Google Accessibility team to support the "last two major versions".
We've seen some recent bugs opened up by users of JAWS 17 (from 2015).