You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 5, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 5, 2024. It is now read-only.
docs: specify the screen reader versions that are supported #11449
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).
It's probably needed that we define which version of the WAI-ARIA spec we will follow. The 1.0 Spec from March 2014 seems to be fairly well supported across screen readers where as the newer 1.1 Spec from Dec 2017 is only moderately supported on the latest screen readers (and not working at all on older versions of those screen readers, like JAWS 17).
I think that for AngularJS Material it probably makes sense to follow the 1.0 Spec and leave it to Angular Material to worry about supporting 1.1+.
Activity
Splaktar commentedon Sep 19, 2018
It's probably needed that we define which version of the WAI-ARIA spec we will follow. The 1.0 Spec from March 2014 seems to be fairly well supported across screen readers where as the newer 1.1 Spec from Dec 2017 is only moderately supported on the latest screen readers (and not working at all on older versions of those screen readers, like JAWS 17).
I think that for AngularJS Material it probably makes sense to follow the 1.0 Spec and leave it to Angular Material to worry about supporting 1.1+.
4 remaining items
docs(a11y): add a list of supported screen readers
docs(a11y): add a list of supported screen readers
docs(a11y): add a list of supported screen readers