Skip to content
This repository was archived by the owner on Sep 5, 2024. It is now read-only.
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

Closed

Description

@Splaktar

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).

Activity

  1. added
    a11yThis issue is related to accessibility
    P1: urgentUrgent issues that should be addressed in the next minor or patch release.
    on Sep 17, 2018
  2. added this to the 1.1.11 milestone on Sep 17, 2018
  3. self-assigned this
    on Sep 17, 2018
  4. Splaktar commented on Sep 19, 2018

    @Splaktar
    ContributorAuthor

    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+.

  5. modified the milestones: 1.1.11, 1.1.12 on Sep 25, 2018
  6. modified the milestones: 1.1.12, 1.1.13 on Jan 3, 2019
  7. modified the milestones: 1.1.13, 1.1.14 on Feb 10, 2019
  8. modified the milestones: 1.1.14, 1.1.15 on Mar 14, 2019
  9. removed this from the 1.1.15 milestone on Mar 29, 2019
  10. 4 remaining items

  11. modified the milestones: 1.1.19, 1.1.21 on May 30, 2019
  12. modified the milestones: 1.1.21, 1.1.22 on Aug 15, 2019
  13. modified the milestones: 1.1.22, 1.1.23 on Oct 22, 2019
  14. modified the milestones: 1.1.23, 1.2.0 on May 5, 2020
  15. modified the milestones: 1.2.0, 1.2.1 on Jul 6, 2020
  16. added a commit that references this issue on Sep 13, 2020
    aaa7a33
  17. added a commit that references this issue on Sep 13, 2020
    2085d64
  18. added a commit that references this issue on Sep 14, 2020
    8ce0813
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1: urgentUrgent issues that should be addressed in the next minor or patch release.a11yThis issue is related to accessibilityhas: Pull RequestA PR has been created to address this issuetype: docs

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions