Bulk Action Results are not read by Screen Reader [#2913378]

Problem/Motivation

After performing bulk actions on the content search page, the result of the action is displayed at the top of the page. In Chrome, if the result is an error the screen reader reads the error message; however, if the result is successful the screen reader does not read the success message. In IE, neither result is read by the screen reader. The expected result is that the screen reader is able to read the message, success or failure, across browsers. The issue appears to be similar to work being done for #2805499: Provide screen reader feedback when Views List is filtered by name or description and #2805197: Provide screen-reader feedback when Views UI filterable options are updated, but I couldn't tell if this work would be covered under those tickets.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Original report by @findleys

After performing bulk actions on the content search page, the result of the action is displayed at the top of the page. In Chrome, if the result is an error the screen reader reads the error message; however, if the result is successful the screen reader does not read the success message. In IE, neither result is read by the screen reader. The expected result is that the screen reader is able to read the message, success or failure, across browsers. The issue appears to be similar to work being done for https://www.drupal.org/node/2805499 and https://www.drupal.org/node/2805197, but I couldn't tell if this work would be covered under those tickets.

Comments

Comment #1

2 October 2017 at 21:24

findleys created an issue. See original summary.

Comment #2

andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer and at Annertech commented 3 October 2017 at 06:19

@findleys - welcome, and thanks for filing your first issue! I'm one of the accessibility maintainers for Drupal core.

Can you provide more details about which browser & screen reader combination(s) you have been testing with?

I couldn't tell if this work would be covered under those tickets.

If in doubt, file a separate issue. Don't worry about duplicate issues while you're finding your way around here. The community is quite good at noticing them, and we can close/merge them later.

We have an "accessibility" tag which you can use, which helps to alert other accessibility contributors sooner.

Comment #3

andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer and at Annertech commented 3 October 2017 at 06:20

Issue tags:

+Accessibility

It would help if I remebered to add the tag myself, doh.

Comment #4

andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer and at Annertech commented 3 October 2017 at 06:23

Issue summary:

View changes

Adding issue summary template.

Comment #5

findleys CreditAttribution: findleys commented 28 December 2017 at 17:52

@andrewmacpherson sorry for the significant delay. I just retested on Chrome 63.0.3239.108, JAWS 17.0.2619 and IE11. Issue still exists as described.

Comment #6

mgifford

he/him

English

CreditAttribution: mgifford at OpenConcept Consulting Inc. commented 30 December 2017 at 18:02

Version:	8.2.8	» 8.5.x-dev
Related issues:		+#2805499: Provide screen reader feedback when Views List is filtered by name or description, +#2805197: Provide screen-reader feedback when Views UI filterable options are updated

We should be testing this against the latest dev release.

Comment #7

30 December 2017 at 18:02

Version:

8.5.x-dev

» 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Comment #8

30 December 2017 at 18:02

Version:

8.6.x-dev

» 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Comment #9

30 December 2017 at 18:02

Version:

8.7.x-dev

» 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Comment #10

30 December 2017 at 18:02

Version:

8.8.x-dev

» 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Comment #11

30 December 2017 at 18:02

Version:

8.9.x-dev

» 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Comment #12

30 December 2017 at 18:02

Version:

9.1.x-dev

» 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Comment #13

30 December 2017 at 18:02

Version:

9.2.x-dev

» 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Comment #14

30 December 2017 at 18:02

Version:

9.3.x-dev

» 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Comment #15

30 December 2017 at 18:02

Version:

9.4.x-dev

» 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Comment #16

30 December 2017 at 18:02

Version:

9.5.x-dev

» 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Comment #17

30 December 2017 at 18:02

Version:

10.1.x-dev

» 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.